🚀 go-pugleaf

In article <4ku3id$53h@solutions.solon.com>, c2a192@ugrad.cs.ubc.ca
(Kazimir Kylheku) writes:
> In article <4ksjpn$rjt@solutions.solon.com>,
> Himanshu Gohel <gohel@csee.usf.edu> wrote:
>> My question is, why?  Some of my students have written programs using
>> fflush(stdin) hoping it would clear away anything that's in the input
>> buffer before a scanf() statement and apparently it works on some PC
>> based compilers, but when re-compiled on a UNIX system, it does not
>> always work.
> 
> There is a detailed discussion in the comp.lang.c FAQ that
> covers VMS, UNIX and DOS in this respect, as far as I recall.

Before anyone goes off and looks and is disappointed (actually,
it's probably too late for that), the only system-specific
question that the comp.lang.c FAQ list answers in that much
detail is, "How do I read one character without waiting for
the RETURN key?".  To the implicit followon question, "If
fflush(stdin) won't work, how *can* I flush the user's typeahead
before issuing a prompt confirming whether I should reformat the
hard drive?", the FAQ list suggests no answer, because I don't
know a good one (other than, your program probably shouldn't be
offering to do that at all).

					Steve Summit
					scs@eskimo.com