...@rubyforge.org] On Behalf Of Michael Letterle
Sent: Wednesday, January 07, 2009 11:26 AM
To: ironruby-core@rubyforge.org
Subject: Re: [Ironruby-core] should equal in RubySpecs
require 'mspec'
describe "equals" do
it "compares objects not values" do
a = "a&q
] should equal in RubySpecs
require 'mspec'
describe "equals" do
it "compares objects not values" do
a = "a"
b = "a"
c = a
a.should equal(c)
a.should_not equal(b)
a.should == b
end
end
On Wed, Jan 7, 2009 at 3:48 AM, S
require 'mspec'
describe "equals" do
it "compares objects not values" do
a = "a"
b = "a"
c = a
a.should equal(c)
a.should_not equal(b)
a.should == b
end
end
On Wed, Jan 7, 2009 at 3:48 AM, Shri Borde wrote:
> I noticed this in core\thread\current_spec.rb.
>
>
>
>
I noticed this in core\thread\current_spec.rb.
it "returns the current thread" do
t = Thread.new { Thread.current }
t.value.should equal(t)
Thread.current.should_not equal(t.value)
end
Is this any different than writing "t.value.should == t"? Is either of them the
recommended way
