Path: utzoo!attcan!uunet!seismo!sundc!pitstop!sun!thetone!swilson
From: swilson%thetone@Sun.COM (Scott Wilson)
Newsgroups: comp.lang.c
Subject: Re: Getchar w/wout echo
Message-ID: <66260@sun.uucp>
Date: 30 Aug 88 19:49:29 GMT
References: <371@marob.MASA.COM> <65071@sun.uucp> <624@proxftl.UUCP> <731@ncrcce.StPaul.NCR.COM>
Sender: news@sun.uucp
Reply-To: swilson@sun.UUCP (Scott Wilson)
Organization: Sun Microsystems, Mountain View
Lines: 20

In article <731@ncrcce.StPaul.NCR.COM> mercer@ncrcce.StPaul.NCR.COM (Dan Mercer) writes:
>Terminal echo is a function provided by the
>operating system (in this case,  UNIX(tm)).

Who said we were talking about UNIX?  Again, for the nth time, the environment
in question is THINK's Lightspeed C 3.0 running on a Macintosh under MacOS.
There are no terminals, terminal drivers, terminal emulation windows, stty,
or ioctl's.  Any terminal emulation is provided by the C runtime libraries.

Under UNIX, echoing clearly falls under the realm of the operating system
and it would be wrong for a language to specify something that it can't
or shouldn't control.  I think the real question is that in abscence of OS
support for terminals (or interactive input) should the C environment be
forced to provide a "normal" input mechanism including echoing and maybe
primitive line editing.

--
Scott Wilson		arpa: swilson@sun.com
Sun Microsystems	uucp: ...!sun!swilson
Mt. View, CA