public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Wolfgang Bangerth <bangerth@ticam.utexas.edu> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: libstdc++/8655: Problematic behaviour of std::ends Date: Thu, 28 Nov 2002 15:03:00 -0000 [thread overview] Message-ID: <20021120164605.13987.qmail@sources.redhat.com> (raw) The following reply was made to PR libstdc++/8655; it has been noted by GNATS. From: Wolfgang Bangerth <bangerth@ticam.utexas.edu> To: gcc-bugs@gcc.gnu.org, <gcc-gnats@gcc.gnu.org>, Ioannis Papadopoulos <Ioannis.Papadopoulos@cern.ch> Cc: Subject: Re: libstdc++/8655: Problematic behaviour of std::ends Date: Wed, 20 Nov 2002 10:49:08 -0600 (CST) Ioannis, This problem is exactly what PR 5735 was about. I found that equally annoying, but apparently gcc2.95 was not standards conforming, and gcc3 is. I work around this by only appending the std::ends when using gcc2.95, using the preprocessor for this. Unfortunately, gcc2.95 needs this since otherwise it will return a non-terminated string, which is of course useless when assigned to a char*. This is one of the more annoying incompatibilities between 2.95 and 3.x :-( Read the audit trail of this report. Regards Wolfgang ------------------------------------------------------------------------- Wolfgang Bangerth email: bangerth@ticam.utexas.edu www: http://www.ticam.utexas.edu/~bangerth
next reply other threads:[~2002-11-20 16:46 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-11-28 15:03 Wolfgang Bangerth [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-11-29 0:10 paolo 2002-11-28 14:49 Ioannis Papadopoulos 2002-11-28 11:16 reichelt 2002-11-28 9:06 paolo 2002-11-28 8:26 Ioannis Papadopoulos 2002-11-28 8:19 paolo 2002-11-28 7:14 Ioannis.Papadopoulos
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=20021120164605.13987.qmail@sources.redhat.com \ --to=bangerth@ticam.utexas.edu \ --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).