[Development] Backwards compatibiltiy break in Qt 5.5

[Andreas Aardal Hanssen]

2015-07-28 9:50 GMT+02:00 Robert Iakobashvili <coroberti at gmail.com>:

> On Tue, Jul 28, 2015 at 11:48 AM, Marc Mutz <marc.mutz at kdab.com> wrote:
> > On Monday 27 July 2015 20:44:48 Thiago Macieira wrote:
> >> On Monday 27 July 2015 21:41:44 NIkolai Marchenko wrote:
> >> > Yes,but this requires making override visible in every file of the
> >> > project.
> >> We can solve this by having a global #ifdef that can change the setting.
> > Or an environment variable, so you don't have to recompile the world...
> Yes, it's a good idea to have an environment variable or
> a pre-processing flag to preserve the existing behavior.
> In Qt 5.* the default could be the old behavior,
> and in Qt 6 - the new.
>

Isn't this needless convenience? Yet another environment variable that
needs documenting? If you want to inspect the contents of a QString, can't
you just add the suitable escape code to your own code? Forcing
qPrintable() or qUtf8Printable() on everyone who wants to keep human
readable debug output sounds pretty evil, but having e.g. toHtmlEscaped()
or a similar function doing the octa/hex thing could be better.

-- 
Andreas Aardal  Hanssen
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/development/attachments/20150728/4d32b196/attachment.html>