Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ames!ncar!tank!mimsy!chris
From: chris@mimsy.UUCP (Chris Torek)
Newsgroups: comp.lang.c
Subject: Re: learning c
Keywords: getchar()
Message-ID: <16727@mimsy.UUCP>
Date: 4 Apr 89 17:41:54 GMT
References: <1091@bnlux0.bnl.gov> <584@greens.UUCP> <1384@auspex.auspex.com>
Distribution: usa
Organization: U of Maryland, Dept. of Computer Science, Coll. Pk., MD 20742
Lines: 12

In article <1384@auspex.auspex.com> guy@auspex.auspex.com (Guy Harris) writes:
>... flushing input is generally an action taken on an error, not
>something you do as a matter of course unless you want to make *sure*
>somebody hasn't typed something ahead that they'll regret (cf. "rn",
>which does flush input for precisely that reason).

... *and* which provides a flag (-T) to turn off this behaviour!  Some of
us find ignoring input obnoxious.  If you are going to do it, please
make sure there is a way to defeat it as well.
-- 
In-Real-Life: Chris Torek, Univ of MD Comp Sci Dept (+1 301 454 7163)
Domain:	chris@mimsy.umd.edu	Path:	uunet!mimsy!chris