From: Dave Thomas <Dave@...>
Date: 2001-01-10T02:55:49+09:00
Subject: [ruby-talk:8950] Re: String confusion

Robert Feldt <feldt@ce.chalmers.se> writes:

> On Wed, 10 Jan 2001, Yukihiro Matsumoto wrote:
> 
> > |I just ran into a problem with Strings that really confuses me.
> > 
> > It's a bug.  Here's the patch.  Thank you.
> > 
> Dave&Andy: Would Rubicon have caught this? How complete is it?

Not complete enough, obviously ;-)

Rubicon is kind of languishing, because of a chicken and egg problem.

In the ideal world, it would work like this:

1. All around the world, people with different kinds of machine would
   set up a nightly checkout, build, and Rubicon run. If any tests
   fail, Rubicon automatically e-mails a report to some queue at
   ruby-lang.

2. If these reports correspond to a bug, the interpreter or library is 
   fixed. Otherwise, Rubicon is fixed.

3. If a user finds a bug, the first thing that happens is that a test
   case is added to Rubicon that illustrates the bug. The bug is then
   fixed, and Rubicon run again to verify that the bug went away.

However, right now I don't think the loop is closed. Rubicon isn't
used as part of the development process, and so doesn't get updated as 
bugs are found and fixed.

Now, I'd be happy to participate in keeping it up to date if we could
find some way to get the information to me. Alternatively, I'd happily 
add Rubicon as a module to cvs.ruby-lang.org so that Matz and others
can add tests and use it to validate changes.

Or is there another way of doing it?


Dave