[Ironruby-core] RubySpec and Version Targeting
Tomas.Matousek at microsoft.com
Sat Jun 19 12:43:30 EDT 2010
I don't think it's worth the effort. We're targeting 1.9 for the next major release and I assume 1.9 is the same as 1.8.7 regarding CipherError so let's do whatever 1.9 does.
From: ironruby-core-bounces at rubyforge.org [mailto:ironruby-core-bounces at rubyforge.org] On Behalf Of Jim Deville
Sent: Saturday, June 19, 2010 12:13 AM
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] RubySpec and Version Targeting
If it's just a namespace change, I would target both using the RubyCompatibility flags that get set in the option parser. If you look around, you should be able to find examples related to encodings, enumerable or method names. Search for the file RubyCompatibility.cs, then search for uses of the enum.
RubySpec gets its guard information from the version that the implementation reports, so in our case, passing the flag -187 to ir.exe puts us in 1.8.7 mode. Passing -T"-187" to mspec will cause mspec to pass that flag to ir.
From: Will Green <will at hotgazpacho.org>
Sent: Friday, June 18, 2010 9:16 PM
To: ironruby-core <ironruby-core at rubyforge.org>
Subject: [Ironruby-core] RubySpec and Version Targeting
So, I've finally started doing some work on code for the 30-something failing OpenSSL specs. The first one I've come across is openssl\cipher_spec. There are two different descriptions of the spec here: one for version up to 1.8.7, and one for 1.8.7 (I guess they changed the namespace of CipherError in 1.8.7). What I'm looking for is some guidance. Should I implement the 1.8.6 version, or the 1.8.7 version? If the latter, how do I tell mspec that it should be running as 1.8.7?
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Ironruby-core