From: "NAKAMURA, Hiroshi" <nahi@keynauts.com>
To: <ruby-core@ruby-lang.org>
Subject: Re: [PATCH] object.c ruby.h (fwd)
Date: Fri, 26 Jul 2002 10:16:32 +0900 [thread overview]
Message-ID: <001801c23441$f3bcf200$85222fc0@sarion.co.jp> (raw)
In-Reply-To: <m2vg74q6zk.fsf@zip.local.thomases.com>
Hi,
> From: Dave Thomas
> Sent: Thursday, July 25, 2002 10:21 PM
> > > I'd expect to be able to test it with an assert(), but currently I
> > > can't without writing extra (and distracting) stuff.
> >
> > Indeed assert() of Test::Unit::Assertions does not test
> true/false.
> > I think that the assert() is too generic and that can blur
> the meaning
> > of an assertion. Perhaps true-false-test may prevent abuse of
> > assert() in rubyunit.
>
> Hmm - I differ here. I'd expect assert() to work the same way as 'if'
> and 'unless' do, so that
>
> assert(x)
>
> would succeed and fail the same as
>
> raise "assertion failed" unless x
+1 to gotoken. assert is for tester. When someone put on
tester's hat, (s)he should assert to check true/false
explicitly, I think.
Back to the main topic about introducing Boolean class,
I don't have any idea because I seldom use TrueClass and
FalseClass with Ruby... Does Ruby/C API user use TrueClass
/FalseClass instead of true/false(instances)?
How about introducing Boolean and aliasing TrueClass and
FalseClass to Boolean?
Regards,
// NaHi
next prev parent reply other threads:[~2002-07-26 1:16 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-24 15:02 [PATCH] object.c ruby.h (fwd) Robert Skarwecki
2002-07-24 16:51 ` Boolean class (Re: [PATCH] object.c ruby.h) Yukihiro Matsumoto
2002-07-24 19:50 ` [PATCH] object.c ruby.h (fwd) GOTO Kentaro
2002-07-24 20:05 ` Dave Thomas
2002-07-25 4:22 ` unifying nil and false (Re: [PATCH] object.c ruby.h) Yukihiro Matsumoto
2002-07-25 4:59 ` Dave Thomas
2002-07-25 6:46 ` Yukihiro Matsumoto
2002-07-25 11:06 ` [PATCH] object.c ruby.h (fwd) GOTO Kentaro
2002-07-25 13:20 ` Dave Thomas
2002-07-25 17:42 ` nobu.nokada
2002-07-25 17:55 ` Dave Thomas
2002-07-25 18:11 ` nobu.nokada
2002-07-25 18:28 ` Dave Thomas
2002-07-25 19:53 ` GOTO Kentaro
2002-07-25 20:34 ` Dave Thomas
2002-07-25 22:23 ` GOTO Kentaro
2002-07-27 8:04 ` Masaki Suketa
2002-07-27 12:40 ` Dave Thomas
2002-08-03 9:04 ` Masaki Suketa
2002-08-05 1:39 ` NAKAMURA, Hiroshi
2002-08-06 11:53 ` Masaki Suketa
2002-08-09 13:20 ` NAKAMURA, Hiroshi
2002-08-10 12:19 ` Masaki Suketa
2002-08-12 3:48 ` NAKAMURA, Hiroshi
2002-07-26 10:11 ` YANAGAWA Kazuhisa
2002-07-31 14:47 ` A truth? patch + benchmarks Christoph
2002-07-31 15:03 ` ts
2002-08-01 6:39 ` Christoph
2002-08-01 7:02 ` Yukihiro Matsumoto
2002-08-02 7:12 ` Christoph
2002-08-02 7:20 ` ts
2002-08-02 8:54 ` Christoph
2002-08-03 9:51 ` Yukihiro Matsumoto
2002-08-05 0:58 ` Christoph
2002-08-05 1:44 ` nobu.nokada
2002-08-16 6:52 ` Mswin32 build flags Christoph
2002-08-16 7:12 ` U.Nakamura
2002-09-03 18:51 ` Christoph
2002-07-26 1:16 ` NAKAMURA, Hiroshi [this message]
2002-07-26 15:23 ` [PATCH] object.c ruby.h (fwd) Michal Rokos
2002-07-26 15:31 ` Dave Thomas
2002-07-26 16:37 ` Yukihiro Matsumoto
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.ruby-lang.org/en/community/mailing-lists/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='001801c23441$f3bcf200$85222fc0@sarion.co.jp' \
--to=ruby-core@ruby-lang.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).