Path: utzoo!censor!geac!torsqnt!news-server.csri.toronto.edu!cs.utexas.edu!samsung!rex!uflorida!gatech!udel!ee.udel.edu
From: new@ee.udel.edu (Darren New)
Newsgroups: comp.lang.misc
Subject: Re: Look ... [or: one, two, three, many]
Message-ID: <40690@nigel.ee.udel.edu>
Date: 4 Jan 91 17:21:40 GMT
References: <19717:Jan220:38:5491@kramden.acf.nyu.edu> <40569@nigel.ee.udel.edu> <3340:Jan322:21:4791@kramden.acf.nyu.edu>
Sender: usenet@ee.udel.edu
Organization: University of Delaware
Lines: 22
Nntp-Posting-Host: snow-white.ee.udel.edu

In article <3340:Jan322:21:4791@kramden.acf.nyu.edu> brnstnd@kramden.acf.nyu.edu (Dan Bernstein) writes:
>Gee. I wrote a Forth interpreter in 8088 assembler. Does that make Forth
>a subset of 8088 assembler?

No, and that was the point that the original poster made.  Just because you
can code composable functions in C does not mean that composable functions
are part of C.  

>> Precisely which "features of
>> Fortran syntax" is C incapable of handling?
>
>A parser for C cannot parse Fortran's spacing conventions. Finis.

But the original code fragment passed a string to a function.  Hence, you
are not talking about a parser for C, but rather a parser written in C.
Hence, again, the original poster's argument makes the point.
	   -- Darren
-- 
--- Darren New --- Grad Student --- CIS --- Univ. of Delaware ---
----- Network Protocols, Graphics, Programming Languages, 
      Formal Description Techniques (esp. Estelle), Coffee, Amigas -----
              =+=+=+ Let GROPE be an N-tuple where ... +=+=+=