Anonymous user
Talk:Parse command-line arguments: Difference between revisions
Talk:Parse command-line arguments (view source)
Revision as of 21:53, 15 December 2011
, 12 years ago→Task needs a task
(→Possible task: More explanation of my proposal.) |
|||
| (3 intermediate revisions by 2 users not shown) | |||
Line 1:
== Reasons ==
Reasons for this article:
Line 36 ⟶ 37:
The task description should probably specify what is to be accomplished here. --[[User:Rdm|Rdm]] 00:32, 9 August 2011 (UTC)
: It sure does... when will the below be added? — [[User:Crazyfirex|Crazyfirex]] 21:53, 15 December 2011 (UTC)
==Possible task==
Line 55 ⟶ 58:
::Note: No mention of determining an OS. I have tried to leave enough scope to cater for different option syntaxes in different OS's, hoping that what I have nailed down should be workable under more than one OS, and recognising that even within one OS, there may be multiple schemes for specifying options (choose one, probably the one adopted by your languages compiler/interpreter). Please don't invent an options scheme for the task, adhere to some 'standard'. --[[User:Paddy3118|Paddy3118]] 12:44, 13 September 2011 (UTC)
::I guess I didn't want to force adherence to something like <code>progname -b -s 'Some string' -n 1.2345</code> as some might think it doesn't fit their OS or options scheme from some languages library. --[[User:Paddy3118|Paddy3118]] 12:52, 13 September 2011 (UTC)
:Me being me, I might want to add that the program should print a table of (sorted) option name vs option value for sdifferent runs with/without the b option and with options specified in different orders, Hmmm? --[[User:Paddy3118|Paddy3118]] 12:55, 13 September 2011 (UTC)
| |||