RE: [colorforth] DOES> How is colorForth different from other For ths?
- Subject: RE: [colorforth] DOES> How is colorForth different from other For ths?
- From: Frédéric DUBOIS <frederic.dubois@xxxxxxxxxxxxx>
- Date: Tue, 23 Dec 2003 14:16:43 +0100
> -----Message d'origine-----
> De : Chuck Moore [mailto:chipchuck@xxxxxxxxxxxxxx]
> Envoyé : lun. 22 décembre 2003 18:40
> À : colorforth@xxxxxxxxxxxxxxxxxx
> Objet : Re: [colorforth] DOES> How is colorForth different from other
> Forths?
>
> I like this concept of different times for the same word.
> It's like the
> functions associated with objects. Except that it's
> associated with the
> context instead of the object. So far I distinguish: display
> time, edit
> time, compile time, define time and run time. Are there more.
>
Code is data, data is code. Jeff has put the emphasis on this in his Aha
work; IIRC he focused on the fact the code could be organized into a
database, which has some relationships with the OO concepts.
It seems to me that your set of 'times' is complete from the programming
activity point of view. Outside of this activity, there's probably an
infinite number of actions that one wants to perform on a word: for instance
print it, translate a block into an HTML page or perform speech synthesis.
Amicalement,
Frederic
---------------------------------------------------------------------
To unsubscribe, e-mail: colorforth-unsubscribe@xxxxxxxxxxxxxxxxxx
For additional commands, e-mail: colorforth-help@xxxxxxxxxxxxxxxxxx
Main web page - http://www.colorforth.com