[Development] Removing QT_NO_DEBUG_STREAM?

[Konstantin Ritt]

2014/1/6 David Faure <david.faure at kdab.com>

> On Monday 06 January 2014 19:43:45 Konstantin Ritt wrote:
> > I don't like the idea of removing QT_NO_DEBUG_STREAM. Even if Qt itself
> > doesn't build with it (which is fixable), one might define it globally
> > after it built, to avoid building an unnecessary code in his/3rd-party
> > modules.
>
> You don't gain anything by defining it in your app, compared to just not
> calling qDebug.
>
>
In my app (or in 3rd-party code), there could be classes with debug stream
operators.


> This isn't the intended usage of QT_NO_* - this was about reducing the
> size of
> Qt.
>
>
And this remains desirable for some users.


> But yeah at this point QT_NO_DEBUG_STREAM should just be removed, the
> maintainance pain is not worth it.
>
>
Which maintainance pain, exactly?


The typical purpose for debug operators is a convenience, well, in
debugging. But that costs.
That's why many users (and me) uses a cheap qWarning(msg) for warnings and
#ifndef DEBUG_MY_FEATURE \ qdebug() << various << crap; \ #endif for
testing/debugging their code.

I'd vote for fixing build with QT_NO_DEBUG_STREAM rather than for deleting
it.

Konstantin


>  --
> David Faure | david.faure at kdab.com | Managing Director KDAB France
> KDAB (France) S.A.S., a KDAB Group company
> Tel. France +33 (0)4 90 84 08 53, Sweden (HQ) +46-563-540090
> KDAB - Qt Experts - Platform-independent software solutions
>
> _______________________________________________
> Development mailing list
> Development at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/development
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/development/attachments/20140106/df45f462/attachment.html>