Hi,

At Fri, 30 Apr 2010 06:15:34 +0900,
Roger Pack wrote in [ruby-core:29890]:
> > I'd suggest that a better way to detect this problem is for
> > assert to fail if a non-String is passed as the second
> > parameter. This won't detect all cases of using assert when
> > you meant assert_equal, but it should catch at lest 90%.
> 
> Yeah something like that could work well.  When would someone want to
> output something that's not a string?

How do you want to show non-string message?  Anyway, you can
use a proc too.

-- 
Nobu Nakada