Mochabot log - CommonJS IRC channel: #commonjs on irc.freenode.net

2010-11-03:

[14:05] <WesMac> observation - spec writing is a lot like writing programs. The more you can delete, the better it is
[14:08] <WesMac> deanlandolt: Think you'll have a chance to write about ES-5 interfaces today?
[14:09] <deanlandolt> WesMac: how do you mean? you mean the idea that was thrown out by ls_n?
[14:09] <deanlandolt> the provides stuff?
[14:09] <WesMac> deanlandolt: No, ES-3/5 shim layer for CommonJS
[14:10] <deanlandolt> oh, i see...yeah, sure
[14:10] <deanlandolt> i'll put something together and get it to you by tonight
[14:10] <WesMac> awesome, thanks
[14:10] <deanlandolt> i've gotta run to a meeting real quick...back in a half hour
[14:10] <WesMac> I might actually get a finished draft today
[14:10] <WesMac> I figure I'm 3-4 hours of writing away
[14:14] <WesMac> When this is done I need to write a more formal treatise on CommonJS in the UNIX environment, as invoked by exec
[14:14] <WesMac> Then I can better-document comment-embedded options
[14:15] <WesMac> And document how to use the return statement from the main module to affect the WEXITSTATUS rather than doing an exports replace
[14:46] <deanlandolt> WesMac: http://www.aminutewithbrendan.com/pages/20101103
[15:03] <WesMac> deanlandolt: Thanks for the link. Does it play for you?
[15:03] <deanlandolt> yes
[15:04] <deanlandolt> try downloading the mp3 or ogg
[15:04] <deanlandolt> voodootikigod's trying to be cute and go flash-free...it can be problematic :)
[17:14] <deanlandolt> WesMac: still putting together comments on your latest draft but i have a few quick questions about labeled deps if you have time
[17:24] <hannesw> WesMac: is there a proposal/draft somewhere we can read?
[17:24] <deanlandolt> hannesw: i think wes is trying to button things up a bit before he presents it to prevent any confusion...he's almost finished though
[17:25] <hannesw> ok, great!
[17:55] <WesMac> deanlandolt: have time
[17:55] <WesMac> hannesw: Not yet, I'm still working on a first draft
[17:58] <WesMac> hannesw: Have you been following the module format uber threads on the ML?
[17:58] <hannesw> I've tried :)
[17:59] <hannesw> but not full-time
[17:59] <WesMac> yeah, keeping up is consuming a LOT of my time!
[18:30] <WesMac> deanlandolt: What do you type to make a program execute with narhwal? "narwhal -f program.js" or something?
[18:42] <deanlandolt> WesMac: narwhal program.js
[18:42] <WesMac> deanlandolt: Thanks. That seems like a good recommendation for a minimal script interpreter invocation
[18:42] <deanlandolt> yeah
[18:44] <deanlandolt> so, the question i had re: labeled deps: can you do module.declare({foo: "bar", baz: "quux"}, function(r,e,m){})? you say it doesn't have to explicitly be an array
[18:46] <WesMac> deanlandolt: That's right, you can do that. I see no reason to forbid it.
[18:47] <deanlandolt> ah, cool
[18:47] <deanlandolt> and you can't get any "unlabeled" deps from module.deps, right?
[18:47] <WesMac> Right
[18:47] <deanlandolt> just the module.dependencies array
[18:48] <WesMac> module.dependencies is just as list of dependencies now
[18:48] * WesMac flip flops
[18:48] <WesMac> so if you wanted the exports object, you have to
[18:48] <WesMac> require(module.dependencies[0])
[18:48] <WesMac> This is to prevent semantic changes caused by the order of module initialization without an explicit request
[18:49] <WesMac> So, for labeled dependencies, we have already (necessarily) invoked the module factory functions of the labeled deps before the invoking the module
[18:50] <deanlandolt> ah
[18:51] <deanlandolt> why necessarily again? i thought you got around that by making module.deps a fn
[18:51] <WesMac> oh shit!
[18:51] * WesMac forgot about that
[18:52] <WesMac> that's an even better solution!

 

 

Logs by date :