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: char_traits patch, round two

From: Benjamin Kosnik <bkoz at redhat dot com>
To: Gabriel Dos Reis <gdr at integrable-solutions dot net>
Cc: pthomas at suse dot de, aj at suse dot de, libstdc++ at gcc dot gnu dot org, ro at suse dot de
Date: Mon, 12 Aug 2002 09:51:40 -0700
Subject: Re: char_traits patch, round two
Organization: Red Hat / San Francisco
References: <200207290741.g6T7f7X26915@fillmore.constant.com><hod6somizg.fsf@gee.suse.de><m3bs88xpmj.fsf@soliton.integrable-solutions.net><20020812161433.GA29776@jeffreys.suse.de><m33ctkvxno.fsf@soliton.integrable-solutions.net>

> The standard does not have direct support for strings expressed as
> arrays of "unsigned char".  

Yep. The standard only specifies char and wchar_t specializations for
std::char_traits.

The correct way to deal with this now is to explicitly specialize
std::char_traits for user-defined types. That's always been the correct
way to deal with this, but the generic-mostly-correct definitions that
were previously in place allowed people to be lazy.

No more. 

-benjamin

Follow-Ups:
- Re: char_traits patch, round two
  - From: Martin Sebor
- Re: char_traits patch, round two
  - From: Andreas Jaeger

References:
- Re: char_traits patch, round two
  - From: Andreas Jaeger
- Re: char_traits patch, round two
  - From: Gabriel Dos Reis
- Re: char_traits patch, round two
  - From: Philipp Thomas
- Re: char_traits patch, round two
  - From: Gabriel Dos Reis

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