[9:29]<hannesw> zumbrunn: sorry, no time to talk yesterday [9:29]<hannesw> how would you want to "export everything" with securable modules? export('*')? [9:32]<zumbrunn> or maybe export(this) [9:33]<zumbrunn> where export() would loop through the properties of whatever object it receives as an argument, and copy those properties where hasOwnProperty() is true [9:34]<zumbrunn> easy enough to do inside of modules where it is needed anyway, of course [9:34]<zumbrunn> but maybe convenient syntax to do this often would make sense [9:42]<zumbrunn> or we don't add any module specific sugar for this, and just use some generic utility method to do the job [9:43]<zumbrunn> like the Object.clone(this,exports) function in helma 1.x [10:05]<hannesw> yes, this.clone(exports) should work [10:06]<hannesw> but it'll also export imported stuff, of course [10:06]<hannesw> which is the thing that securable modules fixes, really [10:06]<hannesw> what I've done so far yesterday is: [10:07]<hannesw> when you only export some parts, and those parts are functions, use export("funcname1", ...) [10:07]<hannesw> when you export everything like in the app's config modules, define stuff with exports.foo = bar directly [11:00]<zumbrunn> I guess the main use case is to be able to reuse existing code as easily as possible in the form of a module [11:01]<zumbrunn> without having to think about what needs to be exported