Re: Getting ready to land native-compilation on master

[Eli Zaretskii <eliz@gnu.org>]

> From: Andy Moreton <andrewjmoreton@gmail.com>
> Date: Sat, 10 Apr 2021 01:07:40 +0100
> 
> >> <https://zenodo.org/record/3736363>
> >> <https://toobnix.org/videos/watch/1f997b3c-00dc-4f7d-b2ce-74538c194fa7>
> >> <https://toobnix.org/videos/watch/b985c5ca-fdcf-46ff-92d5-e68922fe4821>
> >> 
> >> ATM to go further I think the approach would be dumping passes and/or
> >> starting to look into the source code.  I tried my best to share with
> >> the community what I was working on and how but is not the easiest when
> >> the thing is being worked.
> >
> > I think it would be good to take the relevant parts of your blog and
> > rewrite them as introductory commentary to the code in comp.el, with
> > the goal of providing enough overview and background information to
> > let people discover the details by reading the code.
> 
> Perhaps some of this material could be added to the "GNU Emacs
> Internals" section of the elisp manual.

Some of it, probably.  But most of that stuff is inappropriate for the
manual.  We have in several files large commentaries that provide
overview of the design and implementation of various features.  For
example, the beginning of xdisp.c and coding.c, the overview of w32
subprocess support in w32proc.c, etc.  I was thinking about a similar
overview in comp.el.