Implementing DOES> in Forth, the entire reason I started this mess

Re:Implementing DOES> in Forth, the entire reason I started ... by sph on Tuesday June 10, 2025 @02:46AM (#44233439)

All the most common Forth I know implement CREATE DOES>

What’s funny, is that I used to know how it works, now any time I come across these kind of articles I get more and more confused and further away from understanding. It’s like reading those convoluted explanations of what a monad is.

[ Parent | on HN ]

Re:Implementing DOES> in Forth, the entire reason I started ... by spc476 on Tuesday June 10, 2025 @02:55AM (#44233510)

It only briefly goes into what it does, this article goes into how it's done for a particular implementation.

[ Parent | on HN ]

Re:Implementing DOES> in Forth, the entire reason I started ... by alexisread on Tuesday June 10, 2025 @04:21AM (#44234058)

It implements defining words ie. Additional compiler words.

It does this by doing something now, and later (you could read create does> as now later>)

So for

: CONSTANT CREATE , >DOES @ ;

This makes the defining word CONSTANT, which when run (now) compiles the next word

So CONSTANT myvar will compile myvar. Myvar, when run (later) will get it's value and push it to the datastack.

[ Parent | on HN ]