Re: [colorforth] meta-compiler
- Subject: Re: [colorforth] meta-compiler
- From: albert@xxxxxxxxxxxxxxxxxx (Albert van der Horst)
- Date: Tue, 31 May 2005 11:41:52 +0200
On Mon, May 30, 2005 at 02:34:03PM -0400, Mark Slicker wrote:
> On Mon, 30 May 2005, Albert van der Horst wrote:
>
> >I miss some premises here, that maybe are implicit.
> >So what is the idea about
> >- where is the source, presumably in colorforth blocks?
>
> Yes colorForth source.
>
> >- how to handle bootcode.
> >
> >But there is a problem here. The editor is in colorforth. So the
> >new colorforth may require tricks from the editor that are not yet
> >present (say e.g. a new color). Right?
> >
>
> I'm not sure what you're asking. The editor and compiler both agree on the
> source format, other than this there is little interaction between the
> two. The editor can easily be taken out of the kernel, and in fact Chuck
> calls it a historical accident the editor currently resides in the kernel.
A historical accident, is that a negative assessment, i.e. something
that preferably be changed? (This is just my understanding of English).
About my question. Suppose you want to add a color. Now the source
has to be generated by the old colorforth. So its editor must know
that new color?
<SNIP>
Groetjes Albert
--
Albert van der Horst,Oranjestr 8,3511 RA UTRECHT,THE NETHERLANDS
Economic growth -- like all pyramid schemes -- ultimately falters.
albert@xxxxxxxxxxxxxxxxxx http://home.hccnet.nl/a.w.m.van.der.horst
---------------------------------------------------------------------
To unsubscribe, e-mail: colorforth-unsubscribe@xxxxxxxxxxxxxxxxxx
For additional commands, e-mail: colorforth-help@xxxxxxxxxxxxxxxxxx
Main web page - http://www.colorforth.com