Captain a écrit :
Le Tue, 27 Nov 2007 10:25:31 +0100,
alxx <[EMAIL PROTECTED]> a écrit :
Patrick says that our patch could be restrictive because we cannot
user options for argument like captain would like...
I don't understand very well what you're saying
We now that our patch is restrictive, it's is purpose.
Works today is to make OPTHash strict or unstrict.
Better way will be to be strict/unstrict for each option and is
argument.
If we couldn't code something with the to possibilities, I think fork
will be necessary.
And Patrick added that they were some implementation problems...
I comment this in next Patrick quotes
do we decide to use opthash normal? or do we implement an option
-strict which specifies that an option must not be passed as an
argument...
My conclusion at the end of this email.
On Nov 20, 2007 7:35 AM, Patrick Davalan <[EMAIL PROTECTED]> wrote:
1 ) Conceptually it's a bit restrictive,
You may not type :
$ myscript.rb --file -f
which probably means that you cannot use a file '-f'?
You may want this, but maybe sometimes you won't in some scripts.
There should be a switch to enable/disable this feature at parser
creation and/or some way for the user to override it.
Could we answer to is queries with few lines of codes ?
With add a control value when we make option list :
Names : files file f
description : in files
Strict : 0 or 1
Why shouldn't it be a special variable like "strict = 1", and so the
option wil be strict, overwise (by default) it wont't be strict ?
--
Beber
--
[email protected]
Unsubscribe: [EMAIL PROTECTED]
Archives: http://lists.else-projects.org/archives/devel
Jabber-MUC: [EMAIL PROTECTED]
