Xref: utzoo comp.std.c:1516 comp.lang.c:20645 Path: utzoo!attcan!uunet!tut.cis.ohio-state.edu!bloom-beacon!adam.pika.mit.edu!scs From: scs@adam.pika.mit.edu (Steve Summit) Newsgroups: comp.std.c,comp.lang.c Subject: Re: ReadKey like Function in C Message-ID: <13456@bloom-beacon.MIT.EDU> Date: 13 Aug 89 04:05:03 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> <13446@bloom-beacon.MIT.EDU> <1989Aug13.004829.28322@utzoo.uucp> Sender: daemon@bloom-beacon.MIT.EDU Reply-To: scs@adam.pika.mit.edu (Steve Summit) Lines: 24 In article <13446@bloom-beacon.MIT.EDU> I wrote: >...the astonishing frequency with which this >question arises indicates that the opportunity is >ripe for some kind of informal, community-"standard" solution. In article <1989Aug13.004829.28322@utzoo.uucp> henry@utzoo.uucp (Henry Spencer) writes: >I strongly suggest that you read IEEE standard 1003.1, i.e. POSIX, before >re-inventing the wheel pointlessly. POSIX compliance will be widespread >in the very near future, so the POSIX approach will automatically be >*far* more widespread than any "community 'standard'" approach. I agree (in fact I have a copy of 1003.1 right here on my desk) and I'll start using its facilities as soon as they become available on machines I use, but in the meantime, and for non-Unix systems such as VMS and MS-DOS, I'd like to have a carrot to toss to the people who keep asking for getch() and kbhit(), in a similar spirit to the getopt() routines which have been floating around for years. You're right, the time for a "community 'standard'" approach is not exactly ripe, but more like waning. Steve Summit scs@adam.pika.mit.edu