20 Jan
2011
20 Jan
'11
10:53 p.m.
On 01/20/2011 06:33 AM, Chad Nelson wrote:
... elision by patrick ... And string16 and string32? We'll have to support UTF-32, as the single-codepoint-per-element type, and UTF-16 (distasteful though it may be) is needed for Windows. string is already templated on the character type, character traits, and allocator, no? So if you used string with char16_t or char32_t (real types in current C++ specs) you would get them already. You just wouldn't know anything about encoding. Or are you suggesting the utf* types in addition to the boost::string type? If so, I believe the idea has merit. Yay! +1.72
Patrick