From: Steingold <sds@gnu.org>
To: emacs-devel@gnu.org
Subject: Re: More reliable byte compilation, take 45
Date: Mon, 04 Oct 2021 12:03:34 -0400 [thread overview]
Message-ID: <lzczokhj55.fsf@3c22fb11fdab.ant.amazon.com> (raw)
In-Reply-To: 87sfxhm5aw.fsf@gnus.org
> * Lars Ingebrigtsen <ynefv@tahf.bet> [2021-10-04 12:51:19 +0200]:
>
> A defensive solution would be to recompile all libraries that require a
> library, building a dependency tree from require/autoloads/etc, but the
> problem is then that if you edit anything in subr.el, then you have to
> recompile all the .el files, basically. So it's not practical.
Nevertheless, this is TRT (and your solution is far too complicated, IMO).
Another solution was adopted by CLISP.
(https://clisp.sourceforge.io/impnotes/require.html#lib-files)
Briefly, compilation of `foo.el` should produce 2 files:
1. `foo.elc`, as now - this is the code whose loading is functionally
equivalent to loading `foo.el`
2. `foo.ell` (lib) - this contains only the compile-time dependencies
(i.e., compiled `defvar`, `defconst`, `defmacro`, and `defsubst`
definitions and function declarations)
When the byte compiler sees `(require 'foo)`, it will check that `foo.ell`
has changed since last loaded and will reload it automatically.
--
Sam Steingold (http://sds.podval.org/) on darwin Ns 10.3.1894
http://childpsy.net http://calmchildstories.com http://steingoldpsychology.com
https://jihadwatch.org https://honestreporting.com https://www.memritv.org
A good programmer: language change is easy, editor change is ... huh?!
next prev parent reply other threads:[~2021-10-04 16:03 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
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 [this message]
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=lzczokhj55.fsf@3c22fb11fdab.ant.amazon.com \
--to=sds@gnu.org \
--cc=emacs-devel@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.
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).