Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!bloom-beacon!oberon!garfield!kopaz
From: kopaz@garfield.RDL.COM (John 'Echo' Kopaz)
Newsgroups: comp.lang.forth
Subject: Re: Forth Pre-Compier
Message-ID: <135@garfield.RDL.COM>
Date: 13 Sep 88 19:17:09 GMT
References: <8808121826.AA23206@jade.berkeley.edu> <1575@crete.cs.glasgow.ac.uk> <1609@crete.cs.glasgow.ac.uk>
Organization: Research Development Labs (RDL), Culver City, CA.
Lines: 35

In article <1609@crete.cs.glasgow.ac.uk>, orr@cs.glasgow.ac.uk (Fraser Orr) writes:
> [...]
> I agree totally, forth is the assembly code of a more powerful model
> of serial comunication. What I've been suggestion for the past few
> months is designing a compiler that can produce this machine code
> without loosing any of the power of the new model.
> 
> Regards,
> === Fraser "Head in the clouds academic" Orr  :^>

(opinion alert)

this proposed compiler does *NOT* preclude the use of forth as it is!!!

i think fraser's idea is sound.  with the advent of forth chips, the
ability to compile a 'high level language' into forth (or something 
like it) will be needed.  this is not a trivial problem though...
as many of you stated there are as many run time environments
as there are problems!!!  this compiler would create its own r.t.e.
based on the h.l.l. that it implements and any volumes from the
library it checks out. (:`] (couldn't resist..) 

this should be viewed as a boon to forth, not as an attack!!

forth *IS* the assembly of code of a *MUCH* more powerful model
of communication (serial and otherwise...)!!!  i think we should
exploit it to its fullest extent.

-- 
john a. kopaz				| 
group head, simulators			| ...after six, it's just syntax...
research scientist by association	|
voice: 213-410-1244 -- fax: 213-216-5940 -- corporeal: rdl 
arpa : kopaz@rdlvax.rdl.com                            5721 w. slauson ave.
uucp : ...!{psivax,csun,sdcrdcf,ttidca}!rdlvax!kopaz   culver city, ca 90320