Unraveling the Mystery of Forth's DOES>

This article delves into the intricate implementation of the `DOES>` word in the Forth programming language. `DOES>` enables the creation of 'smart data structures' capable of executing custom actions. The author meticulously explains the three temporal aspects of `DOES>`: compile time, definition time, and runtime. Using the examples of `SHAPE` and `MAN`, the article illustrates how `DOES>` modifies the execution address of newly created words to achieve its functionality, ultimately executing the code following `DOES>` at runtime. The complexity of implementing `DOES>` and potential conflicts with modern OS memory management are also discussed.