4 ms·
> At some point I came across some writing that suggested that Forth had a “loop control stack”. Wouldn't it be nice if I could implement some kind of loop cont
by uticus 3y ago
> At some point I came across some writing that suggested that Forth had a “loop control stack”. Wouldn't it be nice if I could implement some kind of loop control stack that worked for all kinds of iteration?...I added two loop control stacks – what I call the i-stack, and the next-stack. The i-stack contains the current value(s) being iterated over, and is read from with the i and j words like normal.
So much of what we do has already been done. In Brad Rodriguez' "Moving Forth" series (c 1993) he talks about classical Forth having 5 registers, 2 of which point to stacks. He then explores which of these 2 could point to a hardware stack, and how this decision has been taken historically with other Forths.
I like someone who blogs about Forth in 2023. But if they are truly curious about Forth they'll find themselves reading a bit of history. Forth has been around for quite some time now.
http://www.bradrodriguez.com/papers/moving1.htm http://www.bradrodriguez.com/papers/moving1.htm (speaking of history, this paper itself has a nice compilation of references)
Btw information-superhighway.net does have some excellent articles where they dig a bit more into history behind things: https://blog.information-superhighway.net/spellcaster https://blog.information-superhighway.net/spellcaster
- macintux 3y ago> I like someone who blogs about Forth in 2023. But if they are truly curious about Forth they'll find themselves reading a bit of history. Forth has been around for quite some time now. I've found that many people passionate about something will have read quite a bit about its history. Hardly seems sporting to imply that the author is ignorant of everything; perhaps this is something they overlooked.