From: Stefan Monnier via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Stefan Kangas <stefankangas@gmail.com>
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: Sun, 05 Nov 2023 18:24:13 -0500 [thread overview]
Message-ID: <jwvlebb6b3d.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <CADwFkmnGvEDDbQLJ8iDF-0uwgCrzAvieJHtUXGYPRVi39b-yLA@mail.gmail.com> (Stefan Kangas's message of "Sun, 5 Nov 2023 06:23:59 -0800")
>> In Elisp manual, "17.4 Dynamic Loading of Individual Functions"
>> describes `byte-compile-dynamic' variable.
>>
>> However, according to the docstring, this variable is no longer useful
>>
>> byte-compile-dynamic is a variable defined in bytecomp.el.
>>
>> This variable is obsolete since 27.1; not worthwhile any more.
>>
>> Value
>> nil
>>
>> It looks like the corresponding section of the manual is now obsolete
>> and should probably be removed.
>
> 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?
Stefan
next prev parent reply other threads:[~2023-11-05 23:24 UTC|newest]
Thread overview: 5+ 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 [this message]
2023-11-06 0:21 ` Stefan Kangas
2024-01-11 21:52 ` 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
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=jwvlebb6b3d.fsf-monnier+emacs@gnu.org \
--to=bug-gnu-emacs@gnu.org \
--cc=66946@debbugs.gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=stefankangas@gmail.com \
--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 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).