# Command line Option Parsing broken

**URL:** <https://www.ruby-forum.com/t/command-line-option-parsing-broken/170451>\
**Category:** IronRuby\
**Created:** [June 17, 2009, 6:51pm UTC](https://www.ruby-forum.com/t/command-line-option-parsing-broken/170451 "2009-06-17T18:51:49Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![hotgazpacho](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/h/a587f6/32.png) [@hotgazpacho](https://www.ruby-forum.com/u/hotgazpacho)\
**Post date:** [June 17, 2009, 6:51pm UTC](https://www.ruby-forum.com/t/command-line-option-parsing-broken/170451/1 "2009-06-17T18:51:49Z")

</div>

Hot on the heels of my blog post about getting Cucumber working with  
IronRuby, I’ve discovered that some change in the last 2 weeks has  
caused  
igem to stop parsing command line arguments correctly. The problem is  
that  
it sees arguments like --bindir as the name of a gem to install, rather  
than  
a command line argument. I came to this conclusion be attaching the  
debugger  
at  
%MERLIN\_ROOT%\Languages\Ruby\Libraries.LCA\_RESTRICTED\Builtins\IoOps.cs  
to  
the running ir.exe process.

This doesn’t stop Cucumber from installing; you just omit the command  
line  
args, but the executable wrappers get installed to  
%MERLIN\_ROOT%\Bin\Debug,  
which, as I pointed out, gets clobbered every time you recompile.

I have filed a bug report on Codeplex:  
[http://ironruby.codeplex.com/WorkItem/View.aspx?WorkItemId=1585](http://ironruby.codeplex.com/WorkItem/View.aspx?WorkItemId=1585)

Let me know if any more detail would be helpful.