and if i use -o it does overwritting of given files…
is it possible to use both command at once…
That actually seems to be not a question about OptionParser but rather
your implementation, which we cannot see. With OptionParser you can
have both options on the command line. Your code just needs to react
properly (i.e. in your intended sense) on those options.
and if i use -o it does overwritting of given files…
is it possible to use both command at once…
That actually seems to be not a question about OptionParser but rather
your implementation, which we cannot see. With OptionParser you can
have both options on the command line. Your code just needs to react
properly (i.e. in your intended sense) on those options.
Kind regards
robert
thanks for the reply…
what is the use of opts.separator"" in Option Parser
That actually seems to be not a question about OptionParser but rather
your implementation, which we cannot see. With OptionParser you can
have both options on the command line. Your code just needs to react
properly (i.e. in your intended sense) on those options.
Kind regards
robert
thanks for the reply…
what is the use of opts.separator"" in Option Parser
The OptionParser module is so poorly documented it should be stricken
from ruby. Anyone who would let that piece of junk be part of their
programming language needs to have their head examined.
How can we add the classical “–” pseudo-option which says not
to parse the following flags as in
OptParsealready handles this and has for some time.
Thanks Jason and Robert, it works!
Yes as it was not mention in the documentation, I did just try it.
But I had a mistake in my code (using “opt.parse” instead of
“opt.parse!” ).
Now it works.
About the original subject (OptionParser bad documentation)
I agree that we miss a true reference documentation:
http://optionparser.rubyforge.org
give a very good reference (from Jim F.), but not sure it is
the
same package, neither if it is still maintained