I can't see how code could be compiled apart from thru the action of 
boot.js, and in that case vm.runInNewContext(code,sandbox,filename) is run 
and the code has the sandbox as a global object. What does ' bypassing the 
Node resolver' mean?

On Tuesday, January 12, 2016 at 6:02:04 PM UTC, Devin Weaver wrote:
>
> Thinking about this I bet that TW is bypassing the Node resolver which 
> means it is loosing the private context. Though if that were the case then 
> perhaps there is a way to manage the TW resolver better so the IIFE was not 
> required for every developer to remember. Especially since placing IIFE in 
> Node.js code is considered bad practice.
>
> On Tuesday, January 12, 2016 at 10:13:26 AM UTC-5, Felix Küppers wrote:
>>
>> Continued discussion started by Devin from: 
>> https://groups.google.com/forum/?utm_medium=email&utm_source=footer#!msg/tiddlywiki/N7tXELs9z6k/_Of0R3LbDgAJ
>>  
>> <https://groups.google.com/d/msgid/tiddlywiki/1a20b6b7-f7a3-40a0-8712-82a4c6fc86c6%40googlegroups.com?utm_medium=email&utm_source=footer>
>>
>> *Intro:*
>>
>> While a poll in the tw community reveiled "warm feelings" in connection 
>> to additional closures – and there are rumors about a study that supports 
>> this empirical finding – the question is whether they are actually 
>> redundant.
>>
>> Quote from Devin's source (
>> http://nodejs.org/api/modules.html#modules_modules):
>>
>> Variables local to the module will be private, as though the module was 
>>> wrapped in a function
>>>
>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWikiDev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/tiddlywikidev.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywikidev/5facc128-2fc0-4037-b057-c5027c18063b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to