From: Paul Eggert <eggert@cs.ucla.edu>
To: Gavin Smith <GavinSmith0123@gmail.com>,
bug-gnulib@gnu.org, bug-texinfo@gnu.org
Subject: Re: Avoid gnulib redefinitions - MDA, free-posix
Date: Sat, 29 Oct 2022 09:58:25 -0700 [thread overview]
Message-ID: <916fe3b7-0ace-fa15-2282-2f6571aba26c@cs.ucla.edu> (raw)
In-Reply-To: <Y10sTbYUvG3TKGbt@starmint>
On 2022-10-29 06:36, Gavin Smith wrote:
> Here is one idea. When
> using a module like 'free-posix', if it is loaded as a dependency only,
> use the redefinition in Gnulib code only, but do not override symbols
> in user code. It would be as if there were two modules, say
> gl-free-posix and free-posix, where gl-free-posix made the redefinition
> of rpl_gl_free and free-posix (requested by the user) redirected rpl_free
> to rpl_gl_free.
If it's just 'free', I might prefer the latter solution, to underline
the special case and to avoid even more complexity in gnulib-tool. Is
that something you could write?
If this problem occurs with lots of other symbols perhaps we'd need
something more like the former, though. This would need more hacking, I
expect.
next prev parent reply other threads:[~2022-10-29 16:58 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 [this message]
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
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=916fe3b7-0ace-fa15-2282-2f6571aba26c@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=GavinSmith0123@gmail.com \
--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).