🚀 go-pugleaf

Alex Martelli (martelli@cadlab.it) wrote:
: Trying to explain to a newbie how to do input by whole lines in C++,
: the way they easily used to do it with fgets in bad ol' C, I got bit
: (besides a bug in the libg++ implementation of getline(), which just
: points to some obscurity between the standard libraries' usages of
: length/size/capacity for strings -- obscurity enough to confuse the
: implementor) by a gotcha in the standard itself:
[snip]
: Why the gratuitous spec to setstate(failbit), even possibly to throw!,
: for something as innocuous as an empty line (i.e., just the terminating
While brousing the draft standard/working papers I found a
footnote (This is in the WWW/HTML version, lib-iostreams....)
  29) This implies an empty input line will not cause failbit to be set.

--
	dick@csci.csusb.edu=rbotting@wiley.csusb.edu.
Find out what's new at http://www.csci.csusb.edu/doc/www.sites.html
Disclaimer:`CSUSB may or may not agree with this message`.
Copyright(1995):Copy this freely but include the following link to the
<a href="http://www.csci.csusb.edu/dick/signature.html">author's signature</a>
---
[ comp.std.c++ is moderated.  Submission address: std-c++@ncar.ucar.edu.
  Contact address: std-c++-request@ncar.ucar.edu.  The moderation policy
  is summarized in http://dogbert.lbl.gov/~matt/std-c++/policy.html. ]