_________________
http://WilsonMinesCo.com/ lots of 6502 resources
The "second front page" is http://wilsonminesco.com/links.html .
What's an additional VIA among friends, anyhow?

For INTERPRETER one use case might be if the user wanted to set up a vocabulary of words to be used in an application (eg, a menu system) that are all interpreted.

But, yes, factoring eases testing and debugging as you are building a wordset, which is why many advise that most definitions should be two to seven words long. The shorter the word, the easier it is to identify and test all edge cases before moving on to the word that contains it.

In that example, a peephole optimizer could be added to the COMPILER word, without having to test whether a regression was introduced for the interpreter state.

_________________
http://WilsonMinesCo.com/ lots of 6502 resources
The "second front page" is http://wilsonminesco.com/links.html .
What's an additional VIA among friends, anyhow?

That sounds a lot like what CASE does. And it sounds like the menu words are being created "on-the-fly", so to speak. Wouldn't it be more efficient to compile all words before the application even starts? Or are we theorizing more to use these words as a sort of program overlay for computers with less memory?

Or maybe something more like importing Pascals Procedure calls.

Not on the fly, but independent of the menu system, so the menu can be tailored to the use. One variable to hold the main menu word vocabulary, and a block or file with the menu structure... first word in a line is the main menu heading, following words are choices within that heading. You can develop with a typed command dispatch to test words, and when you have the actions you want in the menu, type up the menu structure.