Path: utzoo!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!caen!news.cs.indiana.edu!arizona.edu!arizona!gmt
From: gmt@cs.arizona.edu (Gregg Townsend)
Newsgroups: comp.lang.c
Subject: Re: Keyboard support in C (was Re: making charact
Message-ID: <568@coatimundi.cs.arizona.edu>
Date: 3 Mar 91 05:48:50 GMT
References: <1991Feb23.170142.538@ux1.cso.uiuc.edu> <15302@smoke.brl.mil> <14542@ganymede.inmos.co.uk> <1213@airs.UUCP>
Sender: news@cs.arizona.edu
Organization: University of Arizona, Tucson
Lines: 17

In article <1213@airs.UUCP> airs!ian@uunet.uu.net (Ian Lance Taylor) writes:
>
> In the set of ANSI C libraries I wrote for the Alpha Micro, opening a
> terminal in unbuffered mode returns single characters without waiting
> for a carriage return.  I don't know whether UNIX libraries work this
> way or not, but is there any reason they couldn't or shouldn't?

Good for you.  That is a valid and very useful interpretation of the
language in the ANSI specification, though I don't know if the ANSI
committee thought of it.  The ANSI spec, of necessity, is loose enough
to allow other interpretations including doing nothing, and as far as
I know that's the easy path that's been chosen by all Unix vendors.
(It's tricky to do "right", by which I mean ensuring that the tty modes
aren't changed permanently.)

    Gregg Townsend / Computer Science Dept / Univ of Arizona / Tucson, AZ 85721
    +1 602 621 4325     gmt@cs.arizona.edu     110 57 16 W / 32 13 45 N / +758m