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]
Other format:	[Raw text]

Re: [patch] Remove invalid test on non-const empty strings

From: Paolo Carlini <pcarlini at suse dot de>
To: Paolo Carlini <pcarlini at suse dot de>
Cc: Jonathan Wakely <cow at compsoc dot man dot ac dot uk>,Chris Jefferson <caj at cs dot york dot ac dot uk>,libstdc++ <libstdc++ at gcc dot gnu dot org>
Date: Fri, 21 Jan 2005 12:33:55 +0100
Subject: Re: [patch] Remove invalid test on non-const empty strings
References: <41F01164.708@cs.york.ac.uk> <41F049E5.5070604@suse.de> <41F0C528.4070404@cs.york.ac.uk> <41F0D34A.9020001@suse.de> <41F0DC6F.4030002@cs.york.ac.uk> <20050121110654.GE776@compsoc.man.ac.uk> <41F0E433.3030904@suse.de>

Paolo Carlini wrote:

From a practical point of view, this idea goes in the right direction, in
my opinion. Is __GLIBCXX_DEBUG_PEDANTIC meant to catch
"undefined behavior" and "implemention defined behavior" usages?


I'm re-reading now our debug.html (sorry about the sloppiness) and indeed
it looks like the way to go is moving these debug-mode tests under
_GLIBCXX_DEBUG_PEDANTIC.

Paolo.

References:
- [patch] Remove invalid test on non-const empty strings
  - From: Chris Jefferson
- Re: [patch] Remove invalid test on non-const empty strings
  - From: Paolo Carlini
- Re: [patch] Remove invalid test on non-const empty strings
  - From: chris jefferson
- Re: [patch] Remove invalid test on non-const empty strings
  - From: Paolo Carlini
- Re: [patch] Remove invalid test on non-const empty strings
  - From: Chris Jefferson
- Re: [patch] Remove invalid test on non-const empty strings
  - From: Jonathan Wakely
- Re: [patch] Remove invalid test on non-const empty strings
  - From: Paolo Carlini

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