Peter Bacon Darwin: > What about the "fast-tracking the external Ruby library loading", idea? > In other words, allowing external "IronRuby" library code to be > developed and compiled into a separate assembly so that it can be > loaded into the Ruby runtime via require "...". (Not to be confused > with "requiring" a straight .NET assembly, which of course we can do > already).
Excellent idea. Will pop this to the top of the queue. This will also force us to initialize $: correctly at startup. > This will allow separate OSS projects to be set up that really can have > direct community interaction for those libraries that are not core to > the IronRuby runtime. Let me noodle on this idea this morning. I have some ideas but I wanted to run them past some folks around here first. > In the long run, surely, this is the model that you want to have > anyway. So why not push toward it now? Agreed. Thanks! -John _______________________________________________ Ironruby-core mailing list [email protected] http://rubyforge.org/mailman/listinfo/ironruby-core
