Oops, please take my posting with a grain of salt. Turns out that the _big_ performance difference was due to a change in my own code which I had overlooked. I still think it's possilbe that the name swapping code in ScriptableObject.accessSlot is not really an improvement, but it probably doesn't make that big a difference.
Hannes On Sep 27, 12:50 am, Hannes Wallnoefer <[EMAIL PROTECTED]> wrote: > I think there may be a serious problem with the code in > ScriptableObject.accessSlot() that updates the slot name in order to > avoid future calls to String.equals(). I suspect that updating the > field repeatedly may have a bigger performance impact than calling > String.equals() - at least that's what my limited testing suggests. I > found that for a simple property access from the shell, the name gets > swapped not once but _twice_, and scripts that ran inexplicably slow > before now run really fast. Other scripts that have been fast before > seem unaffected. I guess it really depends on how and how often you > access properties. > > Can somebody look into this? > > hannes _______________________________________________ dev-tech-js-engine-rhino mailing list [email protected] https://lists.mozilla.org/listinfo/dev-tech-js-engine-rhino
