Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!cs.utexas.edu!uunet!zephyr.ens.tek.com!tektronix!psueea!psueea.uucp!scowl
From: scowl@psueea.uucp (Scott W. Larson)
Newsgroups: comp.lang.forth
Subject: Re: FORTH, the language
Message-ID: <1523@psueea.UUCP>
Date: 23 Jul 89 05:04:36 GMT
References: <8907220145.AA03972@jade.berkeley.edu>
Sender: news@psueea.UUCP
Reply-To: scowl@jove.cs.pdx.edu (Scott W. Larson)
Organization: Dept. of Computer Science, Portland State University; Portland OR
Lines: 23

In article <8907220145.AA03972@jade.berkeley.edu> Forth Interest Group International List <FIGI-L%SCFVM.bitnet@jade.berkeley.edu> writes:
>   Charles Moore visited the U. of Illinois at Chicago a few years ago,
>and I jumped at the chance to hear him. 
> In the course of his talk, he displayed some of his very own code.
>Thinking that the god of FORTH would have some pretty nifty shit, I was
>shocked to discover that he didn't even use line-spacing to make the
>logical flow of his code more apparent: all the lines were jumbled
>together end-to-end. When I asked him about this, he said he wrote code
>that way because it saved space, and besides, no unit of FORTH code
>should be longer than one screen anyway. Needless to say, there were no
>comments embedded in the code.

Wasn't Moore pushing the radical idea of not keeping ANY source
code around and using a fancy decompiler? This stuff sounds
like the output of a cheap decompiler. 


   ARPANET: scowl%cs.pdx.edu@relay.cs.net
   CSNET:   scowl@cs.pdx.edu
   UUCP:    {ucbvax,uunet,gatech}!tektronix!psu-cs!scowl
   C-SERVE: 72106,1035

	"One comment in NLQ is worth two in draft"--SWL