On 14 Apr 2014, at 14:26, Simon Hausmann <[email protected]> wrote: > > Since this affects not just one place but many (and for example we have many > copies of the QML lexer around), I'd like to determine what the _correct_ fix > for this issue is, because frankly speaking I don't know :). However I have > an > interest in the same fix being applied to qtbase, qtdeclarative, qtscript, > qtcreator and other affected modules.
Even more critical, this behavioural change won’t only affect Qt modules, but also a lot of customer code, which cannot be fixed by us. Which makes me wonder if such a be a change between 5.2 and 5.3 is acceptable at all. Was it intentional or an unintended side-effect? I can’t find any discussion about the issue. > 3) I noticed that QString::fromUtf8() differs from QTextCodec in this aspect. > Is that intentional? That inconsistency makes it even more confusing to me. -- Qt Developer Days 2014: October 6 - 8 at BCC, Berlin Frank Osterfeld | [email protected] | Senior Software Engineer KDAB (Deutschland) GmbH&Co KG, a KDAB Group company Tel. Germany +49-30-521325470, Sweden (HQ) +46-563-540090 KDAB - Qt Experts - Platform-independent software solutions _______________________________________________ Development mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/development
