Path: utzoo!utgpu!watmath!att!tut.cis.ohio-state.edu!cs.utexas.edu!csd4.csd.uwm.edu!uxc.cso.uiuc.edu!uxc.cso.uiuc.edu!ux1.cso.uiuc.edu!uxe.cso.uiuc.edu!mcdonald
From: mcdonald@uxe.cso.uiuc.edu
Newsgroups: comp.lang.c
Subject: Re: ReadKey like Function in C
Message-ID: <225800206@uxe.cso.uiuc.edu>
Date: 14 Aug 89 13:38:00 GMT
References: <148@trigon.UUCP>
Lines: 51
Nf-ID: #R:trigon.UUCP:148:uxe.cso.uiuc.edu:225800206:000:2001
Nf-From: uxe.cso.uiuc.edu!mcdonald    Aug 14 08:38:00 1989


/* Written 11:05 pm  Aug 12, 1989 by scs@adam.pika.mit.edu in uxe.cso.uiuc.edu:comp.lang.c */
In article <13446@bloom-beacon.MIT.EDU> scs@pika.mit.edu 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.

Posix fooey!!!!!! Posix is a standard for one and only one OS, not
a language standard. IT WILL BE OF ZERO repeat ZERO utility. Let's
get this straight:

FLAME ON!!   FLAME ON!! FLAME ON!!!

What is needed is a language standard, in the C standard, in the Fortran
standard, in the Pascal standard, in the A.. (oops, that's already too big,
besides it may already be there with the kitchen sink). Standardization
on one OS is NOT what is needed!!!!!!! For example it ALREADY is
standard on MSDOS. 

The language standards need some construct equivalent to what getch()
and kbhit() do on MSDOS. 

This MUST be IN THE LANGUAGE STANDARD!!!!!! It MUST MUST MUST be there
(do you begin to feel the flame???) to FORCE vendors to, if necessary,


************************************

FIX THEIR OPERATING SYSTEMS SO IT WILL WORK

************************************

Flame off. A mode flag to make getchar behave like getch would be
OK, but some new function like kbhit() would still be needed.

The exact name of the functions is of course not really important, except
that getch is already common.

Please note that there are things in the new Fortran standard that
will require some vendors to fix their OS's - like long global
names.

I do not speak for any vendor, merely as a frustrated user.

Doug McDonald