Comments on: Small quirk in RubyFit http://blog.coryfoy.com/2008/01/small-quirk-in-rubyfit/ It's all about delivering Fri, 03 Feb 2012 07:28:23 +0000 hourly 1 http://wordpress.org/?v=3.2.1 By: gpiancastelli http://blog.coryfoy.com/2008/01/small-quirk-in-rubyfit/comment-page-1/#comment-100 gpiancastelli Sun, 28 Dec 2008 02:19:00 +0000 http://blog.cornetdesign.com/?p=97#comment-100 I think that the check on the order of parameters is done to ensure uniform behaviour amongst FitServer implementations that can be called from the command line. If you look at:<br /><br />http://fitnesse.org/FitNesse.FitServerProtocol<br /><br />you will find something like:<br /><br />Command Line Arguments:<br />Java usage: java fit.FitServer [-v] host port socketTicket<br /><br />So, when activating the server from c.l., the verbose option must always be in that specific position. I believe that other FitServer implementations are bound to respect that very same order, and w.r.t. Ruby some tests in test/fit_server_test.rb seem to confirm that (see test_args, test_args_with_verbose, test_bad_args). The check on arg_count should be another hint.<br /><br />I don't know what's the relationship between command line usage and COMMAND_PATTERN usage, but I don't think it would be feasible to break c.l. usage uniformity to gain... well, indeed, to gain what, exactly?<br /><br />I'm still leaving the bug report open, though, with a Postponed resolution<br />and a lower priority. I think that the check on the order of parameters is done to ensure uniform behaviour amongst FitServer implementations that can be called from the command line. If you look at:

http://fitnesse.org/FitNesse.FitServerProtocol

you will find something like:

Command Line Arguments:
Java usage: java fit.FitServer [-v] host port socketTicket

So, when activating the server from c.l., the verbose option must always be in that specific position. I believe that other FitServer implementations are bound to respect that very same order, and w.r.t. Ruby some tests in test/fit_server_test.rb seem to confirm that (see test_args, test_args_with_verbose, test_bad_args). The check on arg_count should be another hint.

I don’t know what’s the relationship between command line usage and COMMAND_PATTERN usage, but I don’t think it would be feasible to break c.l. usage uniformity to gain… well, indeed, to gain what, exactly?

I’m still leaving the bug report open, though, with a Postponed resolution
and a lower priority.

]]>