kdelibs/kdecore

[Maksim Orlovich]

On Thu, 20 Mar 2003, Eray Ozkural wrote:

> CVS commit by exa: 
> 
> Keep track of capacity and actual size separately in RArray. RArray does have size semantics!! (Which I neglected painfully). Also use calloc in constructor. Both suggested by Dirk.
> 
> CCMAIL: kde-optimize@kde.org
> 
> Note: If this still has breakage, please don't hesitate to revert it. If it's correct, I can tell why it's supposed to be faster in detail.

"Supposed to" doesn't matter. /Is/ it faster? Is the code path even
hot? Did you measure i-cache, d-cache pressure, alignment effects, memory
use?