On 2/20/07, Dan Webb <[EMAIL PROTECTED]> wrote: > > > I think it's really important to do something about this because as it > stands Prototype overwrites JS 1.6 methods with incompatible versions. As > more browser support these methods and more scripts depend on them its going > to be a problem.
Dan expressed exactly what I feel. We shouldn't drift away too far from the actual ECMAScript spec for future compatibility. Secondly, I really think that in areas like this where optimisation is going > to make a big difference to most people's script speeds it's really worth > considering how generally worthwhile having the break continue stuff in is > compared to allowing browsers to use native versions if need be. Well, we don't have $continue anymore, so no point in discussing that bit. About $break... I'm not sure whether this feature is good or just a performance/debugging hog, but I'm definitely sure I almost never use it myself (same in Ruby). When I iterate over a collection I want to complete the whole collection. When I only want to find certain stuff I use detect or findAll. Still, detect depends on break functionality. Maybe the method call roll its own $break, slimming down the original each? Remember - forEach and others in JavaScript 1.6 don't have break. Each user has to roll its own explicitly. Maybe we can turn Enumerable.each from implicit break functionality to explicit (optional)? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Prototype: Core" 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/prototype-core?hl=en -~----------~----~----~----~------~----~------~--~---
