On Wednesday 05 of February 2003 12:17, Jordi wrote:
> As long as a previous thread in this list stated that QString is not the
> most efficient thing in memory and CPU, why don't make i18n return a
> QConstString instead of a QString? I think is a very used function all over
> KDE.
>
> Maybe is needed that the .arg() will make the QConstString QString in order
> to add it the data. But _lots_ of text of KDE don't have .arg() , so it
> will be a gain ,no?

 So, why don't you try it? But given that .po texts are in utf8 AFAIK, and 
therefore need to converted anyway, I fail to see the advantage of using 
QConstString.

-- 
Lubos Lunak
KDE developer
---------------------------------------------------------------------
SuSE CR, s.r.o.  e-mail: l.lunak@suse.cz , l.lunak@kde.org
Drahobejlova 27  tel: +420 2 9654 2373
190 00 Praha 9   fax: +420 2 9654 2374
Czech Republic   http://www.suse.cz/

_______________________________________________
Kde-optimize mailing list
Kde-optimize@mail.kde.org
http://mail.kde.org/mailman/listinfo/kde-optimize