#Forth vs C
Thanks…
I really do like MultiForth. I wish the Forth community could agree to
some standardized extensions (like the MultiForth locals, quans, I/O
etc…). Software companies are reluctant to use Forth and be dependent
upon a single vendor.
By the way, the Macintosh version of MultiForth does have structs. I
allways avoid floating point except where it's a must (high resolution CAD)
and then I'd rather use a co-processor direct.
I authored 2 games in '85 for the Mac written in Forth. Mac Challanger (a
flight simulator) and Pyramid of Peril (a real time, first person
adventure). On the Amiga I wrote a CAD program in 'C' (Aegis Draw/Draw
Plus etc…) because the program was highly complex (structs and linked
lists everywhere), unfortunitly needed floating point, and needed to
support several compilers. Forth needs the equilivent of STDIO, that would
allow programmers to move between machines and versions of Forth and
maintain compatability. My fustration with the lack of market reality
within the Forth community is compounded when I see the success of Forth
like systems ala PostScript.
I have a friend on the IEEE Forth standards team who asked me what I wanted
to see in a standard to make Forth more popular. I told him thay should
adopt a syntax compatable with PostScript and provide a set of standard,
optional extensions. This was considered heresay. But I still think it
might work. Anyway I miss Forth and wish it well…. William Volk