Chuck Moore’s ColorForth (formerly available at http://www.colorforth.com, now some info at http://www.inventio.co.uk/cf2019_colorForth.pdf) is a very interesting system. While I admire it both as a novelty and as an effective system in some hands and for some projects, I do not see how I can adopt it entirely at this time. Below are some specific comments, but I reserve the right to change my mind.
I have no objection to this. I even began writing an Emacs mode to try this out. It more or less works, but would need some polishing. See the link to it from my main Forth page (../forth.html).
However, I am still using symbols (rather than color) to “tag” words in Riscy Pygness. Specifically,
$03F8
),&PINSEL0
),'A
is the number 65),So, other than the verbosity of using symbols rather than color for tags, my system seems fairly compatible both with ColorForth and with classic Forth.
ColorForth appears to have exactly two tasks, a foreground task and a background task.
Riscy Pygness similarly has a fixed number of tasks (three in the current version, although this is adjustable).
In ColorForth, OR
means exclusive OR and there is no inclusive OR
I am not able to wrap my mind around this and so retain both the usual OR and XOR.
I embrace these wholeheartedly.
;
to represent the exit).CUT
(which I believe was written as //
in ColorForth and/or some of Chuck’s other Forths), which is used to mark special cases where the use of a semicolon must not cause the preceding subword to be changed to a jump and must result in the compiling of an actual exit, e.g. after a THEN
.