For that case, we may need to add file called 'thread.so.rb'. Tomas
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Wayne Kelly Sent: Sunday, May 18, 2008 5:04 AM To: [email protected] Subject: Re: [Ironruby-core] Code Review: RubyLibsAndYaml > From: Tomas Matousek [EMAIL PROTECTED] > 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 [email protected] http://rubyforge.org/mailman/listinfo/ironruby-core _______________________________________________ Ironruby-core mailing list [email protected] http://rubyforge.org/mailman/listinfo/ironruby-core
