From: Kai <ka...@Ra...> - 2007-06-22 16:10:53
|
Hi, knowing the problem of binary compatibility from=20 hard learned experience, I am very interested in=20 your version_0 approach. And string16_t is one reason more to look at it,=20 because std::wstring is rather unusable due to=20 the different ideas of the size of wchar_t on=20 different platforms/compilers. After a first glance at string[16]_t I have the=20 impression that the functionality is very basic.=20 Nothing against keeping these classes simply and=20 not copying the monolithic design of=20 std::basic_string, but shouldn't there be at=20 least a little bit more? Like concatenation, for=20 instance? What are your plans regarding string[16]_t? Will=20 they stay as they are, which would make them in=20 my opinion more suited for interchange accross=20 module borders and less for use as internal=20 representation? Kai -- Kai Br=FCning RagTime GmbH * http://www.ragtime.de Neustra=DFe 69 * 40721 Hilden * Deutschland Tel: [49](0)2103 9657-0 * Fax: [49](0)2103 9657-96 Sitz der Gesellschaft: Hilden * Amtsgericht D=FCsseldorf HRB 45697 Gesch=E4ftsf=FChrer: Helmut Tschemernjak |