Le 20/01/2013 21:53, Brendan Eich a écrit :
Allen Wirfs-Brock wrote:
We we were going to talk about adding support for addition semantics
to classes we should start at the level of the object model. Not
with syntax. ES6 class syntax is good because it is defined in terms
of the object model and more basic operations that are defined in the
language. You don't have to use class syntax to define a class
equivalent. So, if we are going to introduce private object state the
first step is to define how it works at the object model level.
Cutting there to dodge the controversy over private-in-class based on
weak maps, to divide and conquer in the meta-discussion with David.
Here I agree with you, and we have talked in the past of the perils of
"Scenario Solving" by adding just-so syntax with novel semantics,
which is not decomposed into orthogonal primitives. You saw that in a
past life (VB5, cough) and it made messes, even though the intentions
(serving developer problem-scenarios) were good.
I'm too new to the programming language world, so I don't have this
context, but I'm curious. Do you have links or further explanations on
this topic?
Thanks,
David
_______________________________________________
es-discuss mailing list
es-discuss@mozilla.org
https://mail.mozilla.org/listinfo/es-discuss
