Well, perhaps someone else knows a trick or two for this. I guess my suggestion, if it's that big of an issue, is similar to your peers: don't use prototype. The alternative to that might include some porting of prototype on your end so that it doesn't add methods to the Array's prototype. But that's problematic.
Just so you are aware, you should probably advise your company against use almost any 3rd part libraries then (not just prototype). Array is extended quite frequently, and if you can't spend the time to fix your legacy application you will probably find this issue almost no matter what. --~--~---------~--~----~------------~-------~--~----~ 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?hl=en -~----------~----~----~----~------~----~------~--~---
