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. I mean, the less work there's for you to do, the better, right? Especially if it's something as rudimentary as strings. You may argue that hey, it's not the job of STD to do such things. But then people just reimplement them everywhere. Just look around and see how many codec libraries (some of them buggy!) are there. Almost every major i18able project has one, or at least has some serious wrappers to other code. Heck, even pure-php projects have them (c.f. squirrelmail). One wishes there was one standard implementation. At least if you use Qt you don't have to look for it elsewhere, which I think is cool. Kuba
