--
You received this message because you are subscribed to the Google Groups "ColorForth" group.
To unsubscribe from this group and stop receiving emails from it, send an email to Color-Forth...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/Color-Forth/308d1f0b-d191-455c-8745-8830a27996ad%40googlegroups.com.
But meanwhile GreenArrays have decided, quite sensibly, that the vast majority of Forth programmers are more familiar with conventional ASCI, and have provided a new board #2 with PolyForth as the main proven and reliable higher level workhorse. So I shall buy EVB #2 also, and attack my problem that way as well. Working in parallel on two parallel EVBs: programming the one in CF, the other in PF. I have plenty of time -- I'm a pensioner.
I am an IT industry veteran and in 2016 I retired early. My personal IT journey started with the Commodore 64 (its processor, the 6502, was an early target for Fig-FORTH) and professionally with IBM-DOS and the Intel 80286 processor. Because I, too, have plenty of time I am free to pursue my passions. IT is still one of my hobbies hence my interest in Forth.
Forth is fascinating because it does things so very differently from mainstream IT. These differences include the language Forth uses to describe things (e.g. meta-compilation vs cross-compilation).
ColorForth, as far as I can tell, included 3 parts:
1) Native booting FORTH operating system - now just a Windows executable running SaneFORTH (sF) and still used with ArrayFORTH (aF)
2) Some middleware providing some kind of byte-code compilation/pre-compilation - I am not really clear what this does and why it is strictly necessary - this appears to have been removed in aF 3.
3) The editor - which still exists in aF 3 and appears to work the same.
The GreenArray evaluation boards appear to use polyFORTH for the host chip and eFORTH for the targets.
As far as I can see Chuck Moore stopped developing a native
booting FORTH system after he converted it for the Intel Pentium. Booting an
operating system for any modern system's chipset (Intel, AMD, ARM, etc) is fiendishly
complicated. GreenArrays decided to use a Windows Application (saneFORTH)
instead. This makes sense as you can let
Microsoft worry about the details. These
days EFI booting is the way to do this.
Much of the recent ColorFORTH activity on this mailing list is aimed at creating a new, USB bootable, version of ColorFORTH.
The middleware part of ColorFORTH seems to have been dispensed with because the benefits were outweighed by the complexity.
The editor still exists and this bit is what I am interested in, just because it is unusual. Thankfully GreenArrays default keyboard is qwerty and not the, utterly useless in my view, Dvorak keyboard (see https://reason.com/1996/06/01/typing-errors/). The question in my mind is how you might use the editor to code for other FORTH targets.
PS: Elizabeth Rather clearly had a gift for understanding, documenting and explaining FORTH. I think that without her no one, other than Chuck Moore, would have used the language
--
You received this message because you are subscribed to the Google Groups "ColorForth" group.
To unsubscribe from this group and stop receiving emails from it, send an email to Color-Forth...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/Color-Forth/c62f5a37-8585-4d09-8996-cf17b92159d9%40googlegroups.com.