I've actually already got Optparse and MSpec working. That's the new spec runner that I'm almost ready to commit. I sent it through our internal checkin troll tonight, and if all goes well I will send a code review first thing Monday if not sooner.
I would like to see your catch parse implementation and any other patches to the mspec runner you have. Thanks, Jim D ________________________________ From: [EMAIL PROTECTED] [EMAIL PROTECTED] On Behalf Of Michael Letterle [EMAIL PROTECTED] Sent: Friday, May 16, 2008 3:15 PM To: [email protected] Subject: Re: [Ironruby-core] Toward MSpec I made it this far :) C:\Mike\VS08Proj\IronRuby\trunk\build\debug>ir -D "c:\Mike\Dev\rubyspec\mspec\bin\mspec" -h mspec [COMMAND] [options] (FILE|DIRECTORY|GLOB)+ The mspec command sets up and invokes the sub-commands (see below) to enable, for instance, running the specs with different implementations like ruby, jruby, rbx, etc. I produced a pretty naive implementation of catch/throw that seems pretty functional for the moment, I think the sticking point now is regex's actually.. On Fri, May 16, 2008 at 4:59 PM, Michael Letterle <[EMAIL PROTECTED]<mailto:[EMAIL PROTECTED]>> wrote: Just the end of the week update. I haven't been as active these last few months due to Cleveland Day of .NET planning, but that's this Saturday so hopefully soon I can get back in full swing. Right now I'm playing with getting MSpec (the RubySpec runner), running under IronRuby. The major hurdle right now seems to be that catch/throw isn't implemented. Bug #19888 was also an issue, which I submitted a patch for today. -- Michael Letterle [Polymath Prokrammer] http://blog.prokrams.com -- Michael Letterle [Polymath Prokrammer] http://blog.prokrams.com
_______________________________________________ Ironruby-core mailing list [email protected] http://rubyforge.org/mailman/listinfo/ironruby-core
