RE: [colorforth] forth taxonomy

[Frédéric DUBOIS <frederic.dubois@xxxxxxxxxxxxx>]

> -----Message d'origine-----
> De : Mark Slicker [mailto:maslicke@xxxxxxxxxxx]
> Envoyé : ven. 1 août 2003 15:52
> À : ColorForth@xxxxxxxxxxxxxxxxxx
> Objet : [colorforth] forth taxonomy
> 
> 
> Forth has a long history. I'm only familer with one implementation
> (colorForth), is there classification of past techiniques? I 
> feel I would
> be more able in implementing new colorForths if I understood 
> the breadth
> of past Forth implementations.
> 
> Thanks,
> Mark
> 
>

That's an ambiguous question; what do you mean by technique?
A well known classification is by threading scheme:
- Token threaded
- Indirect threaded code
- direct thread code
- subroutine threaded code
- native code
Another answer would be the history of Chuck's Forth:
Early implementations: I wasn't born :) IIRC you can find "The history of
Forth" at Forth, Inc.
cmForth - designed for the Novix
OKAD : sourceless programming
ColorForth
But there's probably someone else who knows better.

If I read correctly Jeff Fox, OKAD was a sourceless system; that is, you got
a human-readable source by de-compiling the object code. Chuck was not
satisfied with it because you lose information in the process. I think
ColorForth is a "soften" version of OKAD where source and object code are
mixed - but that's my interpretation of the story. Correct me if I'm wrong.

 Amicalement,
 Frederic


---------------------------------------------------------------------
To unsubscribe, e-mail: colorforth-unsubscribe@xxxxxxxxxxxxxxxxxx
For additional commands, e-mail: colorforth-help@xxxxxxxxxxxxxxxxxx
Main web page - http://www.colorforth.com