Talk:Parse command-line arguments

From Rosetta Code
Revision as of 10:57, 11 September 2011 by rosettacode>Dkf (→‎Command line parameter conventions: Complex area, alas)

Reasons for this article:

  • Getopt documentation is often too sparse to be useful
  • Different languages have different pattern syntax (think C's "a:b:cd" getopt syntax)
  • As with ScriptedMain, this behavior is as useful as it is obscure.
  • getopt is not Google-friendly: the results tend to be C programs embedding the language in question.

The phone call example is just a quick example. I think we should define a more useful CLI example for each language. 

pmath: Perform mathematical operations.
Examples:
Usage
./pmath.rb -h
Fibonacci
./pmath.rb --fib 100
e raised to a power
./pmath.rb -e 2

--User:Mcandre

Command line parameter conventions

I have some (currently incomplete) documentation relating to command line parameter conventions that you may wish to consider as part of this project.

http://computerconventions.wikia.com/wiki/Command_line_parameter_conventions

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). 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 “--” 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. –Donal Fellows 10:57, 11 September 2011 (UTC)

Ruby example

What if both -d and -e are given? Then only the last one applies? That seems kinda fragile. --166.250.34.11 19:47, 8 August 2011 (UTC)

Task needs a task

The task description should probably specify what is to be accomplished here. --Rdm 00:32, 9 August 2011 (UTC)

Retrieved from "https://rosettacode.org/wiki/Talk:Parse_command-line_arguments?oldid=197372"