Classes: suggestions for improvement

Brendan Eich brendan at mozilla.com
Mon Jun 13 08:44:06 PDT 2011


On Jun 13, 2011, at 8:41 AM, Juan Ignacio Dopazo wrote:

>  On Sun, Jun 12, 2011 at 10:17 PM, Brendan Eich <brendan at mozilla.com> wrote:
> 
> I'm not sure classes should grow to have private class or prototype variables in ES.next. Mark stripped things down to help get classes in. The one reason I come back to them: private methods for common subroutining are frequent in practice. So YAGNI doesn't work. One can always closure- or module-wrap by hand; that's the counterargument.
> 
> /be
> 
> I'm not sure that's a counterargument. The whole point of the classes proposal is to simplify the use of a common pattern. Private methods for subroutines are a very common use case.

Agreed. The counter-argument and the minimizing of the proposal are all about what can be done now, vs. later. Not sure when later is, perhaps even during ES.next spec construction. It is an open issue.

/be

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.mozilla.org/pipermail/es-discuss/attachments/20110613/cf8189d6/attachment.html>


More information about the es-discuss mailing list