Re: [stack] What are the advantages and disadvantages in manipulation of the return stack

>  Even if you specify exactly how the return
> stack is to behave (e.g. you disallow the compiler to inline functions),
> you'll still have eliminated essentially any possibility for equational
> reasoning because any function can rip its caller off of the return stack
> (or worse, if that's even possible).
> 
in my design for XY i was looking for a way to allow the
programmer to do the maximum possible harm with the least
amount of typing in a language with the smallest possible
base.
> 
> I think that allowing access to the to-be-evaluated syntax tree (i.e. the
> "queue") is also extremely harmful as it means any program modification has
> a global effect; you can't locally verify that some other part of the
> program doesn't behave differently depending on some part of the queue that
> you'll be changing. It would seem you're already far down this path
> however.
> 
yes, that's it exactly.




[Non-text portions of this message have been removed]