From: Gavin Smith <gavinsmith0123@gmail.com>
To: Bruno Haible <bruno@clisp.org>
Cc: bug-gnulib@gnu.org, bug-texinfo@gnu.org
Subject: Re: Avoid gnulib redefinitions - MDA
Date: Sat, 29 Oct 2022 23:20:12 +0100 [thread overview]
Message-ID: <Y12nHIwG+omw4aWp@starmint> (raw)
In-Reply-To: <8965388.O52NOvI7LO@nimes>
On Sun, Oct 30, 2022 at 12:09:50AM +0200, Bruno Haible wrote:
> Gavin Smith wrote:
> > so it sounds like we are better off using #undef before
> > including the Perl headers to avoid depending on undocumented
> > functionalities. Thanks.
>
> Using #undef means to decline all corrections done by Gnulib.
> These are documented in the manual.
In our case, using #undef only avoids a compilation warning about
symbols being redefined. Perl itself redefines fdopen and other
functions, on MS-Windows at least. (I haven't checked why.) We
don't use fdopen, but if we did, it's very likely we would need to
use Perl's redefinition for the module to build properly. I don't
think we'd be able to use Gnulib redefinitions in any case.
The one redefined function from Perl that we do use is "free".
Apparently it's necessary to use Perl's version here (on MS-Windows),
otherwise there can be weird errors.
prev parent reply other threads:[~2022-10-29 22:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-29 13:36 Avoid gnulib redefinitions - MDA, free-posix Gavin Smith
2022-10-29 16:58 ` Paul Eggert
2022-10-29 18:53 ` Gavin Smith
2022-10-30 13:37 ` Avoid gnulib redefinitions - free-posix Bruno Haible
2022-10-29 21:48 ` Avoid gnulib redefinitions - MDA Bruno Haible
2022-10-29 21:59 ` Gavin Smith
2022-10-29 22:09 ` Bruno Haible
2022-10-29 22:20 ` Gavin Smith [this message]
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=Y12nHIwG+omw4aWp@starmint \
--to=gavinsmith0123@gmail.com \
--cc=bruno@clisp.org \
--cc=bug-gnulib@gnu.org \
--cc=bug-texinfo@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).