unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Ken Raeburn <raeburn@raeburn.org>
To: emacs-devel@gnu.org
Subject: Re: Not using DOC for ELisp files
Date: Mon, 3 Jan 2022 08:48:03 -0500	[thread overview]
Message-ID: <30e03635-843d-f3be-7709-d4b633b2c90a@raeburn.org> (raw)
In-Reply-To: <jwv8rw5a4ru.fsf-monnier+emacs@gnu.org>

On 2021-12-27 20:48, Stefan Monnier wrote:
> The patch below removes from the DOC file the docstrings coming from
> ELisp files.
>
> In numbers (in my tests), this reduces the size of DOC from about 3.2MB
> to about 850kB, and increases the pdmp size by about 53kB or about 0.7%.
>
> The benefits aren't great, obviously, but it does remove some warts in
> the `lread.c` code (into which I bumped in the `scratch/fcr` branch,
> which is why this comes up now).
>
> I have a vague recollection that such a change was mentioned in some
> bugreport-discussion some months ago but I can't remember where.
>
> Comments?


I've only skimmed the actual code changes so far, but I think this is a 
good direction to go.

Stefan Kargas dug up an old bug report of mine, but I think I may also 
have mentioned something like this in our old discussion and 
experimentation of doing away with unexec in favor of a big .elc file, a 
few years back now(!), my idea at the time being to reduce the runtime 
startup work done in a build without unexec.

Another piece I recall looking at, which I don't remember if I brought 
up on the list at the time, was moving the C based doc strings into the 
generated .o files and the executable; in combination with removing the 
elisp doc strings, this would get rid of the DOC file altogether. I 
haven't had much time for Emacs hacking in quite a while, sadly, but if 
there's interest, I can try to find a little time to dig up those old 
changes on the C side and see how complete they were and if they can 
still be adapted in some form or other...

Ken




  parent reply	other threads:[~2022-01-03 13:48 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-28  1:48 Not using DOC for ELisp files Stefan Monnier
2021-12-28  2:25 ` Po Lu
2021-12-28  3:48   ` Stefan Kangas
2021-12-28  5:39     ` Po Lu
2021-12-28  4:11   ` LdBeth
2021-12-28  5:03     ` Stefan Monnier
2021-12-28  5:38     ` Po Lu
2021-12-28  9:52     ` Phil Sainty
2021-12-28 10:31       ` Po Lu
2021-12-28 12:47         ` Po Lu
2021-12-28  7:10   ` Lars Ingebrigtsen
2021-12-28  3:39 ` Stefan Kangas
2021-12-28  5:10   ` Stefan Monnier
2021-12-28  6:56 ` Lars Ingebrigtsen
2021-12-28 12:44 ` Eli Zaretskii
2021-12-28 17:14   ` Stefan Monnier
2021-12-28 18:17     ` Eli Zaretskii
2021-12-29  0:15       ` Stefan Monnier
2021-12-29 12:30         ` Johann Klähn
2021-12-29 23:08           ` Stefan Monnier
2021-12-29 12:52         ` Eli Zaretskii
2021-12-29 23:23           ` Stefan Monnier
2021-12-30  7:20             ` Eli Zaretskii
2021-12-31  4:19               ` Stefan Monnier
2021-12-31  8:57                 ` Eli Zaretskii
2021-12-31 16:16                   ` Stefan Monnier
2021-12-31 18:45                     ` Eli Zaretskii
2022-01-03 13:48 ` Ken Raeburn [this message]
2022-01-03 14:30   ` Eli Zaretskii
2022-01-07 22:59     ` Ken Raeburn
2022-01-08  7:08       ` Eli Zaretskii

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=30e03635-843d-f3be-7709-d4b633b2c90a@raeburn.org \
    --to=raeburn@raeburn.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).