all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Kangas <stefankangas@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 66946@debbugs.gnu.org, Ihor Radchenko <yantar92@posteo.net>
Subject: bug#66946: 30.0.50; Elisp manual section 17.4 describes an obsolete variable
Date: Thu, 11 Jan 2024 13:52:45 -0800	[thread overview]
Message-ID: <CADwFkmkM+V4YL7ZxGurx4=tMV4Z2Aqszgpoh9spU9X9UM_W5cg@mail.gmail.com> (raw)
In-Reply-To: <CADwFkmnda48wwrsESj17fnicqjJ2P+AC3rw2JwdEJXNdmS6_2g@mail.gmail.com>

Stefan Kangas <stefankangas@gmail.com> writes:

> Stefan Monnier <monnier@iro.umontreal.ca> writes:
>
>>> The manual says:
>>>
>>>        _Experience shows that using dynamic function loading provides
>>>     benefits that are hardly measurable, so this feature is deprecated
>>>     since Emacs 27.1._
>>>
>>> Stefan M, any comments here?
>>
>> Nothing specific, no.
>>
>>> Is it time to actually mark this stuff obsolete?
>>
>> Hmm... isn't it marked obsolete already?
>> Or did you mean to ask if it's time to throw away the corresponding code?
>
> You're right.  Not sure how I missed that...

Taking another look at this.

Why not throw away the code if it's hardly measurable?  We could make it
a no-op in Emacs 30.1, and then just remove it from the manual.  It's
already been obsolete for three major versions by then.





  reply	other threads:[~2024-01-11 21:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-05  9:37 bug#66946: 30.0.50; Elisp manual section 17.4 describes an obsolete variable Ihor Radchenko
2023-11-05 14:23 ` Stefan Kangas
2023-11-05 23:24   ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-11-06  0:21     ` Stefan Kangas
2024-01-11 21:52       ` Stefan Kangas [this message]
2024-08-12  6:18         ` Ihor Radchenko
2024-08-17  9:39           ` Eli Zaretskii
2024-08-17 12:53             ` Stefan Kangas

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CADwFkmkM+V4YL7ZxGurx4=tMV4Z2Aqszgpoh9spU9X9UM_W5cg@mail.gmail.com' \
    --to=stefankangas@gmail.com \
    --cc=66946@debbugs.gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=yantar92@posteo.net \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.