Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!sharkey!rjf001!hpftc!teemc!rphroy!edsews!uunet!ginosko!husc6!bu-cs!buengc!bph
From: bph@buengc.BU.EDU (Blair P. Houghton)
Newsgroups: comp.std.c
Subject: Re: ReadKey like Function in C
Message-ID: <3727@buengc.BU.EDU>
Date: 12 Aug 89 16:56:28 GMT
References: <148@trigon.UUCP> <207600029@s.cs.uiuc.edu> <941@lakesys.UUCP> <21175@cup.portal.com> <3705@buengc.BU.EDU> <10712@smoke.BRL.MIL>
Reply-To: bph@buengc.bu.edu (Blair P. Houghton)
Followup-To: comp.std.c
Organization: Boston Univ. Col. of Eng.
Lines: 25

In article <10712@smoke.BRL.MIL> gwyn@brl.arpa (Doug Gwyn) writes:
>In article <3705@buengc.BU.EDU> bph@buengc.bu.edu (Blair P. Houghton) writes:
>>How about if someone begs with the ANSI committee to have its
>>implementation as a standard function required for compliance?
>
>Not only is it too late, but I think it was proposed and justly was
>awarded a "VE" stock response code, meaning:  The Standard must
>accommodate a variety of environments.

I don't get it.

All it's gotta say is something to the effect that there should
be a function, call it "readkey()", that returns the value of
the next char from stdin as soon after it's typed as it's needed.
You could even qualify it to apply only when tty input can be
used as stdin.

The Compiler writers are in a much better position to implement
it than are a bunch of fractious C programmers arguing over
whether to use fstat() or ioctl() and the length of timeout()...

Makes me wonder why they haven't, ANSI or no.

				--Blair
				  "ANSI or no."