From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Eli Zaretskii <eliz@gnu.org>
Cc: "T.V Raman" <raman@google.com>,
cpitclaudel@gmail.com, emacs-devel@gnu.org
Subject: Re: More reliable byte compilation, take 45
Date: Mon, 04 Oct 2021 15:18:30 -0400 [thread overview]
Message-ID: <jwvee90k3jm.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <837des6479.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 04 Oct 2021 21:21:46 +0300")
> Why do you assume that starting from .elc will have fewer problems
> than starting from .el?
Converting a `.elc` file to a `.eln` file can be done by a pure function
with no need for any extra information.
In contrast, converting a `.el` to a `.elc` or `.eln` requires extra
information (typically extra files that define macros and functions used
during macro expansion, plus `load-path` settings to find those files, or
commands to load those files, sometimes in a particular order).
Often this extra information follows the usual practice, in which case
Emacs will find that info without us noticing, but not always (in which
case you'll typically need a special Makefile to build the package, or
an extra ELisp file dedicated to compiling the other files).
ELPA has encouraged packages to better follow the usual practice, but
we're still not out of the woods.
Stefan
next prev parent reply other threads:[~2021-10-04 19:18 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-04 10:51 More reliable byte compilation, take 45 Lars Ingebrigtsen
2021-10-04 15:36 ` Clément Pit-Claudel
2021-10-04 16:16 ` Lars Ingebrigtsen
2021-10-04 18:16 ` T.V Raman
2021-10-04 18:21 ` Eli Zaretskii
2021-10-04 19:18 ` Stefan Monnier [this message]
2021-10-04 19:51 ` Eli Zaretskii
2021-10-04 20:13 ` Stefan Monnier
2021-10-05 11:52 ` Eli Zaretskii
2021-10-05 13:27 ` Stefan Monnier
2021-10-05 14:06 ` Adam Porter
2021-10-05 15:41 ` Eli Zaretskii
2021-10-04 16:03 ` Steingold
2021-10-04 17:35 ` Lars Ingebrigtsen
2021-10-04 18:59 ` Steingold
2021-10-05 7:14 ` Lars Ingebrigtsen
2021-10-05 14:50 ` Steingold
2021-10-05 14:51 ` Steingold
2021-10-05 19:30 ` Stefan Monnier
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=jwvee90k3jm.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=cpitclaudel@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=raman@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).