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: "B. Kosnik" <bkoz at nabi dot net>
- Cc: libstdc++ at gcc dot gnu dot org
- Date: 17 Jul 2003 17:28:37 +0200
- Subject: Re: Specializations of std::char_traits
- Organization: Integrable Solutions
- References: <20030717101117.53573190.bkoz@nabi.net>
"B. Kosnik" <bkoz@nabi.net> writes:
| > On the contrary, I think it does matter. int_type is supposed to be
| > provided by char_traits<>. Nobody knows whether it is used by users
| > only with iostreams. Either we provide something consistent or we don't
| > provide a definition at all.
|
| Ditto for state_type. I don't see how a truly generic char_traits can be
| done with one template parameter: I'd think (at least) three would be
| necessary.
Yeah, I thought about that too -- based on your recent changes to
pod_char_traits. To be honest, I don't have any favorite (and I think
I can be convinced for one way or the other :-).
I also thought about using a decoupled external traits like
template<typename CharT>
struct int_type {
// ...
};
template<typename CharT>
struct state_type {
// ...
};
-- Gaby