Cpp Parser & multibyte chars (bug 274430)
apaku at gmx.de
Sun Nov 20 16:19:51 UTC 2011
On 20.11.11 11:13:02, Aleix Pol wrote:
> On 11/20/2011 09:38 AM, Andreas Pakulat wrote:
> >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.
> Now it's broken for people using utf8 apparently, so I don't think
> it's a valid concern.
I think you misunderstood. What I wanted to get across is that fixing
just the utf8 case only means things get broken for a different set of
users. Which is just as wrong as sticking with the current situation.
More information about the KDevelop-devel