From: arnold@skeeve.com
To: tuhs@tuhs.org, douglas.mcilroy@dartmouth.edu
Subject: Re: [TUHS] Systematic approach to command-line interfaces [ meta issues ]
Date: Sun, 01 Aug 2021 13:48:10 -0600 [thread overview]
Message-ID: <202108011948.171JmAcK001895@freefriends.org> (raw)
In-Reply-To: <CAKH6PiUggct8fuTTU2BQwT5b_grigJg+djdnADi=fzAvnG3Y4A@mail.gmail.com>
Douglas McIlroy <douglas.mcilroy@dartmouth.edu> wrote:
> In realizing the white paper's desire to "have the parser
> provide the results to the program", it's likely that the mechanism
> will, like Yacc, go beyond parsing and invoke semantic actions
> as it identifies tree nodes.
I have to admit that all this feels like overkill. Parsing options
is only a very small part of the real work that a program does.
Speaking for myself, I want something simple and regular that will
get the job done and let me get on with the actual business of
my software. A grammar just for command-line argument parsing feels
like the tail wagging the dog: not nearly enough ROI, at least
for me.
I happen to like the getopt_long interface designed by the GNU
project. It's easy to learn, setup and use. Once it's in place
it's set and forget.
My two cents,
Arnold
next prev parent reply other threads:[~2021-08-01 19:48 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-01 18:17 Douglas McIlroy
2021-08-01 19:48 ` arnold [this message]
2021-08-01 21:30 ` John Cowan
2021-08-02 12:11 ` Steffen Nurpmeso
-- strict thread matches above, loose matches on Subject: below --
2021-07-31 12:25 [TUHS] Systematic approach to command-line interfaces Michael Siegel
2021-07-31 19:20 ` [TUHS] Systematic approach to command-line interfaces [ meta issues ] Jon Steinhart
2021-07-31 21:06 ` Richard Salz
2021-07-31 21:32 ` Jon Steinhart
2021-07-31 21:37 ` Richard Salz
2021-07-31 21:55 ` Jon Steinhart
2021-07-31 22:10 ` Warner Losh
2021-07-31 22:19 ` Larry McVoy
2021-07-31 22:20 ` Jon Steinhart
2021-07-31 23:26 ` Warner Losh
2021-07-31 23:41 ` Jon Steinhart
2021-07-31 22:04 ` Bakul Shah
2021-07-31 22:13 ` Larry McVoy
2021-07-31 22:14 ` Bakul Shah
2021-07-31 22:17 ` Bakul Shah
2021-07-31 22:16 ` Jon Steinhart
2021-07-31 22:20 ` Bakul Shah
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=202108011948.171JmAcK001895@freefriends.org \
--to=arnold@skeeve.com \
--cc=douglas.mcilroy@dartmouth.edu \
--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).