From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14048 invoked by alias); 20 Nov 2002 16:46:07 -0000 Mailing-List: contact gcc-prs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-prs-owner@gcc.gnu.org Received: (qmail 13994 invoked by uid 71); 20 Nov 2002 16:46:05 -0000 Date: Thu, 28 Nov 2002 15:03:00 -0000 Message-ID: <20021120164605.13987.qmail@sources.redhat.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, From: Wolfgang Bangerth Subject: Re: libstdc++/8655: Problematic behaviour of std::ends Reply-To: Wolfgang Bangerth X-SW-Source: 2002-11/txt/msg01122.txt.bz2 List-Id: The following reply was made to PR libstdc++/8655; it has been noted by GNATS. From: Wolfgang Bangerth To: gcc-bugs@gcc.gnu.org, , Ioannis Papadopoulos 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