Path: utzoo!utgpu!attcan!uunet!lll-winken!lll-tis!ames!pasteur!ucbvax!decwrl!hplabs!motsj1!mcdchg!clyde!watmath!egisin
From: egisin@watmath.waterloo.edu (Eric Gisin)
Newsgroups: comp.lang.c
Subject: Re: Getchar w/wout echo
Message-ID: <20471@watmath.waterloo.edu>
Date: 20 Aug 88 15:34:33 GMT
References: <371@marob.MASA.COM> <65071@sun.uucp>
Organization: U of Waterloo, Ontario
Lines: 18

In article <65071@sun.uucp>, swilson%thetone@Sun.COM (Scott Wilson) writes:
> Again, the system with which I have the problem is THINK's LightspeedC on
> a Macintosh.  No there isn't ioctl(), stty(), fcntl(), terminals,
> terminal emulation windows, or terminal drivers.  Making a window look
> like a terminal is a function of the C libraries.  And, again, the problem is
> that standards like ANSI appear to leave echoing alone because it is an
> OS issue.  My question is how do we get getchars that behave similarly
> on different systems when for some implementations it falls under the
> responsibility of the C libraries because the OS doesn't have terminal
> support.
> 

If the OS doesn't have terminal support,
the C library should support it,
and it should be the *default* for un-redirected stdout/stdin.
If the programmer wants unechoed keyboard input,
they can call non-portable OS functions.
If LightspeedC doesn't work that way,
complain to THINK, or get better compiler.