Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!umcp-cs!chris
From: chris@umcp-cs.UUCP (Chris Torek)
Newsgroups: net.unix
Subject: Re: Porting UNIX Applications to the Mac
Message-ID: <3708@umcp-cs.UUCP>
Date: Mon, 6-Oct-86 20:19:17 EDT
Article-I.D.: umcp-cs.3708
Posted: Mon Oct  6 20:19:17 1986
Date-Received: Wed, 8-Oct-86 06:44:14 EDT
References: <1572@cbdkc1.UUCP> <1091@hoptoad.uucp>
Reply-To: chris@umcp-cs.UUCP (Chris Torek)
Organization: University of Maryland, Dept. of Computer Sci.
Lines: 24

>>>	I use "cat | cc -O " myself.

>In article <3617@ism780c.UUCP> tim@ism780c.UUCP (Tim Smith) writes:
>>On what UNIXs does this work?   Most cc's that I have seen will not
>>take stdin. ...

In article <52@its63b.ed.ac.uk> simon@its63b.ed.ac.uk (Simon Brown) writes:
>Or even better with symbolic links!
>
>Or perhaps, if you've got System V, you could use named pipes? :-)
>	/etc/mknod fifo.c p
>	cc -O fifo.c &
>	cat > fifo.c

In all seriousness, I sometimes run `/lib/ccom | /lib/c2' to
investigate some aspect of the compiler.  `/lib/cpp | /lib/ccom |
/lib/c2 | as -o foo.o' works too, on a 4BSD Vax.  (The Sun assembler
reads its input twice, and must be able to seek.  Alas!  The Vax
assembler is also two-pass, but it records its second-pass information
in /tmp files.)
-- 
In-Real-Life: Chris Torek, Univ of MD Comp Sci Dept (+1 301 454 1516)
UUCP:	seismo!umcp-cs!chris
CSNet:	chris@umcp-cs		ARPA:	chris@mimsy.umd.edu