[#1147] Copying RVALUE — why the lucky stiff <ruby-core@...>

Hello, everyone. Hope you are all doing well.

18 messages 2003/06/17
[#1155] Re: Copying RVALUE — matz@... (Yukihiro Matsumoto) 2003/06/20

Hi,

[#1157] Re: Copying RVALUE — why the lucky stiff <ruby-core@...> 2003/06/20

Yukihiro Matsumoto (matz@ruby-lang.org) wrote:

[#1173] class.c code cleanup (rb_class_*_instance_methods) — Matthew Dempsky <jivera@...>

Hi, I'm new to this mailing list so I don't know the procedure for

15 messages 2003/06/22
[#1174] Re: [Patch] class.c code cleanup (rb_class_*_instance_methods) — nobu.nokada@... 2003/06/22

Hi,

[#1175] Re: [Patch] class.c code cleanup (rb_class_*_instance_methods) — Matthew Dempsky <jivera@...> 2003/06/22

On Sun, 2003-06-22 at 05:36, nobu.nokada@softhome.net wrote:

[#1176] Re: [Patch] class.c code cleanup (rb_class_*_instance_methods) — nobu.nokada@... 2003/06/22

Hi,

[#1193] Re: [Patch] class.c code cleanup (rb_class_*_instance_methods) — Matthew Dempsky <jivera@...> 2003/06/25

On Sun, 2003-06-22 at 07:41, nobu.nokada@softhome.net wrote:

[#1177] Re: In 1.8.0 nil.to_s is not the same as "" — ts <decoux@...>

14 messages 2003/06/22

Re: Rubicon questions

From: Dave Thomas <dave@...>
Date: 2003-06-15 15:52:31 UTC
List: ruby-core #1142
Chad Fowler wrote:

> I'm sure that any help on Rubicon would be welcome, but it's Dave's baby 
> (he's out of town, I believe).

Rubicon was an attempt to give the Ruby committees a way to test 
changes, and to document differences between versions (using the 
versioning tests).

I'm really not in a position to be able to reverse engineers every CVS 
commit into a set of tests: in an ideal world, the tests would be 
updated by the author of every functional change.

I view Rubicon as a totally shared resource. If folks have fixes or new 
tests to apply, I'd welcome them.


Cheers



Dave


In This Thread