From: "rosenfeld (Rodrigo Rosenfeld Rosas)" <rr.rosas@...>
Date: 2012-10-19T03:24:23+09:00
Subject: [ruby-core:48069] [ruby-trunk - Bug #6548] Rake doesn't ignore arguments after --


Issue #6548 has been updated by rosenfeld (Rodrigo Rosenfeld Rosas).


It is not a matter of respect. I do respect Jim's opinion, but this is how I see this.

Clearly this is not expected behavior for any script (in Unix, -- means that additional options should be ignored).

Now if rake was independent from Ruby distribution we should be done and I wouldn't arguee about this decision here.

But it is part of stdlib, and as so, I think this should be a Ruby core developers decision.

I don't think it is reasonable to break expecations of how programs should work. I respect Jim's opinion and I'm grateful for all his work, but I just think we should discuss this decision further more. After all rake is bundled with Ruby, it is not just an isolated gem.
----------------------------------------
Bug #6548: Rake doesn't ignore arguments after --
https://bugs.ruby-lang.org/issues/6548#change-31020

Author: rosenfeld (Rodrigo Rosenfeld Rosas)
Status: Closed
Priority: Normal
Assignee: drbrain (Eric Hodel)
Category: lib
Target version: 2.0.0
ruby -v: ruby 1.9.3p125 (2012-02-16 revision 34643) [x86_64-linux]


I've created this issue first in GitHub before I realized that Rake is now part of stdlib:

https://github.com/jimweirich/rake/issues/115

I'll copy it here:

rake some_task -- some_arg

Raises an error after running some_task:

Don't know how to build task some_arg.


-- 
http://bugs.ruby-lang.org/