This is the mail archive of the
libstdc++@gcc.gnu.org
mailing list for the libstdc++ project.
Re: Specializations of std::char_traits
- From: Gabriel Dos Reis <gdr at integrable-solutions dot net>
- To: Matt Austern <austern at apple dot com>
- Cc: Nathan Myers <ncm-nospam at cantrip dot org>, libstdc++ at gcc dot gnu dot org
- Date: 16 Jul 2003 23:29:06 +0200
- Subject: Re: Specializations of std::char_traits
- Organization: Integrable Solutions
- References: <FF056C2B-B7D2-11D7-B9AA-000393B2ABA2@apple.com>
Matt Austern <austern@apple.com> writes:
| (4) We should support this usage even in the absence of a change to the
| standard. Rationale: it was supported in 3.1. I simply can't see
| any way in which it's doing users a favor to take away something
| that used to work for them and that still works on every other
We may use a suggestion made on the the LWG reflector: define
char_traits as
template<typename charT>
struct char_traits : __gnu_cxx::char_traits<charT> { };
Users can specialize __gnu_cxx::char_traits<> at will on fundamental
types. We may provide a definition for the primary template
__gnu_cxx::char_traits<>. This we don't create the confusion that
users can specialize std::templates on fundamental types.
Comments?
-- Gaby