This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug libstdc++/15276] Erroneous Comparisons of Negative Characters
- From: "gdr at integrable-solutions dot net" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 5 May 2004 10:38:48 -0000
- Subject: [Bug libstdc++/15276] Erroneous Comparisons of Negative Characters
- References: <20040504045136.15276.mckelvey@maskull.com>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Additional Comments From gdr at integrable-solutions dot net 2004-05-05 10:38 -------
Subject: Re: Erroneous Comparisons of Negative Characters
"pcarlini at suse dot de" <gcc-bugzilla@gcc.gnu.org> writes:
| Admittedly, I become nervous when someone consider changing from one
I see a difference with being "nervous" and "being rude" for the
purpose of "intimidating". IMNSHO, you've been lately in the
latter category than the former these months.
| day to another string::compare behavior to become different from
| std::strcmp. Therefore, please accept my excuses for my harsh
| response, but also, please, don't consider the issue simpler than it is.
The issue as I see it is quite simple: The specification in table 37
regarding char_traits<>::compare is clear, and it takes an
extraodinary interpretation to conclude that string::compare
and std::strcmp should match -- let alone the fact that std::string
already differs from traditional C-style strings in the sene that
the former can contain nul characters whereas the later can't.
But, of course, that may be subtle to someone already convinced that a
C++ string is just a typedef-name for a C-string.
-- Gaby
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=15276