public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/52169] the ifstream readsome() method does not signal any bit on eof.
Date: Wed, 08 Feb 2012 10:57:00 -0000	[thread overview]
Message-ID: <bug-52169-4-NTwwgBHzTI@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-52169-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52169

Jonathan Wakely <redi at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|                            |INVALID

--- Comment #4 from Jonathan Wakely <redi at gcc dot gnu.org> 2012-02-08 10:56:18 UTC ---
(In reply to comment #1)
> cplusplus.com is (a) not authoritative, (b) full of mistakes, and (c) otherwise
> just awful.

This, x 1000

(In reply to comment #2)
> i.e. doesn't readsome become a noop when there's nothing to read?

Yes, which makes it very useful for non-blocking reads from pipes or sockets.

The testcase is simply wrong, as you can see by checking in_avail:

    cerr << "avail: " << f.rdbuf()->in_avail() << endl;

Since in_avail() doesn't return -1, readsome should not set eofbit.

There are better ways to read a whole file anyway, e.g. ostr << f.rdbuf()


      parent reply	other threads:[~2012-02-08 10:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-08 10:31 [Bug libstdc++/52169] New: " viriketo at gmail dot com
2012-02-08 10:40 ` [Bug libstdc++/52169] " tom at kera dot name
2012-02-08 10:46 ` tom at kera dot name
2012-02-08 10:53 ` viriketo at gmail dot com
2012-02-08 10:57 ` redi at gcc dot gnu.org [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-52169-4-NTwwgBHzTI@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).