-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Martin Ellis wrote: > The main problem is with the use of name.camelize() in the final call to > element.style[] = value; Without the camelization of the name everything > works must faster. Is it really camelize() who imposes so much penalty? Event when - as you said - you already provide "camelized" values? Anyway, I'd say it's a no-no to drop backward compatibility, at least for now. OK, maybe as a target for 2.0 with big red "deprecated" warnings along the way. ;-)
Meanwhile, let's see how this situation can be improved: > or checking if it needs to be done in the first place? This looks like the only way to go. So, let's see what happens if we plug a "dash checker" in camelize() before really split()-ing that string: http://gfx.neohub.com/benchmark/t/camelize.html OK, I can see a ~40% improvement in the "already camelized" case ( "foo" vs "foo(*)" ) and ~10% penalty in all other cases. This doesn't look too bright. :( - -- Marius Feraru -----BEGIN PGP SIGNATURE----- iD8DBQFF2MP2tZHp/AYZiNkRAvaaAJ9cAonNT3UN4H+yw9mlT4M7YNUuDACdEvkN Uh2cCfVN2P6KPLc2o9rMYk0= =e6cp -----END PGP SIGNATURE----- --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Prototype: Core" group. To post to this group, send email to prototype-core@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/prototype-core?hl=en -~----------~----~----~----~------~----~------~--~---
