[#686] Wall compilation — Michal Rokos <michal@...>
Hi everybody,
[#688] mkmf.rb - add files to clean and distclean targets — Michal Rokos <michal@...>
Hi,
On Thu, 16 Jan 2003, Michal Rokos wrote:
Hi,
Hi,
On Tue, Jan 21, 2003 at 11:16:39AM +0900, Yukihiro Matsumoto wrote:
Hi,
On Tue, Jan 21, 2003 at 06:38:00PM +0900, Yukihiro Matsumoto wrote:
Hi,
On Tue, Jan 21, 2003 at 11:37:35PM +0900, Yukihiro Matsumoto wrote:
Hi,
Hello,
Hi,
Hi,
Hi,
Hi,
[#708] Documentation for thread.rb — Gavin Sinclair <gsinclair@...>
Hi ruby-core,
[#719] nd_end and NODE_NEWLINE (fwd) — Chad Fowler <chad@...>
[#724] Symbols: More Functionality Wanted — Ryan Pavlik <rpav@...>
I've been discussing this for a bit on #ruby-lang on OPN (or freenode or
Hi,
On 20 Jan 2003 at 15:49, Yukihiro Matsumoto wrote:
Hi --
On Thursday, January 23, 2003, 6:28:04 AM, dblack wrote:
Gavin Sinclair <gsinclair@soyabean.com.au> writes:
Hi,
matz@ruby-lang.org (Yukihiro Matsumoto) writes:
Hi,
On Fri, 24 Jan 2003 03:34:46 +0900
[#730] Comments on matrix.rb — Gavin Sinclair <gsinclair@...>
Hi -core,
[#757] Extensions for Time and ParseDate — Ryan Davis <ryand-ruby@...>
Eric and I have been hacking around and we can't stand the lack of
[#759] Adding Test::Unit to CVS — "Nathaniel Talbott" <nathaniel@...>
Matz has already given me the go-ahead to add Test::Unit to CVS, but I
Nathaniel Talbott wrote:
On Wednesday, January 22, 2003, at 07:56 AM, Dave Thomas wrote:
Re: Adding Test::Unit to CVS
Ryan Davis [mailto:ryand-ruby@zenspider.com] wrote: > On Wednesday, January 22, 2003, at 07:56 AM, Dave Thomas wrote: > > > Is there a reason that rubicon couldn't be included? It seems pretty > > stable (Nathaniel's recent patch notwithstanding). > > I've talked to Matz about this (at rubyconf2002) and he was open to the > idea. I probably need to push on this more and should finally get added > to the core so I can do the work and just get it over with... > > Objections? I'd be happy to take this on and help it evolve over to > Test::Unit. I think the biggest hurdle to the transition is getting a good summarizing TestRunner (like Rubicon's BulkTestRunner) running natively under Test::Unit, which is something I'm already working towards. Once that gets done, it seems that it will mostly be busy work to remove the rubyunit references and convert over fully to Test::Unit (though Dave would know better than I would). The other major thing would be hooking Rubicon somehow in to the build process for Ruby so that it's easy to run as a normal part of development. So I guess I don't have any major objections, except that it seems it would be best to wait (not too long, I hope!) until I get the runner ready to go. Of course, we could go ahead and drop Rubicon in and have it run under rubyunit compatibility, but since converting things over will be a large source of upheaval, it might be better to wait. I'm feeling a bit wishy-washy on what the best strategy is to take. Thoughts? Nathaniel <:((>< + - - | RoleModel Software, Inc. | EQUIP VI