Re: More reliable byte compilation, take 45

[Steingold <sds@gnu.org>]

> * Lars Ingebrigtsen <ynefv@tahf.bet> [2021-10-05 09:14:30 +0200]:
>
> Steingold <sds@gnu.org> writes:
>
>> See if subr.ell has changed (the compiler should not change subr.ell
>> unless necessary, including the timestamp).
>
> Right, because the subr.ell only contains macros (and the like).  So
> the suggestion here is basically the same as mine, only with a lot
> more files spread around.

here is your suggestion:

> go through all the .el files and just look for "^\(defmacro ([^
> \t\n]+)" (and defsubst and cl-defstruct and probably a couple of other
> things, but not a whole lot more), and then do a sha256 of the region
> from the start of the match and until the next "^(".  It would maintain
> a database of these macro names/hashes.  If a macro changes its hash, it
> would then just grep through all the .el files for the macro name, and
> delete the .elc files where it fines matches.

I think the extra "compiled header" file is _way_ simpler and more
transparent solution.


-- 
Sam Steingold (http://sds.podval.org/) on darwin Ns 10.3.1894
http://childpsy.net http://calmchildstories.com http://steingoldpsychology.com
https://ij.org/ https://ffii.org https://memri.org https://jihadwatch.org
Illiterate?  Write today, for free help!