public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "elizbus at yahoo dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/40732] fstream get/put pointers have unexpected positions
Date: Mon, 13 Jul 2009 17:24:00 -0000	[thread overview]
Message-ID: <20090713172444.28986.qmail@sourceware.org> (raw)
In-Reply-To: <bug-40732-17936@http.gcc.gnu.org/bugzilla/>



------- Comment #2 from elizbus at yahoo dot com  2009-07-13 17:24 -------
(In reply to comment #1)
> Your assumption is wrong, in the sense that nothing in the Standard mandates it
> (likewise in C, for plain C streams, by the way) and in fact most, if not all,
> current good performing implementation do not satisfy it.

If I were to add a call to tellg() prior to appending additional data to the
stream, the put pointer is now at the correct location and the output file now
has all ten characters written to it, and not five.  If the pointers are
independent, then this should not happen.


-- 


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


  parent reply	other threads:[~2009-07-13 17:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-13 14:23 [Bug libstdc++/40732] New: " elizbus at yahoo dot com
2009-07-13 14:34 ` [Bug libstdc++/40732] " paolo dot carlini at oracle dot com
2009-07-13 17:24 ` elizbus at yahoo dot com [this message]
2009-07-13 19:59 ` paolo dot carlini at oracle dot com

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=20090713172444.28986.qmail@sourceware.org \
    --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).