Mime-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=UTF-8
Date: Wed, 23 Nov 2022 11:36:08 -0500
Message-Id: <COJTLAKUY6X9.WREYBDDY2UZJ@archlinux-white>
Subject: Re: getopts long options
From: "Sebastian LaVine" <mail@smlavine.com>
To: "Drew DeVault" <sir@cmpwn.com>, "Ember Sawady" <ecs@d2evs.net>, "Tom
 Regner" <tomte@tomsdiner.org>, <~sircmpwn/hare-users@lists.sr.ht>
References: <87k03m12ij.fsf@tomsdiner.org> <COJJMKYOKATA.M5IOFO9BXIK2@monch>
 <COJL7ISEFQFX.3C1Z957SX1KDD@taiga>
In-Reply-To: <COJL7ISEFQFX.3C1Z957SX1KDD@taiga>

On Wed Nov 23, 2022 at 5:02 AM EST, Drew DeVault wrote:
> The getopt module is compatible with POSIX.

Why is POSIX compatibility relevent in this case, and what does
compatibility mean exactly in this context? It is good for C programs to
write to POSIX standards to ensure interoperability between platforms.
But Hare programs only need to worry about writing to the standard
library, which (presumably) is going to be the same on every platform it
is present. The way that the getopt module is used is already very
different from how getopt(3p) is used. There may be an argument for
keeping the getopt module minimal, but I don't think that "POSIX
compatibility" is one of them.