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,
	loren.williams@lycos.com, nobody@gcc.gnu.org, paolo@gcc.gnu.org
Subject: Re: c++/10444: ifstream.peek() can remove a character from the input file stream
Date: Sun, 20 Apr 2003 10:34:00 -0000	[thread overview]
Message-ID: <20030420103403.27909.qmail@sources.redhat.com> (raw)

Synopsis: ifstream.peek() can remove a character from the input file stream

Responsible-Changed-From-To: unassigned->paolo
Responsible-Changed-By: paolo
Responsible-Changed-When: Sun Apr 20 10:34:03 2003
Responsible-Changed-Why:
    Triaged.
State-Changed-From-To: open->closed
State-Changed-By: paolo
State-Changed-When: Sun Apr 20 10:34:03 2003
State-Changed-Why:
    Not a bug. The problem is not with peek() but, honestly, 
    with your understanding of operator>>(char&): at variance
    with get(), it skips any initial whitespace before
    extracting the char. In fact, changing onegm.txt to:
    A_______0.0856
    B_______0.0139
    C_______0.0279
    leads to the behaviour that you expect.
    Thanks for your report, Paolo. 

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


             reply	other threads:[~2003-04-20 10:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-20 10:34 paolo [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-04-20  9:06 loren.williams

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=20030420103403.27909.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=loren.williams@lycos.com \
    --cc=nobody@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).