home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!kithrup!hoptoad!pacbell.com!mips!swrinde!zaphod.mps.ohio-state.edu!rpi!newsserver.pixel.kodak.com!laidbak!tellab5!vpnet!serveme!tallboy!news
- From: pynq@midway.uchicago.edu (George Jetson)
- Newsgroups: comp.unix.bsd
- Subject: Report small bug (?) in GO32
- Message-ID: <9208172142.AA18831@midway.uchicago.edu>
- Date: 17 Aug 92 21:42:57 GMT
- Sender: news@tallboy.chi.il.us
- Lines: 13
-
- I did something like:
-
- go32 foo bar bletch > outfile
-
- and it exited quickly back to the the DOS prompt (it should have run for
- awhile). Turned out that I had forgotten to set GCCTMP, and it could
- not open the swap file. However, the msg to that effect ended up in
- OUTFILE. I suggest that GO32 error msgs go to stderr, not stdout.
-
- Actually, a case can be made that they should just be blasted
- to the terminal (something like to "CON" [In Unixese, /dev/tty]),
- since at this point, your program has not even run (it might want
- to have exclusive control over the contents of the stderr stream)
-