[Ironruby-core] Code Review: RubyLibsAndYaml

Tomas Matousek Tomas.Matousek at microsoft.com
Sun May 18 19:55:46 EDT 2008

For that case, we may need to add file called 'thread.so.rb'.


-----Original Message-----
From: ironruby-core-bounces at rubyforge.org [mailto:ironruby-core-bounces at rubyforge.org] On Behalf Of Wayne Kelly
Sent: Sunday, May 18, 2008 5:04 AM
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Code Review: RubyLibsAndYaml

> From: Tomas Matousek [Tomas.Matousek at microsoft.com]
> Sent: Sunday, 18 May 2008 2:47 PM
> To: IronRuby External Code Reviewers
> Subject: [Ironruby-core] Code Review: RubyLibsAndYaml
> The mapping from Ruby library name to the assembly and namespace is established via .rb files:
> thread.rb:
> load_assembly 'IronRuby.Libraries', 'Ruby.StandardLibrary.Threading'
> openssl.rb:
> load_assembly 'IronRuby.Libraries', 'Ruby.StandardLibrary.OpenSsl'
> The files are included in the solution and their build action is set to "copy if new", which means they
> are copied to the output directory during the build. ir.exe includes the directory it is located in into the
> load paths list ($:), so the .rb files copied there are found by the standard Ruby require/load mechanism.

So what if some legacy code requires 'thread.so' or 'opensll.so'? Can we set it up so that it automatically loads the corresponding library?
Ironruby-core mailing list
Ironruby-core at rubyforge.org

More information about the Ironruby-core mailing list