I often have a number of small but related modules and it would be<br>nice to distributed them as a single file.<br><br>Conceptually an application *is* one thing - so I'd like to distribute one file<br><br>/Joe<br><br><div>
<span class="gmail_quote">On 10/5/06, <b class="gmail_sendername">Vlad Dumitrescu</b> <<a href="mailto:firstname.lastname@example.org">email@example.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi,<br><br>On 10/5/06, Joe Armstrong <<a href="mailto:firstname.lastname@example.org">email@example.com</a>> wrote:<br>> Modules ... thoughts<br>> 1) distribute only one file<br>> 2) modules in file cannot live a life of their own and become
<br>> separated<br>> 3) code loading is faster<br><br>If the modules can't live a life of their own, why would they need to<br>be separate modules? The only advantage I see would be a partitioning<br>of the namespace, but is it a strong enough argument?
<br><br>Actually, I can see a possible application - only one module is<br>visible externally and the others just support it and are hidden (i.e.<br>the compiler mangles the name beyond accidental use). Then the module<br>
namespace would be cleaner too (and no more "app_module" names ;-)<br><br>What would you like to use this for, Joe?<br><br>regards,<br>Vlad<br></blockquote></div><br>