[colorforth] DOES> How is colorForth different from other Forths?

["Robert Patten" <pattenre@xxxxxxxxxxx>]

Rough draft   please edit:
In forth  " DOES>  "   Changes the action of the last created word to get
it's parameter address and place it on the data stack then execute words
following " DOES> ".

: VARIABLE ( - ) CREATE  0 , DOES> ( - a )  ;
: CONSTANT ( n - ) CREATE   ,  DOES> @  ( - n ) ;
: ARRAY ( n - ) CREATE  ALLOT  DOES>  +  ( - a ) ;

In  color forth  variable is provided with magenta word
which  makes a macro entry that defers the source  variable object address
as a constant and a forth entry that puts the  source variable object
address on the data stack.
I colorForth constant is  yellow words computing the value of the constant a
red word, creating a program entry,  and a green ;   deferring top of stack
as a literal and
deferring exit.


----- Original Message ----- 
From: "Jeffrey Massung" <jma@xxxxxxxxx>
To: <colorforth@xxxxxxxxxxxxxxxxxx>
Sent: Friday, December 12, 2003 1:37 PM
Subject: Re: [Re: [colorforth] (state) How is colorForth different from
other Forths? / reply II private]


If anyone with significant experience with colorForth could cover a specific
topic, I'd love one done on DOES> . While I haven't programmed in colorForth
yet, and perhaps won't, I do enjoy the theory behind it and Machine Forth.

DOES> is a word that I use throughout my Forth code and I feel is one of the
most powerful aspects of the language. colorForth doesn't have it, but
perhaps
something equally as powerful?

Jeff

"Robert Patten" <pattenre@xxxxxxxxxxx> wrote:


Please start a list  on how they are a like.   I  will take  editing   the
difference list.  We all can  contribute to these lists.   This format
takes one concept at a time and contrasts it with  Forth which will allow
all interested forth users  a deeper understanding of ColorForth.  As each
concept is deemed correct I will post them to Comp.lang.forth for a greater
exposure and the best material  edited into the ColorForth wiki
Robert

----- Original Message ----- 
From: "Tim Neitz" <tim@xxxxxxxxxxxxxx>
To: <colorforth@xxxxxxxxxxxxxxxxxx>
Sent: Friday, December 12, 2003 11:46 AM
Subject: Re: [colorforth] (state) How is colorForth different from other
Forths? / reply II private


> ,
> ,
> ,
> Dear Robert, Tim here again.
>
> I also wanted to indicate that sometimes it might also be effective
> to point out some similarities between cf and old forth.
>
> These are clearer to me now, but in the start, it made me ask,
> are there any similarities? Now I see there are many.
>
> With kind regards,
>
> Tim Neitz
> rj_cf on #c4th IRCnet
> tim@xxxxxxxxxxxxxx
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: colorforth-unsubscribe@xxxxxxxxxxxxxxxxxx
> For additional commands, e-mail: colorforth-help@xxxxxxxxxxxxxxxxxx
> Main web page - http://www.colorforth.com


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






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


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