On Fri, Aug 31, 2012 at 6:24 PM, 程劭非 csf...@gmail.com wrote:
What does it look like if you want to import more than one variables
from one module?
import {a,b} from oldscript.js#a,b
2012/8/31 Shijun He hax@gmail.com:
On Fri, Aug 31, 2012 at 3:16 PM, 程劭非 csf...@gmail.com wrote:
I guess
I guess Kevin has some same concerns with me.
The four things point to one question: What should we do with the old
ES3/ES5 libraries after we have module?
(please correct me if you didn't mean that.)
ES3/ES5 libraries might be in more than one files and there are no
“export” and import in it.
On Fri, Aug 31, 2012 at 3:16 PM, 程劭非 csf...@gmail.com wrote:
I guess Kevin has some same concerns with me.
The four things point to one question: What should we do with the old
ES3/ES5 libraries after we have module?
(please correct me if you didn't mean that.)
ES3/ES5 libraries might be in
What does it look like if you want to import more than one variables
from one module?
2012/8/31 Shijun He hax@gmail.com:
On Fri, Aug 31, 2012 at 3:16 PM, 程劭非 csf...@gmail.com wrote:
I guess Kevin has some same concerns with me.
The four things point to one question: What should we do with
Four things:
1) The export grammar on the wiki allows:
export *;
Which I take to mean export every local binding. What's the
justification? I don't think I've ever seen a ES5 module that didn't
have some local, non-exported state or function.
2) The grammar also allows:
export *
5 matches
Mail list logo