From: Robert Skarwecki <skaav@gmx.net>
To: <ruby-core@ruby-lang.org>
Subject: [PATCH] object.c ruby.h (fwd)
Date: Thu, 25 Jul 2002 00:02:28 +0900 [thread overview]
Message-ID: <Pine.LNX.4.33.0207241658220.25951-100000@natalie.stuwo.fh-heilbronn.de> (raw)
Hello everybody,
my name is Robert Skarwecki and this is my first contribution to the Ruby
development.
The patch implements the ToDo task "introduce Boolean class; super of
TrueClass, FalseClass".
A quick test shows the result:
$ ruby -e "puts true.class.ancestors.join(',')"
TrueClass,Object,Kernel
$ ./ruby -e "puts true.class.ancestors.join(',')"
TrueClass,BooleanClass,Object,Kernel
Here are the patched files. Do they reflect the finished state of the task
or is there anything else left to do, if so, what is it ?
Index: object.c
===================================================================
RCS file: /src/ruby/object.c,v
retrieving revision 1.81
diff -r1.81 object.c
29a30
> VALUE rb_cBooleanClass;
1382c1383,1387
< rb_cTrueClass = rb_define_class("TrueClass", rb_cObject);
---
> rb_cBooleanClass = rb_define_class("BooleanClass", rb_cObject);
> rb_undef_method(CLASS_OF(rb_cBooleanClass), "allocate");
> rb_undef_method(CLASS_OF(rb_cBooleanClass), "new");
>
> rb_cTrueClass = rb_define_class("TrueClass", rb_cBooleanClass);
1391c1396
< rb_cFalseClass = rb_define_class("FalseClass", rb_cObject);
---
> rb_cFalseClass = rb_define_class("FalseClass", rb_cBooleanClass);
Index: ruby.h
===================================================================
RCS file: /src/ruby/ruby.h,v
retrieving revision 1.66
diff -r1.66 ruby.h
553a554
> EXTERN VALUE rb_cBooleanClass;
Bye,
Robert
next reply other threads:[~2002-07-24 15:51 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-24 15:02 Robert Skarwecki [this message]
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 ` [PATCH] object.c ruby.h (fwd) NAKAMURA, Hiroshi
2002-07-26 15:23 ` 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=Pine.LNX.4.33.0207241658220.25951-100000@natalie.stuwo.fh-heilbronn.de \
--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).