# Toward MSpec **URL:** \ **Category:** IronRuby\ **Created:** [May 16, 2008, 11:00pm UTC](https://www.ruby-forum.com/t/toward-mspec/137859 "2008-05-16T23:00:46Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![dreamwave](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/d/7feea3/32.png) [@dreamwave](https://www.ruby-forum.com/u/dreamwave)\ **Post date:** [May 16, 2008, 11:00pm UTC](https://www.ruby-forum.com/t/toward-mspec/137859/1 "2008-05-16T23:00:46Z")
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. ---
**Author:** ![dreamwave](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/d/7feea3/32.png) [@dreamwave](https://www.ruby-forum.com/u/dreamwave)\ **Post date:** [May 17, 2008, 12:16am UTC](https://www.ruby-forum.com/t/toward-mspec/137859/2 "2008-05-17T00:16:26Z")
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 L. \< ---
**Author:** ![dreamwave](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/d/7feea3/32.png) [@dreamwave](https://www.ruby-forum.com/u/dreamwave)\ **Post date:** [May 17, 2008, 5:28am UTC](https://www.ruby-forum.com/t/toward-mspec/137859/3 "2008-05-17T05:28:48Z")
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: removed\_email\_address@domain.invalid [removed\_email\_address@domain.invalid] On Behalf Of Michael L. [removed\_email\_address@domain.invalid] Sent: Friday, May 16, 2008 3:15 PM To: removed\_email\_address@domain.invalid 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 L. \ 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 L. [Polymath Prokrammer] [http://blog.prokrams.com](http://blog.prokrams.com) ---
**Author:** ![dreamwave](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/d/7feea3/32.png) [@dreamwave](https://www.ruby-forum.com/u/dreamwave)\ **Post date:** [May 17, 2008, 3:15pm UTC](https://www.ruby-forum.com/t/toward-mspec/137859/4 "2008-05-17T15:15:34Z")
I haven’t patched MSpec at all, the catch/throw is extremely naive, I can send you my current patch off-list 🙂 On Fri, May 16, 2008 at 11:24 PM, Jim D. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)