From: Masaki Suketa <masaki.suketa@...>
Date: 2002-07-27T17:04:02+09:00
Subject: Re: [PATCH] object.c ruby.h (fwd)

In message "Re: [PATCH] object.c ruby.h (fwd)"
    on 02/07/26, GOTO Kentaro <gotoken@notwork.org> writes:

> By the way, how about asking the auther to fit the behavior of
> RubyUnit's assert() to Test::Unit's?

Older version of RubyUnit's assert() behavior is same as Test::Unit's.
The behavior has been changed to avoid confusion of assert and 
assert_equal.

  str = 'foo'
  str += 'bar'
  assert('foobar', str) #  str must be 'foobar'

The above code is not correct(assert_equal should be used instead of
assert). But older version of RubyUnit can not notice it because
1st argument is true.

I am not sure which behavior is better. Can I ignore this kind of 
confusion? Any idea?

  Regards,
  Masaki Suketa