Thanks for your reply. While I find it a bit odd that someone might want the args behavior the way it is (I guess it seems less versatile to me), I've explored getopts-long per your recommendation and I think I even like it more. My only current gripe with getopts-long is that it doesn't seem to support passing values to long options with a space instead of an "=" (even though one of th examples provided says otherwise, the "--apples" "Granny Smith" bit).
-------- Original Message --------
Subject: Re: [Chicken-users] Bug with #:optional in args egg?
Local Time: June 20, 2017 1:17 AM
UTC Time: June 20, 2017 5:17 AM
From: address@hidden
To: Diego A. Mundo <address@hidden>
address@hidden <address@hidden>
Hello Diego,
I"m not sure whether this is a bug and fixing it is desired. If
changed, it would affect existing programs using the args egg that would
no longer work in the old way. Also, there are programs that do
argument parsing this way, albeit not many and typically only for a few
select arguments, like mysql for passwords (typing a space between -p
and the argument made the password check fail) and compilers (for -L and
alike).
I"ve switched to the getopt-long egg for this reason. While it doesn"t
do as much magic and takes more effort to understand, the command line
interfaces created with it feel completely like proper GNU programs.
Cheers
Vasilij