Xref: utzoo comp.windows.ms.programmer:2164 comp.os.msdos.programmer:4967 Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!swrinde!cs.utexas.edu!asuvax!ukma!dftsrv!oneel From: oneel@heawk1.rosserv.gsfc.nasa.gov ( Bruce Oneel ) Newsgroups: comp.windows.ms.programmer,comp.os.msdos.programmer Subject: Re: What to do about stdin, stdout, and stderr under Windows 3.0? Message-ID: Date: 1 May 91 12:41:13 GMT References: <1991Apr30.162028.7771@sq.sq.com> Sender: news@dftsrv.gsfc.nasa.gov Organization: STX/GSFC Nasa Lines: 31 In-reply-to: dak@sq.sq.com's message of 30 Apr 91 16:20:28 GMT In article <1991Apr30.162028.7771@sq.sq.com> dak@sq.sq.com (David A Keldsen) writes: On reading through the includes for the SDK, I see that std{in,out,err} are not supported under Windows. While this isn't entirely surprising, what do you do to substitute for them? (On Unix, I'd consider opening /dev/null, but there isn't one that I can find for DOS/MS-WINDOWS.) Please reply by email; I'll post a summary if there is enough interest. (Ah, the joys of porting code. The rambling through the fields of bits, stumbling over segments...) Dak -- David A. 'Dak' Keldsen of SoftQuad, Inc. email: dak@sq.com phone: 416-963-8337 "Anyway, you shouldn't believe everything you read in the Classics," Rincewind added. "They never check their facts. They're just out to sell legends." -- _Eric_ by Terry Pratchett Uh, not to be silly, but don't use them. But, in the next issue of Tech Specialist they will have a package to replace stdio in c under windows 3.0 so that you can write and read from windows. This from some kind net person. bruce -- | Bruce O'Neel | internet : oneel@heasfs.gsfc.nasa.gov| | Code 664/STX | span : lheavx::oneel | | NASA/GSFC Bld 28/W281 |compuserve: 72737,1315 | | Greenbelt MD 20771 | AT&Tnet : (301)-286-4585 | Thats me in the corner, thats me in the spotlight, losin' my religion -- rem