Date: Thu, 8 Apr 1999 11:57:54 -0400
Message-Id: <199904081557.LAA13267@envy.delorie.com>
From: DJ Delorie <dj AT delorie DOT com>
To: eliz AT is DOT elta DOT co DOT il
CC: djgpp-workers AT delorie DOT com
In-reply-to: <Pine.SUN.3.91.990408113334.29868R-100000@is> (message from Eli
	Zaretskii on Thu, 8 Apr 1999 11:34:02 +0200 (IST))
Subject: Re: v2.03 release: what else has to be done?
References:  <Pine DOT SUN DOT 3 DOT 91 DOT 990408113334 DOT 29868R-100000 AT is>
Reply-To: djgpp-workers AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


> > I'd like to decide what to do about fflush(stdin) for this release.
> > The silent failures generate FAQs; I'd prefer less FAQs.
> 
> I'm not sure that the cause is fflush itself.  People who ask these
> questions don't call fflush just for the sake of it; they do something
> else after calling fflush, and *that* is the part which doesn't work
> and that triggers questions.

I'd prefer that fflush(stdin) issue a warning, perhaps something like this:

Warning: fflush() doesn't flush input streams, nor should it.
         Perhaps you want scanf("%*[^\n]\n") instead ?