[Development] FW: Backwards compatibiltiy break in Qt 5.5
Thiago Macieira
thiago.macieira at intel.com
Mon Jul 27 19:03:25 CEST 2015
On Monday 27 July 2015 16:57:23 Knoll Lars wrote:
> On 27/07/15 18:52, "development-bounces+lars.knoll=theqtcompany.com at qt-
project.org on behalf of Thiago Macieira" <development-
bounces+lars.knoll=theqtcompany.com at qt-project.org on behalf of
thiago.macieira at intel.com> wrote:
> >On Monday 27 July 2015 19:49:15 NIkolai Marchenko wrote:
> >> If we are to believe Thiago, every developer that needs to see trace
> >> information from an old code, now needs to edit all of his qDebug()'ed
> >> instances to use qPrintable. Yes, all of them. However much there is,
> >> manually, one by one.
> >
> >You need to qualify this as "every developer who wants to see the string
> >printed without the quotes and escaping". This reduces your "every
> >developer" to maybe 5% of them, probably less.
>
> I think you underestimate this. We have a huge amount of developers in non
> latin countries and for everybody doing development in these countries this
> is a very common problem.
I'm not thinking of people's languages.
I'm thinking of the intent to "read" the string in the output, as opposed to
inspecting it for why it contains the content it contains. The whole thinking
is that the use of operator<< for QString implies you're trying to figure out
why that string is the way it is, as opposed to trying to convey a message. If
you wanted the latter case, you'd have used operator<< for const char*, which
wasn't affected.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
More information about the Development
mailing list