KMessage/KMessageHandler: a core/ui seperation for displaying message.
thiago at kde.org
Sun May 28 22:20:11 BST 2006
Michaël Larouche wrote:
>Exactly, you can use Debug type to use your own debug methods if you
> don't like kDebug().
Don't do that. If anybody wants a debug message, he has to use kDebug()
(never printf, never qDebug, never any other method that could output
text without going through kDebug in the end).
Debugging output has to be disabled at compilation time if -DNDEBUG has
been specified. It should expand to a code-path that never gets executed,
so that the compiler can optimise the whole thing out. And if -DNDEBUG
has not been specified, then the debugging output has to be done via
kDebug so that one can enable/disable easily with kdebugdialog.
Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org
thiago.macieira (AT) trolltech.com Trolltech AS
GPG: 0x6EF45358 | Sandakerveien 116,
E067 918B B660 DBD1 105C | NO-0402
966C 33F5 F005 6EF4 5358 | Oslo, Norway
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 191 bytes
Desc: not available
More information about the kde-core-devel