Treat the bottom of the stack as implicit ""
A stack-oriented programming language suitable for code golfing
Status: Alpha
Brought to you by:
aditsu
This is an alternative suggestion to ticket 3.
Whenever an operator tries to use more operands than are present on the stack, supply empty arrays for the others. Most use-cases I can think of are source-layout challenges, but you can also consider being able to terminate a g or h loop by emptying the stack, or being able to build a string in a loop with + without having to supply an empty string manually first.
I have thought about this some more, and I think this could actually be even more powerful: additionally add an operator which allows to switch the element that is returned on the bottom of the stack. The default could be either
0or""(something falsy). I'm not entirely sure which of these is more useful - they both have their use cases. But then if I can do something like5ev, then from then on hitting the bottom of the stack implicitly returns5.