Hey,
astecomm a écrit :
> What do you think about it? Is there any way to avoid this
> "incompatibility" with existent JS code in my web app? Is prototype a
> good way to do things only if you wanna make your app from 0?
I'm in a rush, so very shortly:
- This article is 1.5 years old
- Prototype hasn't extended Object.prototype since version 1.4.0
- Extending Array.prototype is no problem at all, the issue stems from
people misusing for...in:
- thinking it's a shortcut for numerical loop, which it is not;
- using Array objects as associative arrays when they should use
raw Object instances instead.
So yeah, you should totally go with Prototype if all that holds you back
is those critics. The Object one is very much obsolete, and the Array
one is ill-founded.
JM2C,
--
Christophe Porteneuve aka TDD
[EMAIL PROTECTED]
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Spinoffs" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/rubyonrails-spinoffs?hl=en
-~----------~----~----~----~------~----~------~--~---
