Uh, yeah. Thanks for  correcting my method arguments David.

On Wed, Oct 8, 2008 at 10:16 AM, David A. Black <dblack / rubypal.com> wrote:
> Hi --
>
> On Thu, 9 Oct 2008, Jim Freeze wrote:
>
>> So, currently we have
>>
>>  assert_equal a == b   # I assert that a equals b
>>  assert_equal a != b   # I assert that a does not equal b
>
> It's:
>
>  assert_equal(a,b)
>  assert_not_equal(a,b)
>
> which is similar to:
>
>  assert(a == b)
>  assert(a != b)
>
>> So, is the new plan to move to
>>
>>  assert_equal a == b
>>  refute_equal a == b  # I assert not that a == b
>>
>> If so, that is hard for me to parse.
>> A few examples I think would help me understand the exact proposal.
>
> I think it would be:
>
>  refute_equal(a,b)
>
> and so forth.
>
>
> David
>
> --
> Rails training from David A. Black and Ruby Power and Light:
>  Intro to Ruby on Rails  January 12-15   Fort Lauderdale, FL
>  Advancing with Rails    January 19-22   Fort Lauderdale, FL *
>  * Co-taught with Patrick Ewing!
> See http://www.rubypal.com for details and updates!
>
>



-- 
Jim Freeze