public inbox for cygwin-announce@cygwin.com
 help / color / mirror / Atom feed
From: Andrew Schulman <andrex.e.schulman@gmail.com>
To: cygwin-announce@cygwin.com
Subject: libargp-20230708-1
Date: Sun, 9 Jul 2023 06:13:42 -0400	[thread overview]
Message-ID: <CAJOCpN3bF_8dd49jPq5w2AXQ_L7Yxzmzaa3mg-PgShY6F1=6vw@mail.gmail.com> (raw)

A new release of libargp, version 20230708-1, is available in Cygwin. This
release contains many small improvements and bug fixes since the last release,
20110921-3 - yes, 12 years ago. For a list of the changes, see the upstream
commit log[1].

Argp is an interface for parsing unix-style argument vectors. Argp provides
features unavailable in the more commonly used getopt interface. These
features include automatically producing output in response to the ‘--help’
and ‘--version’ options, as described in the GNU coding standards. Using argp
makes it less likely that programmers will neglect to implement these
additional options or keep them up to date.

Argp also provides the ability to merge several independently defined option
parsers into one, mediating conflicts between them and making the result
appear seamless. A library can export an argp option parser that user programs
might employ in conjunction with their own option parsers, resulting in less
work for the user programs. Some programs may use only argument parsers
exported by libraries, thereby achieving consistent and efficient
option-parsing for abstractions implemented by the libraries.

The header file <argp.h> should be included to use argp.

Home page: https://www.gnu.org/software/gnulib/
Documentation: https://www.gnu.org/software/libc/manual/html_node/Argp.html
License: LGPL-3

Andrew Schulman

[1]https://git.savannah.gnu.org/gitweb/?p=gnulib.git&a=search&h=HEAD&st=commit&s=argp

                 reply	other threads:[~2023-07-09 10:14 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='CAJOCpN3bF_8dd49jPq5w2AXQ_L7Yxzmzaa3mg-PgShY6F1=6vw@mail.gmail.com' \
    --to=andrex.e.schulman@gmail.com \
    --cc=cygwin-announce@cygwin.com \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).