Quoting Zach Dennis :
> On Wed, Apr 11, 2012 at 12:47 PM, Alex Chaffee wrote:
> j.even?should be true
> >
> >>> j.even?.should be true
> >
> >> j.even?.should be_true
> >
> > Not to ignite a flame war, but this is my biggest problem with RSpec: Unless
> > you're an expert at Ruby syntax alrea
On Wed, Apr 11, 2012 at 12:47 PM, Alex Chaffee wrote:
j.even?should be true
>
>>> j.even?.should be true
>
>> j.even?.should be_true
>
> Not to ignite a flame war, but this is my biggest problem with RSpec: Unless
> you're an expert at Ruby syntax already, it's really easy to make
> punctuati
>>> j.even?should be true
>> j.even?.should be true
> j.even?.should be_true
Not to ignite a flame war, but this is my biggest problem with RSpec:
Unless you're an expert at Ruby syntax already, it's really easy to make
punctuation mistakes.
And of course, it should be
j.should be_even
(thoug
On 05/04/2012, at 8:02 AM, Brad Symons wrote:
> I think you have a syntactical error on the line thats throwing the
> error, you state:
>
>>j.even?should be true #throws an error on j == 2, j == 4
>
> should this line not read as:
>
> j.even?.should be true
lol
j.even?.should be
--
Curtis J Schofield
BlazingCloud.net
"Creativity can solve anything"
- George Lois
(source: art & copy)
On Apr 4, 2012, at 3:02 PM, Brad Symons wrote:
> I think you have a syntactical error on the line thats throwing the
> error, you state:
>
>>j.even?should be true #throw
I think you have a syntactical error on the line thats throwing the
error, you state:
> j.even?should be true #throws an error on j == 2, j == 4
should this line not read as:
j.even?.should be true
--
Posted via http://www.ruby-forum.com/.
_
