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

On Fri, May 1, 2009 at 9:35 AM, Dominique Devienne wrote:

On Fri, May 1, 2009 at 9:22 AM, Etienne Philip Pretorius wrote:

...

namespace unicode {    typedef std::size_t code_point;    class string : public std::basic_string {

Is "std::basic_string" 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

Wouldn't then the OP rather use uint32_t or similar? I thought that int represented the natural word size of the architecture. If so, then wouldn't unsigned int be 64-bit on a 64-bit platform as well? Or did I miss something? -- Dan Day