This is the mail archive of the libstdc++@gcc.gnu.org mailing list for the libstdc++ project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]

Re: [v3] Fix stringbuf handling of NUL characters

To: Phil Edwards <pedwards at disaster dot jaj dot com>
Subject: Re: [v3] Fix stringbuf handling of NUL characters
From: Carlo Wood <carlo at alinoe dot com>
Date: Sat, 14 Jul 2001 02:49:39 +0200
Cc: Gabriel Dos Reis <Gabriel dot Dos-Reis at cmla dot ens-cachan dot fr>, Andrew Snare <ASnare at allshare dot nl>, libstdc++ at gcc dot gnu dot org, gcc-patches at gcc dot gnu dot org, Mathew Pitchforth <mathew at pandromeda dot com>
References: <5.1.0.14.0.20010712093301.0409cb80@10.1.3.1> <flbsmqv980.fsf@sel.cmla.ens-cachan.fr> <20010712161504.C25863@disaster.jaj.com> <flofqpqq55.fsf@sel.cmla.ens-cachan.fr> <20010713162423.A684@disaster.jaj.com>

On Fri, Jul 13, 2001 at 04:24:23PM -0400, Phil Edwards wrote:
> But that's not c_str()'s fault.  Both c_str() and data() simply return a
> pointer to the character string.  A second NUL character (which will never
> be seen) won't make any difference.
> 
> It's just occurred to me that we may be talking about different things
> anyhow.  :-)

It irrelevant for the patch anyway, you should use data() if only because
it is faster.

-- 
Carlo Wood <carlo@alinoe.com>

Follow-Ups:
- Re: [v3] Fix stringbuf handling of NUL characters
  - From: Phil Edwards

References:
- Re: [v3] Fix stringbuf handling of NUL characters
  - From: Andrew Snare
- Re: [v3] Fix stringbuf handling of NUL characters
  - From: Gabriel Dos Reis
- Re: [v3] Fix stringbuf handling of NUL characters
  - From: Phil Edwards
- Re: [v3] Fix stringbuf handling of NUL characters
  - From: Gabriel Dos Reis
- Re: [v3] Fix stringbuf handling of NUL characters
  - From: Phil Edwards

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]