public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Paolo Carlini <pcarlini@unitus.it> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: libstdc++/4433 Date: Thu, 15 Nov 2001 10:06:00 -0000 [thread overview] Message-ID: <20011120083601.1667.qmail@sourceware.cygnus.com> (raw) The following reply was made to PR libstdc++/4433; it has been noted by GNATS. From: Paolo Carlini <pcarlini@unitus.it> To: gcc-gnats@gcc.gnu.org, gcc-bugs@gcc.gnu.org, nobody@gcc.gnu.org Cc: Subject: Re: libstdc++/4433 Date: Tue, 20 Nov 2001 09:29:17 +0100 Hi, I think that the behaviour you are reporting is not a bug. I suggest you to confer to page 634 of Josuttis (ISBN 0-201-379-260) where it is stated that "this value (that reported by tellp/tellg) is *not* an integral value or simply the position of the character as an index". So, in general, it *cannot* be directly compared with the parameter given to a preceding seekp/seekg. In particular, the values returned by tellp/tellg after a relative seek (which you are using) may *differ* if you referred the seek to beg, cur, or end. Even if some implementations happen to pass your test this does not mean that all the implementations have to pass it to be conforming (in fact among the 5 or 6 I have tried more than half of them do *not* pass it) Personally, I prefer to use either only relative seeks, or absolute seeks and tells (according to the scheme explained, f.i., in Langer/Kreft (ISBN 0-201-18395-1)), never a mix. Cheers, Paolo Carlini. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=4433&database=gcc
reply other threads:[~2001-11-20 8:36 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20011120083601.1667.qmail@sourceware.cygnus.com \ --to=pcarlini@unitus.it \ --cc=gcc-prs@gcc.gnu.org \ --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: linkBe 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).