News for hackers. Stuff that matters.
Re:Why Concatenative Programming Matters (2012) by michaelfeathers on Saturday April 13, 2013 @05:19PM (#5544715)
The only thing that bothers me about the concatenative languages I've seen is the stack. It is a global variable. You don't have the bounding (this is your part of the stack) that you have in languages that have an enforced frame for procedure/method calls.

Sometimes I wonder what a concatenative language would look like if operations could only access things given them by the immediately previous operation and if those things were read-only.

Re:Why Concatenative Programming Matters (2012) by abecedarius on Saturday April 13, 2013 @07:24PM (#5545097)
One thing it could look like is Backus's FP. I made a concatenative variant of it back in the 80s, and just rewrote the essentials this afternoon: https://github.com/darius/peglet/blob/master/examples/fp.py

In my earlier dialect I added a form of local variables, just enough for better readability without really changing the semantics.

Re:Why Concatenative Programming Matters (2012) by mwotton on Saturday April 13, 2013 @05:29PM (#5544747)
Row polymorphism has something to say about this, doesn't it? Coming from Haskell, I'm still finding concatenative programming hard to handle.