From: "Arsen Arsenović" <arsen@aarsen.me>
To: Bruno Haible <bruno@clisp.org>
Cc: Eli Zaretskii <eliz@gnu.org>,
GavinSmith0123@gmail.com, sam@gentoo.org, bug-texinfo@gnu.org,
bug-gnulib@gnu.org
Subject: Re: namespacing issues with Gnulib
Date: Thu, 08 Dec 2022 21:19:55 +0100 [thread overview]
Message-ID: <867cz1prsf.fsf@aarsen.me> (raw)
In-Reply-To: <1958921.NnIJQXNAa5@nimes>
[-- Attachment #1: Type: text/plain, Size: 242 bytes --]
Bruno Haible <bruno@clisp.org> writes:
> Any other ideas?
The one that pops to mind is prefixing everything with ``gl_'', and
exposing aliases maybe. The former is unergonomic and latter is
fragile, though.
--
Arsen Arsenović
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 381 bytes --]
next prev parent reply other threads:[~2022-12-08 20:26 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-07 20:57 -Wlto-type-mismatch warning in error() Sam James
2022-12-07 21:10 ` Arsen Arsenović
2022-12-07 21:37 ` Gavin Smith
2022-12-08 0:21 ` Bruno Haible
2022-12-08 6:16 ` Eli Zaretskii
2022-12-08 8:25 ` Arsen Arsenović via Gnulib discussion list
2022-12-08 10:55 ` Eli Zaretskii
2022-12-08 11:31 ` Arsen Arsenović
2022-12-08 19:00 ` namespacing issues with Gnulib Bruno Haible
2022-12-08 20:10 ` Eli Zaretskii
2022-12-08 20:19 ` Arsen Arsenović [this message]
2022-12-08 20:54 ` Paul Eggert
2022-12-10 1:48 ` -Wlto-type-mismatch warning in error() Gavin Smith
2022-12-10 1:50 ` Gavin Smith
2022-12-10 21:42 ` Paul Eggert
2022-12-11 4:24 ` Jeffrey Walton
2022-12-09 12:00 ` Florian Weimer
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=867cz1prsf.fsf@aarsen.me \
--to=arsen@aarsen.me \
--cc=GavinSmith0123@gmail.com \
--cc=bruno@clisp.org \
--cc=bug-gnulib@gnu.org \
--cc=bug-texinfo@gnu.org \
--cc=eliz@gnu.org \
--cc=sam@gentoo.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).