Hi James.

Take a look here: https://people.mozilla.org/~jorendorff/es6-draft.html#sec-runtime-semantics-makesuperreference-propertykey-strict .
I think that should help you.

- Jonathan Barronville

On December 9, 2013 at 10:54:54 AM, James Long (longster at gmail.com) wrote:

Hey guys,  

First posting to this mailing list. I'm defining a few ES6 features as  
sweet.js macros so existing projects can easily leverage them. I also  
happen to think macros are a big deal for JS and this is how future  
extensions should be defined... (at least ones that are mostly  
syntactic) My project is here: https://github.com/jlongster/es6-macros  

I'm working on `class`, and it's mostly working. You can see the tests  
here: https://github.com/jlongster/es6-macros/blob/master/tests/class.sjs,  
and the generated code here:  
https://github.com/jlongster/es6-macros/blob/master/tests/class.js  

My question is with `super`. I've searched the archives and read the  
spec to answer most of my questions, but one thing is unclear. What  
exactly is the scope of `super`? Is it valid to use `super` inside a  
nested function, like in this example?  
https://github.com/jlongster/es6-macros/blob/master/tests/class.sjs#L91  

If so, `super` seems somewhat magical in that it can resolve the  
prototype of a `this` object that isn't available (when that function  
is called, `this` is not the object anymore). Are there clear rules  
with how `super` is resolved somewhere?  

Thanks,  
James  
_______________________________________________  
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/20131209/3b09b0d6/attachment-0001.html>

Take a look here: https://people.mozilla.org/~jorendorff/es6-draft.html#sec-runtime-semantics-makesuperreference-propertykey-strict .
I think that should help you.