unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>,
	"help-gnu-emacs@gnu.org" <help-gnu-emacs@gnu.org>
Subject: RE: FW: [External] : Re: Native compilation by default?: Was [Re: stats say SBCL is 78 875 % faster than natively compiled Elisp
Date: Sun, 26 Feb 2023 17:12:56 +0000	[thread overview]
Message-ID: <SJ0PR10MB548865EE51C5A5C71351C68BF3AE9@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <83h6v8ie1r.fsf@gnu.org>

> > > If you want to load "the most efficient option available", then just
> > > don't specify any extension, and Emacs will load the `.el`, `.elc`,
> > > or `.eln` file according to what it finds.
> >
> > Again, please point that out explicitly (though this
> > one will be familiar to longtime Emacs users, as the
> > same logic has long existed for *.el and *.elc).
> 
> The logic has existed, but none of the doc strings of 'load',
> 'load-file', and 'load-library' says anything about it.  Neither does
> the manual.  What is different here?

I won't argue about it.  I can say that when
I read the doc of those functions (long ago)
I never had any doubt that Emacs "would load
the .el or .elc according to what it finds."

I wasn't aware that the discussion here is
only about doc strings.  Whether, and if so
then which, doc strings should mention this
is an open question.  I was talking about
the doc in general, not just doc strings.

But you also say "neither does the manual".  

To me, the Emacs manual is (and has long been)
very clear about this.  Node `Lisp Libraries'
goes into it, pointing out explicitly which
files (*.el or *.elc) get loaded (priority)
by `load', `load-library', and `load-file'.

And that Emacs-manual text points to the more
detailed text in the Elisp manual, node `How
Programs Do Loading'.

So it's not clear to me what you mean by
"neither does the manual".

If that (or similar) doc in the manuals has
been updated to say what's involved wrt *.el,
*.elc, and *.eln, then great.

In that case, perhaps the user confusion shown
in this thread could have been dispelled just
by pointing to the (updated) manuals?

And perhaps some of the doc about compilation
has been updated similarly?

(It also wouldn't hurt for the doc strings of
the various functions (e.g. `load') to link
to a manual.)

Bottom line: Maybe a little more clarification
would help.  Or else maybe it would have been
enough to point to the doc sections that you
think already clear up the confusion exhibited.
You decide.



  reply	other threads:[~2023-02-26 17:12 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-14  7:56 stats say SBCL is 78 875 % faster than natively compiled Elisp Emanuel Berg
2023-02-15  5:04 ` Chen Zhaoyang
2023-02-15 11:37   ` Emanuel Berg
2023-02-15  6:59 ` Jean Louis
2023-02-16  6:04   ` Emanuel Berg
2023-02-17 17:38     ` Jean Louis
2023-02-18 19:54       ` Emanuel Berg
2023-02-18 20:15         ` Emanuel Berg
2023-02-18 20:39           ` Eli Zaretskii
2023-02-18 20:47             ` Emanuel Berg
2023-02-19  6:35               ` Eli Zaretskii
2023-02-21  7:04                 ` Native compilation by default?: Was [Re: " Madhu
2023-02-21 12:37                   ` Eli Zaretskii
2023-02-21 16:35                     ` Emanuel Berg
2023-02-21 19:57                       ` Emanuel Berg
2023-02-21 22:21                       ` Native compilation by default? (was: Re: stats say SBCL is 78 875 % faster than natively compiled Elisp) Emanuel Berg
2023-02-21 23:54                         ` Emanuel Berg
     [not found]                           ` <87h6vetquk.fsf@dataswamp.org>
2023-02-22  1:47                             ` Emanuel Berg
2023-02-23 10:46                         ` Emanuel Berg
2023-02-23 20:18                           ` Jean Louis
2023-02-26  1:05                             ` Emanuel Berg
2023-02-22 12:32                       ` Native compilation by default?: Was [Re: stats say SBCL is 78 875 % faster than natively compiled Elisp Eli Zaretskii
2023-02-26  3:08                     ` Madhu
2023-02-26  4:32                       ` Stefan Monnier via Users list for the GNU Emacs text editor
2023-02-26  5:15                         ` Emanuel Berg
2023-02-26  6:27                         ` Eli Zaretskii
2023-02-26  7:10                         ` Emanuel Berg
2023-02-26 16:14                         ` FW: [External] : " Drew Adams
2023-02-26 16:31                           ` Eli Zaretskii
2023-02-26 17:12                             ` Drew Adams [this message]
2023-02-26 17:31                               ` Eli Zaretskii
2023-02-26 18:29                                 ` Drew Adams
2023-02-26 19:04                                   ` Eli Zaretskii
2023-02-26 20:05                                     ` Emanuel Berg
2023-02-27  8:42                         ` Madhu
2023-03-03 14:55                           ` Stefan Monnier via Users list for the GNU Emacs text editor
2023-02-26  6:25                       ` Eli Zaretskii
2023-02-26 16:10                         ` [External] : " Drew Adams
2023-02-19  5:58         ` Jean Louis
2023-02-15 12:36 ` full native compile (was: Re: stats say SBCL is 78 875 % faster than natively compiled Elisp) Emanuel Berg
2023-02-15 14:05   ` 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=SJ0PR10MB548865EE51C5A5C71351C68BF3AE9@SJ0PR10MB5488.namprd10.prod.outlook.com \
    --to=drew.adams@oracle.com \
    --cc=eliz@gnu.org \
    --cc=help-gnu-emacs@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.
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).