Thanks for this :-)
The /name/ property is initialized with the best value given static
semantics
= I think all the rules should be explicitly laid out (i think that's
what you did in the subsections after this sentence) to avoid
implementation-specific interpretations of this sentence. Some
On 4/4/2013 11:52 AM, David Bruant wrote:
The /name/ property is initialized with the best value given static
semantics
= I think all the rules should be explicitly laid out (i think that's
what you did in the subsections after this sentence) to avoid
implementation-specific interpretations of
On Apr 4, 2013, at 12:02 PM, Brandon Benvie wrote:
On 4/4/2013 11:52 AM, David Bruant wrote:
The name property is initialized with the best value given static semantics
= I think all the rules should be explicitly laid out (i think that's what
you did in the subsections after this sentence)
On 4/4/2013 12:47 PM, Allen Wirfs-Brock wrote:
I would argue that the best name for the method is add while the
path/origin of it might be Set#add. They are orthogonal in my
opinion, and name is much simpler to specify.
This would seem to argue against prepending static. Also it
wouldn't
On 4/4/2013 12:47 PM, Allen Wirfs-Brock wrote:
What about function that are defined like:
Date.myParse = function () {...}.
This brings up another point I wanted to address but didn't think to at
the time. It makes sense, since function names are being formalized, to
also specify how
5 matches
Mail list logo
