Hey Robert, And in the worst case, we throw a $stop object instead. :-) It's just too good an idea (IMHO), letting us have self-stopping while still being able to use functions as repeaters that didn't know they were going to be repeaters... But I'm for continuing to use $break until/ unless it goes away entirely.
-- T.J. :-) On Aug 28, 5:30 pm, Robert Kieffer <bro...@gmail.com> wrote: > @tobie: I'm a little unclear how the ES5 implementation of forEach() > impacts the idea of using $break to terminate a repeat() call. Can > you elaborate? > > Unless $break is removed from Prototype altogether, I don't see how > this is an issue. And the only reason to remove $break is if all the > Enumerable methods (that depend on it) are also going away. But given > that a) ES5 doesn't support a mechanism for early termination of > forEach(), b) the "throw $break" pattern is both useful and c) ES5 > doesn't support many of the Enumerable methods, it seems like those > methods will stick around and continue to recognize $break as a way of > terminating an enumeration. --~--~---------~--~----~------------~-------~--~----~ 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 prototype-core-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/prototype-core?hl=en -~----------~----~----~----~------~----~------~--~---
