with the addition of writing nastygrams to tell other devs how to do proper JS iteration :)
Yes, great idea! :-) I'm on the fence actually. I don't see too much use in treating an associative array (object) as a collection. If you need a robust dictionary or hash like collection, there are better ways IMHO. So I've never had issues with any libs "breaking" the (for var p in obj) method, as I've never thought of that as a great way to iterate (mind you, I do use it in a pinch, but am sure to filter things out if I have to). Arrays are much better suited, and it just gets my goat every time I see someone do something like declare an array and then try to iterate its properties as an associative array, rather than using indexes and the Array object's special collection operation methods (like .push() for example).
Anyway... </rant>
--~--~---------~--~----~------------~-------~--~----~
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 rubyonrails-spinoffs@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/rubyonrails-spinoffs
-~----------~----~----~----~------~----~------~--~---
