It seems that a number of socket methods were implemented in r108 but deleted in r109!
(not sure what else has gone missing) Cheers, Wayne. ________________________________ From: [EMAIL PROTECTED] [EMAIL PROTECTED] On Behalf Of Peter Bacon Darwin [EMAIL PROTECTED] Sent: Friday, 16 May 2008 4:01 PM To: [email protected] Subject: Re: [Ironruby-core] IronRuby r109 is out Hi Wayne, Socket.gethostname is now implemented (as of r108). Have you regenerated the Initializer.Generated.cs class? My update to r108 did not touch that file and that may be the reason it is not picking it up. Pete From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Wayne Kelly Sent: Friday,16 May 16, 2008 06:34 To: [email protected] Subject: Re: [Ironruby-core] IronRuby r109 is out > From: John Lam (IRONRUBY) [EMAIL PROTECTED] > To: [email protected] > Subject: [Ironruby-core] IronRuby r109 is out > > Next steps are to start looking at running some simple Rails unit tests to > see what > missing APIs fall out of that investigation. I haven't had a chance to investigate this in detail, but my preliminary tests show the following results: (after applying the latest version, plus a number of my own patches) Of the 365 test files required by my gems and rails use case: 315 load successfully The rest fail for the following reasons: 13 - Regexp.new overloads not implemented 11 - Socket::gethostname not implemented 8 - gsub $n bug [#20137] 7 - YAML::Syck::Resolver::use_types_at not implemented 3 - OpenSSL::Digest::OPENSSL_VERSION_NUMBER not defined 2 - Thread::critical= not implemented 1 - trap not implemented 1 - catch not implemented 1 - DATA global variable not defined 1 - IO::sync not implemented 1 - File::writable? not implemented The gsub bug is what's currently preventing gems setup.rb from executing correctly. Cheers, Wayne.
_______________________________________________ Ironruby-core mailing list [email protected] http://rubyforge.org/mailman/listinfo/ironruby-core
