From: Rich Salz <rich.salz@gmail.com>
To: Aaron <aaronscohen@gmail.com>
Cc: tuhs@tuhs.org
Subject: [TUHS] Re: Of flags and keyletters
Date: Sun, 3 Mar 2024 16:24:11 -0500 [thread overview]
Message-ID: <CAFH29to2nda668ZkYCR0N2yWD81RUb5=+Jf6n1bAY9VqGkTRBQ@mail.gmail.com> (raw)
In-Reply-To: <9C2BE9BE-F241-416A-9966-820FB21FD5C0@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 513 bytes --]
On Sun, Mar 3, 2024 at 12:38 PM Aaron <aaronscohen@gmail.com> wrote:
> Having written the first versions of getopt(3), getopt(1), and associated
> man pages around 1979 ...
>
I always thought that this was a brilliant piece of engineering. In less
than 70 lines, it was a clever, but not obtuse, bit of code to handle the
most common option/flag/switch usages that pervaded the Unix ecosystem at
the time. Thanks for that!
Source: https://www.linux.co.cr/unix-source-code/review/1985/1103.html
[-- Attachment #2: Type: text/html, Size: 898 bytes --]
next prev parent reply other threads:[~2024-03-03 21:24 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-02 22:14 Noel Chiappa
2024-03-03 17:38 ` Aaron
2024-03-03 17:52 ` Larry McVoy
2024-03-03 19:28 ` Aaron
2024-03-03 18:44 ` [TUHS] Re: getopt Phil Budne
2024-03-03 21:24 ` Rich Salz [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-03-01 15:49 [TUHS] Of flags and keyletters Douglas McIlroy
2024-03-01 16:23 ` [TUHS] " Steve Nickolas
2024-03-01 19:44 ` Paul Winalski
2024-03-01 16:56 ` Bakul Shah via TUHS
2024-03-02 0:33 ` silas poulson via TUHS
2024-03-02 18:53 ` Lars Brinkhoff
2024-03-02 18:24 ` Paul Winalski
2024-03-02 18:35 ` Warner Losh
2024-02-29 17:21 [TUHS] " Dave Horsfall
2024-02-29 17:59 ` [TUHS] " segaloco via TUHS
2024-03-01 5:30 ` Dave Horsfall
2024-03-01 5:44 ` G. Branden Robinson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAFH29to2nda668ZkYCR0N2yWD81RUb5=+Jf6n1bAY9VqGkTRBQ@mail.gmail.com' \
--to=rich.salz@gmail.com \
--cc=aaronscohen@gmail.com \
--cc=tuhs@tuhs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).