Anonymous user
Talk:Parse command-line arguments: Difference between revisions
Talk:Parse command-line arguments (view source)
Revision as of 10:57, 11 September 2011
, 12 years ago→Command line parameter conventions: Complex area, alas
m (moved Talk:Parsing command-line arguments to Talk:Parse command-line arguments: Remove extra -ing, see Rosetta Code:Village Pump/Renaming to rename tasks) |
(→Command line parameter conventions: Complex area, alas) |
||
Line 26:
I have also got some part written code that will follow the conventions, but the project is in its infancy, and not ready for prime time here on rosettacode (because it is in a language that I am still learning). It will eventually become available as library code, providing an alternative parser to getopt (but using different conventions). [[User:Markhobley|Markhobley]] 19:37, 6 August 2011 (UTC)
: There are ''many different'' conventions in use. The only one that I've seen that is really close to universal is the one that says that a “<tt>--</tt>” on its own indicates the end of the options and the start of the file arguments. Otherwise, they're all over the map. It gets even more complex on Windows, where some programs are downright idiosyncratic in their command line handling. Because of this, it would really help in this task if it was nailed down exactly what sort of command line options ''should'' be parsed as well as a specific set to actually parse the sense out of. –[[User:Dkf|Donal Fellows]] 10:57, 11 September 2011 (UTC)
== Ruby example ==
| |||