[Ironruby-core] Opening up our tree to external committers

Curt Hagenlocher curt at hagenlocher.org
Wed Apr 30 23:49:46 EDT 2008

On Wed, Apr 30, 2008 at 8:36 PM, M. David Peterson <m.david at xmlhacker.com>

> On Wed, 30 Apr 2008 21:14:23 -0600, Curt Hagenlocher <curt at hagenlocher.org>
> wrote:
> One advantage of having "one dll per library" is that you can make
> > decisions about which DLL to load based solely on the library name.  Once
> > you have multiple libraries per DLL, you need a more complicated probing or
> > mapping scheme to know which assembly to load.
> >
> Why not meet half way: Generate netmodules who's primary purpose, if I am
> remembering correctly, is the ability to be merged together into a final
> assembly.

This isn't dynamic, though.  There has to be a single manifest for the
assembly that lists all the netmodules.  I imagine it would be desirable to
be able to add a new library simply by copying it into the appropriate
directory without having to register it or relink the assembly.

Curt Hagenlocher
curt at hagenlocher.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/ironruby-core/attachments/20080430/a5159500/attachment.html>

More information about the Ironruby-core mailing list