Re: arguments parsing, wildcard matcher

From: christian.engstrom_at_[hidden]
Date: 2001-11-29 10:10:09

>  The only problem with interspersing options 
> and arguments is ambiguity arising with optional parameters.
> "--foo bar" can mean two different things if "foo" takes optional 
> parameter. 

One possible way of resolving this particular ambiguity is to let the 
command line parser impose the syntax rule that if an option takes an 
argument, there must be an "=" sign between the option name and the 
argument.  This would mean that "--foo = bar" is always an option 
with an argument, whereas "--foo bar" is always an option and a 
parameter.

This syntax rule is consistent with how most programs work under MS-
DOS, and is also consistent with how for instance Emacs handles (most 
of its) long options.  While it may not be consistent with how most 
Unix programs presently handle short options, it wouldn't do any harm 
to the legibility there either, IMO.