Xref: utzoo comp.windows.ms.programmer:2162 comp.sys.ibm.pc.programmer:2671
Newsgroups: comp.windows.ms.programmer,comp.sys.ibm.pc.programmer
Path: utzoo!utgpu!news-server.csri.toronto.edu!torsqnt!geac!sq!dak
From: dak@sq.sq.com (David A Keldsen)
Subject: What to do about stdin, stdout, and stderr under Windows 3.0?
Message-ID: <1991Apr30.162028.7771@sq.sq.com>
Summary: I can avoid them, but what do you do?
Keywords: Missing in action
Organization: SoftQuad Inc., Toronto, Canada
Date: Tue, 30 Apr 91 16:20:28 GMT
Lines: 16

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