From: Eli Zaretskii <eliz@gnu.org>
To: "Aurélien Aptel" <aurelien.aptel+emacs@gmail.com>,
"John Wiegley" <johnw@gnu.org>
Cc: phst@google.com, p.stephani2@gmail.com, emacs-devel@gnu.org
Subject: Re: [PATCH] Reimplement module functions
Date: Sun, 14 May 2017 17:30:27 +0300 [thread overview]
Message-ID: <83zief7bp9.fsf@gnu.org> (raw)
In-Reply-To: <CA+5B0FPH0XLCgBYYR5XjSHak1umgyNQHXtF_X4Zd7Ny3-a7ADw@mail.gmail.com> (message from Aurélien Aptel on Sun, 14 May 2017 13:40:49 +0200)
> From: Aurélien Aptel <aurelien.aptel+emacs@gmail.com>
> Date: Sun, 14 May 2017 13:40:49 +0200
> Cc: Philipp Stephani <p.stephani2@gmail.com>, Philipp Stephani <phst@google.com>,
> Emacs development discussions <emacs-devel@gnu.org>
>
> On Sat, May 13, 2017 at 7:05 PM, Eli Zaretskii <eliz@gnu.org> wrote:
> > I don't think we can simply remove a function that was already present
> > in one or more Emacs releases. We need to provide a backward
> > compatibility layer, and definitely also mention this in NEWS.
>
> Module support is experimental and this was an internal implementation
> detail, I think it's ok to remove it.
I don't think the "experimental" defense will stand in this case: this
function was present in 2 Emacs releases.
It also is easy to provide a back-compatibility shim in this case, so
I think we should. Back-compatibility is nicer to users.
But since others seem to disagree, I'll let John decide on this.
next prev parent reply other threads:[~2017-05-14 14:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-13 14:44 [PATCH] Reimplement module functions Philipp Stephani
2017-05-13 17:05 ` Eli Zaretskii
2017-05-14 3:07 ` Noam Postavsky
2017-05-14 14:11 ` Eli Zaretskii
2017-05-14 11:40 ` Aurélien Aptel
2017-05-14 14:30 ` Eli Zaretskii [this message]
2017-05-14 18:08 ` Philipp Stephani
2017-05-14 18:09 ` Philipp Stephani
2017-05-20 13:37 ` Philipp Stephani
2017-05-20 20:46 ` Paul Eggert
2017-05-21 20:20 ` Philipp Stephani
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=83zief7bp9.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=aurelien.aptel+emacs@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=johnw@gnu.org \
--cc=p.stephani2@gmail.com \
--cc=phst@google.com \
/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).