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

List:       kde-core-devel
Subject:    Re: Normalizing signals and slots
From:       "=?UTF-8?Q?Rafael_Fern=C3=A1ndez_L=C3=B3pez?=" <ereslibre () gmail ! com>
Date:       2007-01-14 22:17:38
Message-ID: 93f85fee0701141417m14f8bce0i762d7538ec44285f () mail ! gmail ! com
[Download RAW message or body]

Hi,

I agree that a well written script or app (like Olivier's one) will be
better than human minds changing them, since we lead to errors. The
point here is that Matt said "optimization is the root of all evil",
well... there's no difference here, is not a gcc -O3, i mean the code
that we let without normalize will be normalized in run-time, is not
like an optimization that will change assembly code, and can cause
unknown problems.

And yes, maybe is only necessary on kdelibs. I just proposed this
because I have heard lots of times "kde is slow". Well for me it
isn't, but if we can improve that way with a "simple" effort, why
not?. From my point of view, normalized signals and slots are not
unreadable, but there's always the possibility as Olivier said
normalizing them on building time.

Bye,
Rafael Fernández López.

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