QString latin1 comparision

Stephan Kulow coolo at kde.org
Sun Oct 17 18:36:56 BST 2004

Am Sonntag 17 Oktober 2004 19:31 schrieb Juergen Pfennig:
> I would understand if you would say you want some no-op macro to flag such
> a situation or use the macro that comes with qt4 (or a dummy for that). But
> QString::fromLatin1() is not a no-op and it is unefficient because it
> creates a temporary QString object.
Do you have such a no-op macro? I don't mind how to flag them, but I want to 
have them flaged and not by run over by scripts to remove the flags.
> (1) using UTF-8 strings everywhere instead of us-ascii (does gcc like
> this?)
Our code is UTF-8 already. But strings that are definitely 7bit are easier to 
parse as latin1.

> (2) moving away from GCC - here: supporting UNICODE string literals.
> Moving away from GCC (by using a pre-processor?) could help to cure another
> extremely ugly KDE problem:
> --- The broken exception handling in C++ (is it really broken?)
It was broken in '98 I think.

Greetings, Stephan

More information about the kde-core-devel mailing list