Sat Sep 15 05:07:40 CEST 2007
sticking to forth as basis
reading http://lambda-the-ultimate.org/node/2452 forth in the news
i'm more and more convinced that forth should be the lowest level, not
some block structured higher level construct, which would require more
elaborate optimizations. it's best to have the pure control structs
(i.e. for next) as direct macros, and implement the higher code block
quoting constructs in terms of them.
forth has this way with return stack juggling that's very powerful for
making new control structures. this is hard to do efficiently when you
tuck it all away in combinators..