[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kwrite-devel
Subject:    Re: KDE/kdelibs/kate/mode
From:       Christoph Cullmann <cullmann () babylon2k ! de>
Date:       2007-10-17 15:47:34
Message-ID: 200710171747.34872.cullmann () babylon2k ! de
[Download RAW message or body]

Am Mittwoch, 17. Oktober 2007 00:37:42 schrieb Andreas Pakulat:
> On 16.10.07 23:34:43, Sebastian Pipping wrote:
> > Andreas Pakulat wrote:
> > >> Btw I used a macro to get zero debug speed loss for
> > >> releases builds. Would be cool if we could make that
> > >> configurable from outside the sources. If you like
> > >> it would could use it at other places, too.
> > >
> > > Excuse my ignorance (of the kate code that prints something) but that
> > > code already exists, if you output using kDebug(). kDebug() calls do
> > > nothing in release builds, so as long as you're printing with kDebug()
> > > the release build won't be as noisy as your debug build.
> >
> > Sure, but the functions are still called. I like to
> > trim that down to zero, nto just very little overhead.
>
> Uhm, if you have so many kdebug calls that this is still a noticeable
> overhead you did something wrong with kdebug (i.e. used in far too many
> places)
Don't think so, sometimes you just need over verbose debug output, for such 
places, Sebastian's Macro is cool :) For example the rendering/highlighting 
stuff comes into my mind.


-- 
Christoph Cullmann
KDE Developer, Kate Maintainer
http://babylon2k.de, cullmann@kde.org
_______________________________________________
KWrite-Devel mailing list
KWrite-Devel@kde.org
https://mail.kde.org/mailman/listinfo/kwrite-devel
[prev in list] [next in list] [prev in thread] [next in thread]