[#237] object.c ruby.h (fwd) — Robert Skarwecki <skaav@...>

Hello everybody,

42 messages 2002/07/24
[#239] Re: [PATCH] object.c ruby.h (fwd) — GOTO Kentaro <gotoken@...> 2002/07/24

At Thu, 25 Jul 2002 00:02:28 +0900,

[#240] Re: [PATCH] object.c ruby.h (fwd) — Dave Thomas <Dave@...> 2002/07/24

GOTO Kentaro <gotoken@notwork.org> writes:

[#246] Re: [PATCH] object.c ruby.h (fwd) — GOTO Kentaro <gotoken@...> 2002/07/25

At Thu, 25 Jul 2002 05:05:46 +0900,

[#247] Re: [PATCH] object.c ruby.h (fwd) — Dave Thomas <Dave@...> 2002/07/25

GOTO Kentaro <gotoken@notwork.org> writes:

[#248] Re: [PATCH] object.c ruby.h (fwd) — nobu.nokada@... 2002/07/25

Hi,

[#249] Re: [PATCH] object.c ruby.h (fwd) — Dave Thomas <Dave@...> 2002/07/25

nobu.nokada@softhome.net writes:

[#250] Re: [PATCH] object.c ruby.h (fwd) — nobu.nokada@... 2002/07/25

Hi,

[#252] Re: [PATCH] object.c ruby.h (fwd) — GOTO Kentaro <gotoken@...> 2002/07/25

At Fri, 26 Jul 2002 03:11:02 +0900,

[#253] Re: [PATCH] object.c ruby.h (fwd) — Dave Thomas <Dave@...> 2002/07/25

GOTO Kentaro <gotoken@notwork.org> writes:

Re: [PATCH] object.c ruby.h (fwd)

From: Dave Thomas <Dave@...>
Date: 2002-07-27 12:40:33 UTC
List: ruby-core #269
Masaki Suketa <masaki.suketa@nifty.ne.jp> writes:

>   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?

There's not much we can do if people call the incorrect method :)

If this is a problem that occurs frequently, then perhaps we could go
the way JUnit went and deprecate 'assert' in favor of 'assert_true'
(or possibly 'assert_truth').


Cheers


Dave

In This Thread