kDebug improvements

Andreas Pakulat apaku at gmx.de
Wed Jan 17 15:21:53 GMT 2007

On 17.01.07 15:52:57, Thomas Zander wrote:
> On Wednesday 17 January 2007 04:34, Teemu Rytilahti wrote:
> > > Changing the items you mention means changing _all_ the kDebug calls we
> > > have now. Which IMO is not only not worth it, its too risky to piss off a
> > > huge amount of developers.
> >
> > Well, the change shouldn't be that big for the developers of new KDE4 apps
> > and for KDE3 developers porting to KDE4 some parts could be done
> > automatically with kde3to4 script, right? Most of those changes wouldn't do
> > much harm anyway if not ported at first at all, or at least I can't see the
> > bad sides.
> One feature that I use a lot is to have kDebug() << "foo: '" << bar "'\n";
> which prints the bar variable with single quotes around it.  In KWord I work 
> with text a lot and having the _exact_ text on screen is very important.
> With qDebug() it adds spaces automatically; which makes the above impractical 
> or impossible.

Huh? Qt4 qDebug() puts "" around a QString, so you can still see the
exact text unless bar is not a QString.


You possess a mind not merely twisted, but actually sprained.

More information about the kde-core-devel mailing list