A similar idea was considered by Ryan a few years ago. I think it looked like
this
import('modulename')
All the exports are dumped by name in to the scope. There was also some
copy-on-write isolate stuff in there if i remember correctly.
It was scrapped as a bad idea for a lot of the reasons people have already
mentioned. Also, the `module.exports = function () {}` pattern has become
pervasive and would be really hacky to get right with this kind of feature.
Modules are done. node.js is at a stage now where certain new ideas aren't
welcome like they were a few years ago. That's just how projects evolve, some
things solidify and in order to make progress elsewhere we have to reject a lot
of alternative ideas.
-Mikeal
On Jun 8, 2012, at June 8, 20128:38 AM, Seiji Sam Lee wrote:
> El 01/06/12 21:59, Isaac Schlueter escribió:
>> No, we're not going to do this. The module system is finished. It
>> won't be changing except for critical bugs.
>>
>> On Fri, Jun 1, 2012 at 12:57 PM, Alan Gutierrez<[email protected]>
>> wrote:
>>> On Fri, Jun 01, 2012 at 12:42:42PM -0700, Martin Wawrusch wrote:
>>>>>>>> On Fri, Jun 1, 2012 at 2:26 PM, Seiji Sam Lee<[email protected]>
>>>>>>>> wrote:
>>>>>>>>> Due the great expectation around node.js, libs and functions grow up
>>>>>>>>> without control.
>>>>>>>>>
>>>>>>>>> Nowadays we have a lot of "requires" and we need to memorize a lot of
>>>>>>>>> names (fs, path, vm, ...); with time, we'll spend more and more time
>>>>>>>>> reading
>>>>>>>>> documentation :-(
>>>>>>>>>
>>>>>>>>> My proposal is incorporate the mechanism of "register" the module,
>>>>> for
>>>>>>>>> example, phpjs library could register the function "isset" into
>>>>>>>>> "utils", and
>>>>>>>>> "abs" function into "math"
>>>>>>>>>
>>>> On Fri, Jun 1, 2012 at 12:39 PM, Joshua
>>>> Holbrook<[email protected]>wrote:
>>>>
>>>>> -1 as I like my modules exactly as they are.
>>>>>
>>>>> --Josh
>>>> -1 as well. Thank you Josh.
>>> -1
>>>
>>> Perl has this, a default export. You'll need a switch to say that you don't
>>> want
>>> the default exports. Then you're going to need a way to remap the default
>>> exports. Pretty soon you're going to have Perl.
>>>
>>> Actually, I am you're more likely to devolve into PHP, a global namespace
>>> full
>>> of suprises.
>>>
>>> --
>>> Alan Gutierrez - @bigeasy
>>>
>>> --
>>> Job Board: http://jobs.nodejs.org/
>>> Posting guidelines:
>>> https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
>>> You received this message because you are subscribed to the Google
>>> Groups "nodejs" group.
>>> To post to this group, send email to [email protected]
>>> To unsubscribe from this group, send email to
>>> [email protected]
>>> For more options, visit this group at
>>> http://groups.google.com/group/nodejs?hl=en?hl=en
> But is possible to develop a module called "namespace" to allow namespaces
> and a hierarchy of them. It could be a parallel developing.
>
> --
> Job Board: http://jobs.nodejs.org/
> Posting guidelines:
> https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
> You received this message because you are subscribed to the Google
> Groups "nodejs" group.
> To post to this group, send email to [email protected]
> To unsubscribe from this group, send email to
> [email protected]
> For more options, visit this group at
> http://groups.google.com/group/nodejs?hl=en?hl=en
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups "nodejs" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en
