FWIW, there continue to be strong misgivings about the pythonesqe design we
have now, but Mozilla insists on the back of their shipping implementation.
Many feel that exceptions for control-flow are a missdesign, myself
included, but at this point the ship us nearly past the lighthouse on its
way to sea and the effort involved in recalling it not worth the pain.

Regards
On Feb 10, 2013 8:26 AM, "Domenic Denicola" <domenic at domenicdenicola.com>
wrote:

> > -----Original Message-----
> > From: Brendan Eich [mailto:brendan at mozilla.com]
> > Sent: Sunday, February 10, 2013 03:20
>
> > Changing from hasMore/getNext to current/moveNext does not eliminate two
> methods that can get out of sync. You can imagine one is a property, not a
> method, but the general case is a getter or C#-style Current method.
>
> Ah, the fact that it could be a getter does reduce it to the original
> two-out-of-sync-methods case, right. Thanks!
> _______________________________________________
> es-discuss mailing list
> es-discuss at mozilla.org
> https://mail.mozilla.org/listinfo/es-discuss
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.mozilla.org/pipermail/es-discuss/attachments/20130210/6f0f9883/attachment.html>

FWIW, there continue to be strong misgivings about the pythonesqe design we
have now, but Mozilla insists on the back of their shipping implementation.
Many feel that exceptions for control-flow are a missdesign, myself
included, but at this point the ship us nearly past the lighthouse on its
way to sea and the effort involved in recalling it not worth the pain.