Kuba Ober <[EMAIL PROTECTED]> writes:
| On czwartek 09 grudzień 2004 10:42 am, Lars Gullik Bjønnes wrote:
>> Kuba Ober <[EMAIL PROTECTED]> writes:
>> >> Are you sure of this. I know that the std::string in libstdc++ has
>> >> gotten quite a bit of performance tweaks lately.
>> >> (gcc 3.4.x and 4.x)
>> |
>> | So they finally play catch up with Qt. Nice :)
>> |
>> | Even then, it's essentially just a dumb container. You'd expect something
>> | more of a useful string implementation. Afaik std::string doesn't have
>> | from8BitLocal(), fromUcs(), etc.
>>
>> Why should it?
>
| Because in real life applications you typically don't just look at a
container
| of characters. You need conversion functions etc. just to interface with the
| real world out there, and in the best case you'll need to find, intall, test
| and use a 3rd party library. Which library might well not use std::string but
| char*, and so on. So you write some "trivial" wrappers. And waste some time
| to maintain them later. With Qt, you get the whole deal.
And all those extra member functions could just as well be separate
functions.
It seems that even the std::string is now considered too fat. Most of
what it does is possible to implement outside of the class.
So I am not argueing against functions that operate on strings. I am
argueing against the functions being part of the class.
--
Lgb
