From: Michael Walter <michael.walter@...>
Date: 2005-04-14T13:06:02+09:00
Subject: Re: assert_equal hates my CPU

Phlip,

On 4/13/05, Phlip <phlip_cpp@yahoo.com> wrote:
> Because assertions passing should be the most common behavior, shouldn't
> that method run like this?
> 
>       def assert_equal(expected, actual, message=nil)
>         assert_block(full_message) do
>              if expected == actual then
>                 ''
>             else
>                 build_message(message, <<EOT, expected, actual)
> <?> expected but was
> <?>.
> EOT
>              end
>         end
>       end
> 

Unbound variable 'full_message'? :\

> Then assert_block() should trigger if its block yields a complaint string.

That's too much magic in the block semantics for me. Without taking a
look into the test sources, mayb you could call some
raise_error(reason) function instead?

Regards,
Michael