Binding "this":
- Does it ever make sense to access globals via "this"? If so, I assume there
will be a use case in the upcoming modules rationale document.
- Should there be a keyword for "the current module" (a module-this, if you
will)? Accessing module-global data via "this" feels strange (I that is indeed
the intention of what I have read). It would also not work inside methods. But
it seems like the only globals inside a module are module-relative. Then
everything would work out fine.
Nesting modules:
- Can several files have the same namespace parent? It looks like all
submodules must be in the same file, as it stands right now.
- I think Python uses directories for namespace nesting, which has some pros
and cons compared to completely abstracting the file system structure.
Renaming:
- I find this syntax slightly unintuitive: import Geometry.{draw: drawShape}
At first glance this would mean for me: rename drawShape to draw. "draw"
feels to me like the result of the import.
- Possible alternative: import Geometry.{draw <- drawShape} (maybe a colon is
not a good choice here)
FWIW: I’ve tried to summarize the current proposal here, to give JavaScripters
a first impression:
http://www.2ality.com/2011/03/first-look-at-upcoming-javascript.html
--
Dr. Axel Rauschmayer
[email protected]
twitter.com/rauschma
home: rauschma.de
blog: 2ality.com
_______________________________________________
es-discuss mailing list
[email protected]
https://mail.mozilla.org/listinfo/es-discuss
