Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!rutgers!sun-barr!cs.utexas.edu!tut.cis.ohio-state.edu!bloom-beacon!husc6!ogccse!cvedc!nosun!illian!sopwith!snoopy
From: snoopy@sopwith.UUCP (Snoopy)
Newsgroups: comp.unix.wizards
Subject: Do we need auxin and auxout? (was: Should fd 3 be /dev/tty?)
Summary: I still think so.
Message-ID: <188@sopwith.UUCP>
Date: 29 May 89 19:00:29 GMT
References: <8123@phoenix.Princeton.EDU> <172@sopwith.UUCP> <30752@bu-cs.BU.EDU>
Reply-To: snoopy@sopwith.UUCP (Snoopy)
Distribution: usa
Organization: The Daisy Hill Puppy Farm
Lines: 27

In article <30752@bu-cs.BU.EDU> bzs@bu-cs.BU.EDU (Barry Shein) writes:

|> There is also a need for a standard auxiliary output.  stderr is often
|> pressed into service for non-error output.  I claim that this is a bad
|> thing.

| I think we're missing the spirit here and getting too literal minded
| (ie. that some messages sent to stderr aren't errors, that isn't
| exactly why it was called stderr.)

Okay, Barry, why *is* it called stderr then?

| It would probably be better to just write programs to use some sort of
| character tag at the beginning so you could de-mux the different types
| of messages at the other end with grep rather than reworking all of
| Unix to solve this problem.

I think *you* are missing the point.  One of the big wins of Unix is that it
imposes no structure on data, everything is a stream of bytes.  Yes, putting
in an 'error' (or whatever) tag is a useful technique at times, (and I
have done this myself) but requiring one to be used isn't 'the Unix way'.

    _____     						  .-----.
   /_____\    Snoopy					./  RIP	 \.
  /_______\   qiclab!sopwith!snoopy			|  	  |
    |___|     parsely!sopwith!snoopy			| tekecs  |
    |___|     sun!nosun!illian!sopwith!snoopy		|_________|