colorForth

[yurapyon]

PR (#35)

colorForth is very smart problems: editor support

goals: make vm easier to implement remove cruft from the standard make the language simpler

[yurapyon]

• 'traditional' direct threaded forth
• VM more inspired by MuP21 or f18 chips https://www.ultratechnology.com/mup21.html https://www.greenarraychips.com/home/documents/greg/PB003-110412-F18A.pdf

threading will create a more clear separation between machine code and calling forth words, which will make the language easier to use

simplifying the instruction set and VM architecture will make it easier to port

[yurapyon]

address register, @+, !+

• seems easy, could probably just be done with a forth variable

circular stacks

• data stack is easy, but how should return stack be done?
• sentinel would be needed to mark when the execution loop should exit

[yurapyon]

remove the concept of hiding words, its not very often that i override words using a new word with the same name. this will also simplify terminators because all they do now is record whether a word is immediate or not

[yurapyon]

automatic tailcalls:

• ';' can convert the previous compiled word to a tailcall. how does this work with data or strings?
  • can just have the word tailcall 'nop' at the end of the string definition
• are there other ways to do it

[yurapyon]

rename 'here' to 'h' ? then 'here' is 'h @'

[yurapyon]

remove u/mod or /mod or whatever, just go off whatever the AVR instruction set gives you

[yurapyon]

closing in favor of this PR https://github.com/yurapyon/mini/pull/35