public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: paolo@gcc.gnu.org
To: bkoz@redhat.com, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org,
	nobody@gcc.gnu.org, paolo@gcc.gnu.org, peturr02@ru.is
Subject: Re: libstdc++/9439: filebuf::sputbackc ignores beginning-of-file
Date: Sun, 02 Feb 2003 17:38:00 -0000	[thread overview]
Message-ID: <20030202173824.18764.qmail@sources.redhat.com> (raw)

Synopsis: filebuf::sputbackc ignores beginning-of-file

Responsible-Changed-From-To: unassigned->paolo
Responsible-Changed-By: paolo
Responsible-Changed-When: Sun Feb  2 17:38:23 2003
Responsible-Changed-Why:
    Analyzed a bit.
State-Changed-From-To: open->feedback
State-Changed-By: paolo
State-Changed-When: Sun Feb  2 17:38:23 2003
State-Changed-Why:
    Hi. I don't think there is a bug here: I cannot find in the
    standard a specific prescription for the behaviour you
    expect (in particular in 27.5.2.4.4) Can you?
    Indeed, sputbackc calls, as expected, pbackfail, which in turns calls seekoff (fstream.tcc, line 218) (pay attention
    to the preceding comment which means that this specific situation was considered and _not_ supposed to lead to an
    obvious failure). The latter call then does _not_ fail and
    a put back buffer is created by _M_pback_create(), hosting
    the put back char, _exactly as happens_ when __testpb &&
    !__testeof && !__testeq, above. 
    I agree that a few widespread implementations behave
    differently in this case, but we are, I maintain, in the
    realm of implementation defined behaviour.
    
    Paolo.

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


             reply	other threads:[~2003-02-02 17:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-02 17:38 paolo [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-02-05 19:23 paolo
2003-02-03 14:26 Paolo Carlini
2003-02-03 14:06 Pétur Runólfsson
2003-01-25 12:06 peturr02

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=20030202173824.18764.qmail@sources.redhat.com \
    --to=paolo@gcc.gnu.org \
    --cc=bkoz@redhat.com \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@gcc.gnu.org \
    --cc=peturr02@ru.is \
    /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).