From: Philip Kaludercic <philipk@posteo.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org, "Stefan Monnier" <monnier@iro.umontreal.ca>,
"João Távora" <joaotavora@gmail.com>
Subject: Re: Proposal: Forwards-Compatibility Library for Emacs
Date: Tue, 21 Sep 2021 13:00:16 +0000 [thread overview]
Message-ID: <871r5it76n.fsf@posteo.net> (raw)
In-Reply-To: <83v92uxfto.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 21 Sep 2021 15:40:03 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Stefan Monnier <monnier@iro.umontreal.ca>
>> Cc: emacs-devel@gnu.org
>> Date: Tue, 21 Sep 2021 08:31:39 -0400
>>
>> > By its very nature it is an intrusive package, as it defines functions,
>> > macros and advice outside of the "namespace", but I don't see any way
>> > around that if transparent compatibility is to be provided (anything
>> > else would just replicate dash, s, f, ...).
>>
>> I think this uncleanliness is a bit risky. Better put the definitions
>> in their own namespace. I don't think "transparent compatibility" is
>> worth the trouble here, and I don't think `s`, `f`, ... solve the
>> same problem.
>
> Can symbol-renaming help here, perhaps? I believe João is trying to
> get it ready in time for Emacs 28.
Going by my proposal, the library does nothing when loaded in Emacs
28.1, because it is already compatible to itself. No need for an extra
layer. It is only of interest to older versions, and they won't be able
to make use of symbol-renaming.
--
Philip Kaludercic
next prev parent reply other threads:[~2021-09-21 13:00 UTC|newest]
Thread overview: 66+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-20 23:35 Proposal: Forwards-Compatibility Library for Emacs Philip Kaludercic
2021-09-21 0:30 ` Adam Porter
2021-09-21 4:10 ` Lars Ingebrigtsen
2021-09-21 8:28 ` Philip Kaludercic
2021-09-21 12:31 ` Stefan Monnier
2021-09-21 12:40 ` Eli Zaretskii
2021-09-21 12:50 ` Stefan Kangas
2021-09-21 13:38 ` Arthur Miller
2021-09-21 13:49 ` João Távora
2021-09-21 13:00 ` Philip Kaludercic [this message]
2021-09-21 13:12 ` Eli Zaretskii
2021-09-21 13:28 ` Philip Kaludercic
2021-09-21 13:24 ` João Távora
2021-09-21 13:29 ` Philip Kaludercic
2021-09-21 13:50 ` João Távora
2021-09-21 14:59 ` Lars Ingebrigtsen
2021-09-21 12:58 ` Philip Kaludercic
2021-09-21 13:37 ` Arthur Miller
2021-09-21 13:54 ` Philip Kaludercic
2021-09-21 14:18 ` Arthur Miller
2021-09-21 15:02 ` Lars Ingebrigtsen
2021-09-21 15:40 ` João Távora
2021-09-21 16:10 ` Philip Kaludercic
2021-09-21 16:22 ` João Távora
2021-09-21 17:22 ` Lars Ingebrigtsen
2021-09-21 17:29 ` João Távora
2021-09-21 19:24 ` Stefan Monnier
2021-09-21 21:06 ` Philip Kaludercic
2021-09-21 21:50 ` Stefan Monnier
2021-09-22 6:48 ` Philip Kaludercic
2021-09-22 17:53 ` Stefan Monnier
2021-09-22 18:54 ` Philip Kaludercic
2021-09-22 19:15 ` Stefan Monnier
2021-09-21 21:57 ` Lars Ingebrigtsen
2021-09-21 22:08 ` João Távora
2021-09-21 22:16 ` Lars Ingebrigtsen
2021-09-21 22:24 ` João Távora
2021-09-21 22:25 ` Lars Ingebrigtsen
2021-09-21 22:34 ` João Távora
2021-09-22 6:53 ` Philip Kaludercic
2021-09-22 7:12 ` João Távora
2021-09-22 7:14 ` Arthur Miller
2021-09-21 13:05 ` Philip Kaludercic
2021-09-21 13:27 ` Arthur Miller
2021-09-21 13:45 ` Philip Kaludercic
2021-09-21 14:05 ` Arthur Miller
2021-09-21 22:17 ` Richard Stallman
2021-09-21 22:24 ` Lars Ingebrigtsen
2021-09-22 9:54 ` Philip Kaludercic
2021-10-04 23:00 ` [ELPA] Add compat.el Philip Kaludercic
2021-10-07 7:03 ` Old (static) builds of Emacs Philip Kaludercic
2021-10-07 7:48 ` Michael Albinus
2021-10-07 7:56 ` Philip Kaludercic
2021-10-07 12:49 ` Stefan Monnier
2021-10-07 20:29 ` Philip Kaludercic
2021-10-07 21:21 ` Stefan Monnier
2021-11-30 21:21 ` Philip Kaludercic
2021-12-01 13:15 ` Stefan Monnier
2021-10-07 20:49 ` [ELPA] Add compat.el Philip Kaludercic
2021-10-08 5:56 ` Eli Zaretskii
2021-10-08 9:59 ` Philip Kaludercic
2021-10-08 11:10 ` Eli Zaretskii
2021-10-08 11:35 ` Philip Kaludercic
2021-10-08 7:45 ` Mattias Engdegård
2021-10-08 10:00 ` Philip Kaludercic
2021-10-15 19:08 ` Philip Kaludercic
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://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=871r5it76n.fsf@posteo.net \
--to=philipk@posteo.net \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=joaotavora@gmail.com \
--cc=monnier@iro.umontreal.ca \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).