Path: utzoo!attcan!uunet!husc6!uwvax!rutgers!bellcore!tness7!killer!vector!rpp386!pigs!haugj
From: haugj@pigs.UUCP (Joe Bob Willie)
Newsgroups: comp.unix.wizards
Subject: Re: /dev/stdin
Message-ID: <190@pigs.UUCP>
Date: 18 Jul 88 18:01:22 GMT
References: <16305@brl-adm.ARPA> <8220@ncoast.UUCP> <12327@mimsy.UUCP> <8241@ncoast.UUCP> <12472@mimsy.UUCP>
Reply-To: haugj@pigs.UUCP (Joe Bob Willie)
Organization: Big "D" Oil and Gas
Lines: 34

In article <12472@mimsy.UUCP> chris@mimsy.UUCP (Chris Torek) writes:
|>In artcile <12327@mimsy.UUCP> Chris also wrote (re multiple compiler passes)
|>>... the first will be /lib/cpp, without output sent to a temp file ...
|
|In article <8241@ncoast.UUCP> allbery@ncoast.UUCP (Brandon S. Allbery) writes:
|>May I remind everyone that nowhere does it state that Unix cc *must* have a
|>separate /lib/cpp?
|
|Okay:  `the first will be the preprocessor, with output sent to a temp file'.
|
|Happy?
|
|( :-) )

nope, still not happy.  the compiler doesn't even have to have a separate
pass which includes a preprocessor.  assuming the compiler itself can
parse the C source in one pass, the ``output'' of the preprocessor need
never be saved to a file.

as an example, the input function could return characters from a 
preprocessorified buffer for such things as macro expansions, or straight
from the file, which might be either the normal input (c.c), or from
an include file.

any compiler which makes more than one pass over the source code should
be shot out of a cannon, so cc -c /dev/stdin.c should still work.  for
all reasonable values of cc. ;-)

- john.
-- 
 John "Evil USENET User" F. Haugh II          HECI Exploration Co, Inc., Dallas
 UUCP: ...!killer!rpp386!jfh                            jfh@rpp386.UUCP :DOMAIN
 **** Trivia question of the day: VYARZERZIMANIMORORSEZASSEZANSERAREORSES? ****
 "You are in a twisty little maze of UUCP connections, all alike" -- fortune