Date: Sun, 11 Apr 1999 13:05:41 -0400
Message-Id: <199904111705.NAA01422@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.990411192721.21838A-100000@is> (message from Eli
	Zaretskii on Sun, 11 Apr 1999 19:28:09 +0300 (IDT))
Subject: Re: v2.03 release: what else has to be done?
References:  <Pine DOT SUN DOT 3 DOT 91 DOT 990411192721 DOT 21838A-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 prefer that fflush(stdin) issue a warning
> 
> I gather that we do NOT want this warning to be issued when they call 
> `fflush' with a NULL as argument, right?

Right.  If fflush is passed a single stream, and it's a read-only
stream (like stdin), issue a warning (once!  Set a flag to prevent
multiple warnings).

Note: I tried adding this, but there's a lot of places in libc where
we blindly call fflush() on streams (rewind is one), so if we do put
in a warning we'll have to be extra careful about other calls to
fflush, or provide a _fflush that doesn't check for read-only streams.