public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "tom at kera dot name" <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:40:00 -0000 [thread overview] Message-ID: <bug-52169-4-PtvLjfhn3I@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 Tomalak Geret'kal <tom at kera dot name> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tom at kera dot name --- Comment #1 from Tomalak Geret'kal <tom at kera dot name> 2012-02-08 10:39:54 UTC --- cplusplus.com is (a) not authoritative, (b) full of mistakes, and (c) otherwise just awful. Instead, we'll quote the standard(s): [C++11: 27.7.2.3]: streamsize readsome(char_type* s, streamsize n); 32/ Effects: Behaves as an unformatted input function (as described in 27.7.2.3, paragraph 1). After constructing a sentry object, if !good() calls setstate(failbit) which may throw an exception, and return. Otherwise extracts characters and stores them into successive locations of an array whose first element is designated by s. If rdbuf()->in_avail() == -1, calls setstate(eofbit) (which may throw ios_base::failure (27.5.5.4)), and extracts no characters; — If rdbuf()->in_avail() == 0, extracts no characters — If rdbuf()->in_avail() > 0, extracts min(rdbuf()->in_avail(),n)). 33/ Returns: The number of characters extracted. [C++03: 27.6.1.3]: streamsize readsome(char_type* s, streamsize n); 30/ Effects: Behaves as an unformatted input function (as described in 27.6.1.3, paragraph 1). After constructing a sentry object, if !good() calls setstate(failbit) which may throw an exception, and return. Otherwise extracts characters and stores them into successive locations of an array whose first element is designated by s. If rdbuf()->in_avail() == -1, calls setstate(eofbit) (which may throw ios_base::failure (27.4.4.3)), and extracts no characters; — If rdbuf()->in_avail() == 0, extracts no characters — If rdbuf()->in_avail() > 0, extracts min(rdbuf()->in_avail(),n)). 31/ Returns: The number of characters extracted.
next prev parent reply other threads:[~2012-02-08 10:40 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 ` tom at kera dot name [this message] 2012-02-08 10:46 ` [Bug libstdc++/52169] " 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
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-PtvLjfhn3I@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: linkBe 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).