RE: [colorforth] To kernel, or not to kernel

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

> -----Message d'origine-----
> De : Arthur W. Green [mailto:goshawk@xxxxxxxxx]
> Envoyé : jeu. 11 mars 2004 20:51
> À : colorforth@xxxxxxxxxxxxxxxxxx
> Objet : Re: [colorforth] To kernel, or not to kernel
> 
> 
> Frédéric DUBOIS <frederic.dubois@xxxxxxxxxxxxx> wrote...
> 
> >I think it is the role of the kernel to hold the definitions  common to
your
> >apps. Then it can harbor the utility apps you want at your fingertips,
too.
> >
> I'd rather see the kernel harbor just enough code to bring up 
> the virtual machineForth, and nothing else. With all other code as
"high-level"
> source, including colorForth itself, not only would colorForth be far
> more versatile (and better documented than it is), it would 
> be far easier
> to move code to any platform just by reimplementing the 
> hardware abstraction.
> 

It depend on the context; if we're talking about a kernel to be distributed
to others, I agree with you. If we're talking about _your_ kernel you use at
home, orthogonality or minimalism is less important and you'll certainly
prefer a custom one.

	Amicalement,
	Frédéric


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