From: Paul Eggert <eggert@cs.ucla.edu>
To: Bruno Haible <bruno@clisp.org>, bug-gnulib@gnu.org
Subject: Re: getprogname: Move declaration from "getprogname.h" to <stdlib.h>
Date: Sat, 21 Jan 2023 22:57:56 -0600 [thread overview]
Message-ID: <02345fc5-de5e-31cf-549f-b573175216f2@cs.ucla.edu> (raw)
In-Reply-To: <3365185.MIaLTWTXVN@nimes>
On 1/21/23 18:10, Bruno Haible wrote:
> I don't understand. Is the #warning that I added misleading?
No, all I meant was that if I see the warning I do the same thing that I
do if I see the error from the missing #include, so there's not much
point in having a transition period with the warning.
Things can be different the transition involves other ports or rarely
used platforms. But this one involves all GNU/Linux platforms so I see
the #warning right away.
next prev parent reply other threads:[~2023-01-22 4:58 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
2023-01-22 4:57 ` Paul Eggert [this message]
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=02345fc5-de5e-31cf-549f-b573175216f2@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=bruno@clisp.org \
--cc=bug-gnulib@gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).