`this` inside modules
matthewwrobb at gmail.com
Mon Jun 9 08:19:06 PDT 2014
I guess it just seems odd to me that we HAVE a system in place now for
importing "stuff" into a Program with an author defined local identifier
name and we're discussing magic like using this or module. Just make it
another thing the author imports inside their own module? ``` import meta
from "./@meta"; ``` or something in the ballpark. Let's use the system
we're creating to our advantage.
- Matthew Robb
On Mon, Jun 9, 2014 at 8:11 AM, Kevin Smith <zenparsing at gmail.com> wrote:
> I agree with Alex completely. Using `this` as a module meta object is a
> bad idea. Boo.
> On Mon, Jun 9, 2014 at 11:03 AM, Matthew Robb <matthewwrobb at gmail.com>
>> What if instead of any sort of magic there was a special relative import
>> a person could specify to get access to the this module?
>> import module from "@currentModule";
>> - Matthew Robb
>> On Mon, Jun 9, 2014 at 7:46 AM, Erik Arvidsson <erik.arvidsson at gmail.com>
>>> On Mon Jun 09 2014 at 12:25:42 AM, Domenic Denicola <
>>> domenic at domenicdenicola.com> wrote:
>>>> If a magically in-scope binding is necessary to access module meta
>>>> capabilities, giving it a name like `module` or `System.currentModule`
>>>> would be much better.
>>> `System.currentModule` requires magic. It would require the engine to
>>> know where the call site was.
>>> We also talked about adding a binding, like NodeJS does but @David
>>> Herman <dherman at mozilla.com> argued that thaw is a non starter.
>>> So, if we don't want to use `this` or introduce a new binding name, or
>>> add more magic, the only thing left seems to be new dedicated syntax. In
>>> ES4 we `this function` which is similar to what @Axel Rauschmayer
>>> <axel at rauschma.de> suggested.
>>> es-discuss mailing list
>>> es-discuss at mozilla.org
>> es-discuss mailing list
>> es-discuss at mozilla.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the es-discuss