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

List:       kde-commits
Subject:    Re: new_rendering: kdelibs/khtml/rendering
From:       David Faure <david () mandrakesoft ! com>
Date:       2000-02-29 23:25:18
[Download RAW message or body]

On Wed, Mar 01, 2000 at 12:22:52AM +0100, Lars Knoll wrote:
> On Tue, 29 Feb 2000, David Faure wrote:
> 
> > On Tue, Feb 29, 2000 at 06:13:13PM +0100, CVS by knoll wrote:
> > > 
> > > kdelibs/khtml/rendering bidi.cpp,1.1.2.30,1.1.2.31 render_table.cpp,1.1.2.22,1.1.2.23
> > > Author: knoll
> > > CVSROOT: /home/kde
> > > Tue Feb 29 18:18:28 MET 2000
> > > Update of /home/kde/kdelibs/khtml/rendering
> > > In directory zeus:/tmp/cvs-serv27644/rendering
> > > 
> > > Modified Files:
> > >       Tag: new_rendering
> > > 	bidi.cpp render_table.cpp 
> > > Log Message:
> > > just tried how fast khtml can get if you remove the debug output...
> > 
> > If you used kdDebug, all you would have to do would
> > be to use kdebugdialog or -DNDEBUG :-)
> 
> I know. But somehow, we kept sticking to printf's and #ifdefs around for
> historical reasons.
:)

> Anyway, I sometimes need something to work with
> ifdefs. Try defining BOX_DEBUG in rendering/render_flow.cpp and look at
> khtmls rendering. No way, you could get an effect like that with kdebug
> ;-)

Why ? What's the difference with debug areas (except perhaps speed) ?

With kdebugdialog you can very easily enable/disable an area...

(Sorry, can't look into the code, I don't have the branch checked out)

-- 
David FAURE
david@mandrakesoft.com, faure@kde.org
http://home.clara.net/faure/
KDE, Making The Future of Computing Available Today

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