Cpp Parser & multibyte chars (bug 274430)

Andreas Pakulat apaku at gmx.de
Sun Nov 20 08:38:40 UTC 2011

On 19.11.11 19:09:07, David Nolden wrote:
> Using QString is not an option, because it not only affects memory-usage,
> but also efficiency.

Whats the efficiency problem with QString here? After all indexing into
it to get a QChar out should be O(1), right?

> It shouldn't be too complicated though to map ranges regarding utf8 when
> doing the highlighting in the editor.

Then you break things for anybody not using utf-8 which is just as
valid as a source file encoding.


More information about the KDevelop-devel mailing list