Xref: utzoo comp.windows.ms.programmer:2200 comp.os.msdos.programmer:4995
Path: utzoo!utgpu!cunews!bnrgate!bwdls58!mlord
From: mlord@bwdls58.bnr.ca (Mark Lord)
Newsgroups: comp.windows.ms.programmer,comp.os.msdos.programmer
Subject: Re: What to do about stdin, stdout, and stderr under Windows 3.0?
Keywords: Missing in action
Message-ID: <6690@bwdls58.bnr.ca>
Date: 3 May 91 14:37:09 GMT
References: <1991Apr30.162028.7771@sq.sq.com>
Sender: mlord@bwdls58.bnr.ca
Reply-To: mlord@bwdls58.bnr.ca (Mark Lord)
Organization: Bell-Northern Research, Ottawa, Canada
Lines: 7

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.)

There is a device called NUL for use in the PC world.  NUL == /dev/null