Re: [Boost-users] General C++: Class Method Signatures Miss-Match

Subject: Re: [Boost-users] General C++: Class Method Signatures Miss-Match
From: Dominique Devienne (ddevienne_at_[hidden])
Date: 2009-05-01 10:35:34

On Fri, May 1, 2009 at 9:22 AM, Etienne Philip Pretorius
<icewolfhunter_at_[hidden]> wrote:
> namespace unicode {
>    typedef std::size_t code_point;
>    class string : public std::basic_string<code_point> {
>
> Is "std::basic_string<unsigned int, std::char_traits<unsigned int>,
> std::allocator<unsigned int> >" not the same as "unicode::string"? If not
> why is it not?

Not strictly related to your question, but Unicode code points use a
maximum of 21 bits currently (max code point is 0x0010FFFF), and are
unlikely to ever overflow a 32-bit integer. Whereas size_t will be
64-bit when compiling for a 64-bit architecture, so you want to
typedef unicode::code_point to unsigned int anyway. --DD