[PATCH] a little optimization of KJS GarbageCollector

[David Faure]

On Thursday 01 December 2005 15:54, Dirk Mueller wrote:
> On Thursday 01 December 2005 15:45, Oswald Buddenhagen wrote:
> 
> > sounds absurd, but if you think about it, this is the case we (the
> > developers) use most ...
> 
> Yeah, but onyl those developers who don't use -Wall or test if their code 
> works at all (note: compiler optimisation can introduce warnings or expose 
> bugs that are otherwise not seen). 

You lost me there. --enable-debug leads to -g3 without optimization, for reliable
step-by-step debugging in gdb and backtraces. So, like everyone who compiles
kdelibs with debug enabled, I'm among the developers who benefit from an 
optimization like the one this thread is about; and this has nothing to do 
with -Wall does it? --enable-debug enables warnings too iirc, but how is that
related?
What do you expect? That everyone has two versions of kdelibs compiled,
one with debug for debugging and one without debug for more performance
and seeing all warnings? I don't think this is realistic.

-- 
David Faure, faure at kde.org, sponsored by Trolltech to work on KDE,
Konqueror (http://www.konqueror.org), and KOffice (http://www.koffice.org).