Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!tut.cis.ohio-state.edu!cwjcc!hal!ncoast!allbery From: allbery@ncoast.ORG (Brandon S. Allbery) Newsgroups: comp.unix.wizards Subject: Re: stdout (was What "isatty"?) Message-ID: <13694@ncoast.ORG> Date: 3 Jun 89 18:14:55 GMT References: <19756@adm.BRL.MIL> <17796@mimsy.UUCP> <13692@ncoast.ORG> Reply-To: allbery@ncoast.UUCP (Brandon S. Allbery) Followup-To: comp.unix.wizards Organization: Cleveland Public Access UN*X, Cleveland, Oh Lines: 15 As quoted from <13692@ncoast.ORG> by allbery@ncoast.ORG (Brandon S. Allbery): +--------------- | I'd prefer that "cc" build the pipeline to cpp, ccom, and c2/optim/copt/ | whatever-it's-called-on-system-xyzzy, then write the resulting assembly code +--------------- Come to think of it, the user can perfectly well pipe the output of cc to optim his/her/itself, as desired. ++Brandon -- Brandon S. Allbery, moderator of comp.sources.misc allbery@ncoast.org uunet!hal.cwru.edu!ncoast!allbery ncoast!allbery@hal.cwru.edu Send comp.sources.misc submissions to comp-sources-misc@ NCoast Public Access UN*X - (216) 781-6201, 300/1200/2400 baud, login: makeuser