From: Bruno Haible <bruno@clisp.org>
To: bug-gnulib@gnu.org, Paul Eggert <eggert@cs.ucla.edu>
Subject: Re: getprogname: Move declaration from "getprogname.h" to <stdlib.h>
Date: Sun, 22 Jan 2023 01:10:38 +0100 [thread overview]
Message-ID: <3365185.MIaLTWTXVN@nimes> (raw)
In-Reply-To: <92099878-2f9b-846d-151d-cccdb9cdd59f@cs.ucla.edu>
Paul Eggert wrote:
> I ... wouldn't object to a very short transition period
Short transition periods tend to cause unnecessary hassle to some users.
I therefore favour 1 year or 2 years as a transition period.
> since the current #warning is something I would treat
> like a diagnostic that getprogname.h is missing.
I don't understand. Is the #warning that I added misleading? Then, by
all means, please provide a better message. (The compiler typically
reports the location of the warning; so, from the compiler's diagnostic
it should be clear that there still is a getprogname.h. No?)
Bruno
next prev parent reply other threads:[~2023-01-22 0:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-21 8:56 getprogname: Move declaration from "getprogname.h" to <stdlib.h> Bruno Haible
2023-01-21 21:19 ` Paul Eggert
2023-01-22 0:10 ` Bruno Haible [this message]
2023-01-22 4:57 ` Paul Eggert
2023-01-22 10:04 ` transition periods Bruno Haible
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
List information: https://lists.gnu.org/mailman/listinfo/bug-gnulib
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3365185.MIaLTWTXVN@nimes \
--to=bruno@clisp.org \
--cc=bug-gnulib@gnu.org \
--cc=eggert@cs.ucla.edu \
/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).