Article View: gnu.g++.lib.bug
Article #383out << flush v. out.flush()
From: Jason Merrill
Date: Mon, 14 Dec 1992 18:56
Date: Mon, 14 Dec 1992 18:56
6 lines
709 bytes
709 bytes
ostream& ostream::flush() and ostream& flush(ostream &) do different things; the first one discards everything which hasn't been output, while the second spits it all out. Are both the correct behavior? -- Jason Merrill jason@jarthur.claremont.edu
Technical Details
Message-ID:
<JASON.92Dec14135638@it.claremont.edu>Path:
arc1-ca.pugleaf.net!sparky!uunet!elroy.jpl.nasa.gov!swrinde!zaphod.mps.ohio-state.edu!cis.ohio-state.edu!jarthur.claremont.edu!jasonShow Full Headers
Complete Article Headers
Newsgroups: gnu.g++.lib.bug Path: arc1-ca.pugleaf.net!sparky!uunet!elroy.jpl.nasa.gov!swrinde!zaphod.mps.ohio-state.edu!cis.ohio-state.edu!jarthur.claremont.edu!jason From: jason@jarthur.claremont.edu (Jason Merrill) Subject: out << flush v. out.flush() Message-ID: <JASON.92Dec14135638@it.claremont.edu> Sender: gnulists@ai.mit.edu Organization: Minimal Distribution: gnu Date: Mon, 14 Dec 1992 18:56:38 GMT Approved: bug-lib-g++@prep.ai.mit.edu Lines: 7