Odd error

Testing RSpec
1

with 1.8.6 + rspec 1.2.9 (sorry couldn’t try trunk, see previous post)

I get:

C:\dev\ruby\old\arguments>spec spec\arguments_spec.rb
…F… 0.000000 0.000000 0.000000 ( 0.000000)
.F 0.000000 0.000000 0.000000 ( 0.000000)
0.015000 0.000000 0.015000 ( 0.015625)
.

‘Arguments should raise ArgumentError if passing recoginized keywords’
FAILED
expected: "four, five are not recognized argument keywords",
got: "five, four are not recognized argument keywords" (using
==)
./spec\arguments_spec.rb:140:

(succeeds with 1.9.x)

Thanks.
-r

2

On Wed, Nov 4, 2009 at 3:37 PM, rogerdpack [email protected]
wrote:

‘Arguments should raise ArgumentError if passing recoginized keywords’
FAILED
expected: “four, five are not recognized argument keywords”,
got: “five, four are not recognized argument keywords” (using
==)
./spec\arguments_spec.rb:140:

Please be sure to post the relevant code when you are asking for help on
this list. I’ll take a guess at what is going on, but it’s hard to know
if
I’m barking up the right tree without seeing the code.

If I understand the problem correctly, it’s that the spec is expecting
hash
keys to be in a specific order. In Ruby 1.8, the order of hash keys are
not
guaranteed to be in any specific order, whereas in 1.9, AFAIK, they are.

HTH,
David

3

expected: "four, five are not recognized argument keywords",
got: "five, four are not recognized argument keywords" (using
==)
./spec\arguments_spec.rb:140:

Please be sure to post the relevant code when you are asking for help on
this list. I’ll take a guess at what is going on, but it’s hard to know if
I’m barking up the right tree without seeing the code.

Oops my apologies. For some reason my eyes got crossed and I thought
the strings were identical.
My bad.
-r