3 ms·
In Forth, you have to reason about how many things each command takes off the stack and leaves on the stack, whereas with pipes, it's always exactly one thing.
by xigoi 4y ago
In Forth, you have to reason about how many things each command takes off the stack and leaves on the stack, whereas with pipes, it's always exactly one thing.
- benj111 4y agoThat's true I suppose, but is the the only issue with forth? Or perhaps it's that a stack is good for certain things, but not for everything? If your language just consisted of map() you'd soon run into its limits.
- smcl 4y agoYeah I think it’s one of the less-hard things about Forth. For what it’s worth I quite enjoyed fiddling with Forth, and went through a bit of a “stack computing” phase. I never made the connection with the the pipe operator tho