Re: Handling getopt for option without optional argument value
From:
Chet Ramey
Subject:
Re: Handling getopt for option without optional argument value
Date:
Sat, 24 Jul 2021 15:00:26 -0400
User-agent:
Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.9.1
On 7/23/21 3:46 PM, lisa-asket@perso.be wrote:
Otherwise I could simply have sent a working implementation. My conclusion
is that it is extremely difficult to do. Bash developers should not get too
upset
admitting this, rather than trying to trash the user trying to do some job.
It may or may not be difficult to do, depending on the specification. How
would you propose to specify these long options in a call to `getopts',
should they accept the optional `=value', how do you specify (or should
you) whether or not the option-argument is optional? These are the issues
that we should consider, and they're nearly all syntactic.
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRU chet@case.edu http://tiswww.cwru.edu/~chet/