Ordering of JS properties

[Harri Porten]

On Mon, 16 Feb 2004, Darin Adler wrote:

> > The only solution - other than returning to the slow list - is to do
> > double book keeping with an index or list which will cause an
> > additional memory overhead.
>
> We did this for Safari 1.0.

Oh. I'll look for the diffs. Thanks for the hint.

> This is one of the differences that exists between TOT kjs and
> JavaScriptCore after my current merging is done. I was planning to send
> a complete diff to this list with some comments about it.

One word of caution in case I haven't posted this here before: I'm
considered to revert the optimisation of adding virtual functions like
Node::toString() etc. It reduces the number of value object creations but
I'm not convinced anymore that this is worth the effort. Instead, the
strategy should be to "compile better code" that is adapted to the
operations required. More on that on another day in the future ...

Harri.