inline unicode()

[Darin Adler]

On Monday, March 10, 2003, at 04:56 PM, Harri Porten wrote:

> On Mon, 10 Mar 2003, Darin Adler wrote:
>
>> It's a simple practical issue. We do our development builds with -O0 
>> so
>> with no inlining. The functions that get right at the value of the
>> UChar are so hot, that if we leave them calling the inline function,
>> it's noticeably slower, and also more annoying to debug.
>
> OK. I do understand the debugging argument. But I hope you are basing 
> your
> optimization work on the debug version. It's not like the behaviour 
> would
> vary linearly or even monotonous.

Right, speed of the development builds means nothing to the end user, 
and of course we don't analyze those builds or optimize for them. 
Except that Safari programmers use development builds all day long when 
doing tasks other than optimization, so the speed does matter a little 
bit to us.

     -- Darin