[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Handling options with optional arguments with getopts
From: |
Lawrence Velázquez |
Subject: |
Re: Handling options with optional arguments with getopts |
Date: |
Fri, 27 Aug 2021 13:32:45 -0400 |
User-agent: |
Cyrus-JMAP/3.5.0-alpha0-1125-g685cec594c-fm-20210825.001-g685cec59 |
On Fri, Aug 27, 2021, at 1:20 PM, nigelberlinguer wrote:
> ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
> On Friday, August 27, 2021 4:02 PM, Robert Elz <kre@munnari.OZ.AU> wrote:
> > XBD 12.2 guideline 7 is:
> >
> > Guideline 7: Option-arguments should not be optional.
> >
> > That is, if you want to be able to give an option arg, or not give one,
> > those should be implemented as 2 separate options.
>
> It should be noted though, that the POSIX requirement by "Guideline 7"
> is not guided by actual portability in the technical sense but by a
> rule written in the POSIX standard. Perhaps there should be an update
> to POSIX on what is actually portable or not
https://www.opengroup.org/austin/lists.html
--
vq
- Handling options with optional arguments with getopts, nigelberlinguer, 2021/08/27
- Re: Handling options with optional arguments with getopts, Robert Elz, 2021/08/27
- Re: Handling options with optional arguments with getopts, Robert Elz, 2021/08/27
- Handling options with optional arguments with getopts, nigelberlinguer, 2021/08/27
- Handling options with optional arguments with getopts, nigelberlinguer, 2021/08/27
- Handling options with optional arguments with getopts, hancooper, 2021/08/28
- Re: Handling options with optional arguments with getopts, Robert Elz, 2021/08/28
- Handling options with optional arguments with getopts, hancooper, 2021/08/28