Re: Please help with testing & improving a StringValue class
* Barry:
Alf P. Steinbach wrote:
* Alf P. Steinbach:
TESTING:
Could readers please try to sort a large vector and large list of e.g.
BStringValue versus std::string, and report the timings? I'm
suspecting that at least for vector of strings, unoptimized
BStringValue will be significantly faster than a typical heavily
optimized by best experts around std::string. But this is just a
hunch... ;-)
You must forget to test the 'W' streaming of StringValue
change them into basic_ostream.
Not sure what you mean. Wide string streaming operators << and >> are
not provided because MingW g++ 3.4.4 doesn't support wide streams. That
is, MingW g++ 3.4.4 simply does not implement wide streams, e.g. there's
no wcout or wcin, although std::wstring is implemented.
However, narrow string streaming operators (for BStringValue) are
provided, and if the compiler supports wide streams, wide strings
(StringValue) can be streamed out simply by applying the pointer()
member function -- and streaming operators implemented simply by
copying and changing the types for the existing narrow operators.
More generally: when streaming wide character strings using the standard
library streams (no matter whether to/from std::wstring or what), one
should be aware that mostly the result is a not-very-well-defined
conversion to narrow characters. I.e. "wcout << L"hello" << endl" does
not by default result in UTF-16 or some other encoding at the output
end. And the standard library does not offer such encodings.
As far as I know, only the Dinkumware library has reasonable support for
wide character streaming, in the sense of offering the usual Unicode
encoding formats.
It would be nice if e.g. Boost provided this...
Cheers,
- Alf (hoping SomeOne(TM) will do the honors of measuring performance!)