public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "paolo.carlini at oracle dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/49269] wifstream::tellg reports invalid stream position after reading single wchar_t character with NullCodecvt
Date: Sun, 26 Jun 2011 22:30:00 -0000	[thread overview]
Message-ID: <bug-49269-4-PA2alw6av2@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-49269-4@http.gcc.gnu.org/bugzilla/>

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

Paolo Carlini <paolo.carlini at oracle dot com> changed:

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

--- Comment #2 from Paolo Carlini <paolo.carlini at oracle dot com> 2011-06-26 22:30:15 UTC ---
Granted, the Standard leaves quite a bit of room for implementation defined
behavior in this area, but for sure this codecvt is not going to work with our
implementation for what you want (and never did). First, do_always_noconv
returns true, thus you are already screwed, because this implies that all the
other codecvt members will not be used at all. Even if you fix that, do_in
still needs work, because, still according to the standard, if it returns
noconv, it means _To and _E are the same type, something certainly not true
here.


      parent reply	other threads:[~2011-06-26 22:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-02 22:29 [Bug libstdc++/49269] New: " Michael.Kv at gmail dot com
2011-06-26 21:04 ` [Bug libstdc++/49269] " Michael.Kv at gmail dot com
2011-06-26 22:30 ` paolo.carlini at oracle dot com [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-49269-4-PA2alw6av2@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).