public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: paolo@gcc.gnu.org
To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org,
	paolo@gcc.gnu.org, pergj@newmad.no
Subject: Re: libstdc++/9657: [3.2/3.3/3.4 regression] Incorrect parsing when using istringstream::str
Date: Tue, 18 Feb 2003 10:01:00 -0000	[thread overview]
Message-ID: <20030218100135.25515.qmail@sources.redhat.com> (raw)

Synopsis: [3.2/3.3/3.4 regression] Incorrect parsing when using istringstream::str

Responsible-Changed-From-To: unassigned->paolo
Responsible-Changed-By: paolo
Responsible-Changed-When: Tue Feb 18 10:01:34 2003
Responsible-Changed-Why:
    Analyzed.
State-Changed-From-To: analyzed->closed
State-Changed-By: paolo
State-Changed-When: Tue Feb 18 10:01:34 2003
State-Changed-Why:
    Not a bug, but behaviour mandated by the standard, now
    implemented correctly. After the first extraction iss.good()
    is false and iss.eof() is true since the end of the string
    is reached during the extraction. Therefore istream::sentry
    blocks the second extraction. User code can be fixed either
    initializing the first time with "1 " (space after 1), or
    clearing the stream state before the second extraction
    (iss.clear()). Thanks for your report, Paolo.
    
    P.S. In fact we _test_ in the testsuite for this behaviour,
    in istringstream_members.cc

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=9657


             reply	other threads:[~2003-02-18 10:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-18 10:01 paolo [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-02-17 23:46 bangerth

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=20030218100135.25515.qmail@sources.redhat.com \
    --to=paolo@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@gcc.gnu.org \
    --cc=pergj@newmad.no \
    /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).