From: Adam Porter <adam@alphapapa.net>
To: emacs-devel@gnu.org
Subject: Re: More reliable byte compilation, take 45
Date: Tue, 05 Oct 2021 09:06:01 -0500 [thread overview]
Message-ID: <87sfxfva5y.fsf@alphapapa.net> (raw)
In-Reply-To: jwvsfxf7gon.fsf-monnier+emacs@gnu.org
Stefan Monnier <monnier@iro.umontreal.ca> writes:
>> And that's all? Then why not fix that problem right away, it sounds
>> like something that should be easy to fix. (Though I'm not sure I
>> understand why "some other ELisp file was not loaded beforehand" -- is
>> that a case of a missing 'require' or 'eval-when-compile' or somesuch?)
>
> Often the problem is with packages where you basically have to load
> all/most the files before you can call any of its functions (because of
> mutual dependencies between the files) and where the authors never
> compile the code or only ever compile the code from a running session
> where the files have already been loaded.
>
> Fixing those can be a pain in the rear, not only because of the amount
> of code you need to move between files to disentangle the dependencies,
> but also because it requires educating the authors about it (they may
> not see the value/importance).
>
>> Ah, so the problem is with buggy *.el files, and only with them?
>
> Yes, tho the authors may disagree about the characterization of "buggy",
> in the sense that it works reliably *if* you compile the code by running
> their Makefile.
FWIW, I mostly solved this kind of problem in my own packages by using
makem.sh to lint compilation, which now compiles each file separately:
https://github.com/alphapapa/makem.sh
It detects project Elisp files automatically, so it doesn't require
writing a Makefile or other configuration, which makes it easier for
package authors to use.
next prev parent reply other threads:[~2021-10-05 14:06 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 [this message]
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=87sfxfva5y.fsf@alphapapa.net \
--to=adam@alphapapa.net \
--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).