unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Alan Mackenzie <acm@muc.de>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
Subject: Re: How does one find out what file a library has been loaded from?
Date: Thu, 21 Jul 2022 18:24:17 +0000	[thread overview]
Message-ID: <YtmZ0XJCa7BDfS2W@ACM> (raw)
In-Reply-To: <jwvzgh2fjn2.fsf-monnier+emacs@gnu.org>

Hello, Stefan.

On Thu, Jul 21, 2022 at 13:52:43 -0400, Stefan Monnier wrote:
> > It's accurate, though.  The current text is not accurate.  The situation
> > it is describing is vague and confusing.

> > Would this strategy be an improvement: "This function returns a file
> > name.  When the file from which the function was loaded was a source
> > file or byte compiled file .......  When that file was a native compiled
> > file ......."?

> BTW, the design of the native code compiler is that it aims to be
> transparent, a bit like a JIT compiler would be transparent:

I think the word you should be using is not "transparent", but "opaque".

> whether the native code comes from a .eln file or was generated
> on-the-fly or combined from several .eln files (or any other option
> you can come up with) should ideally not matterd.

That is a gross departure from long valued Emacs philosophy - that there
should be nothing "transparent" (i.e. opaque) to the user, and that it's
not for us maintainers to predict what users want to do in their hacking
(and thus restrict Emacs to just doing those predicted things).

For crying out loud, you can even get the position of the gap in Emacs
Lisp.  That is surely a candidate for being "transparent" (i.e. opaque)
if ever there were one.

> (ELisp code shouldn't need to know and end-users shouldn't need to
> know either (barring bugs or curiosity of course))

For those reasons, amongs others, there shouldn't be these transparent (i.e.
opaque) things.

> Clearly we do want to make that info visible somehow (e.g. for debugging
> purposes, but also because we can never make something really
> transparent), but it's very different from `load-history` which keeps
> track of information that is relevant: whether /usr/share/.../org.el, or
> usr/share/.../org.elc, or ~/.emacs.d/elpa/.../org.el, or ... was loaded
> can result in different outcomes even if there's no bug anywhere.
> Those 4 files do not have the same semantics., e.g. because it's not the
> same version of Org, or because of the `eval-when-compile` in `org.el`.

I think we've violently in agreement, here.

>         Stefan

-- 
Alan Mackenzie (Nuremberg, Germany).



  reply	other threads:[~2022-07-21 18:24 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-19 10:52 How does one find out what file a library has been loaded from? Alan Mackenzie
2022-07-19 12:39 ` Eli Zaretskii
2022-07-19 15:01   ` Alan Mackenzie
2022-07-19 15:32     ` Andrea Corallo
2022-07-24 16:07       ` Eli Zaretskii
2022-07-24 17:46         ` Andrea Corallo
2022-07-31 12:52           ` Eli Zaretskii
2022-08-01  9:23             ` Andrea Corallo
2022-08-02  8:43               ` Andrea Corallo
2022-08-02 12:12                 ` Eli Zaretskii
2022-08-02 14:13                   ` Andrea Corallo
2022-08-03 14:19                     ` Eli Zaretskii
2022-08-01 19:31             ` Alan Mackenzie
2022-08-03 14:16               ` Eli Zaretskii
2022-07-19 15:50     ` Eli Zaretskii
2022-07-19 17:07       ` Alan Mackenzie
2022-07-19 19:13         ` Eli Zaretskii
2022-07-20 11:47           ` Alan Mackenzie
2022-07-20 15:31             ` Stefan Monnier
2022-07-20 20:34             ` Alan Mackenzie
2022-07-21  6:13               ` Eli Zaretskii
2022-07-21 17:37                 ` Alan Mackenzie
2022-07-21 17:52                   ` Stefan Monnier
2022-07-21 18:24                     ` Alan Mackenzie [this message]
2022-07-21 18:37                       ` Stefan Monnier
2022-07-21 21:03                         ` Alan Mackenzie
2022-07-21 23:15                           ` Stefan Monnier
2022-07-21 17:53                   ` Eli Zaretskii
2022-07-21 20:39                     ` Alan Mackenzie
2022-07-23 10:11                       ` Eli Zaretskii
2022-07-24 11:27                         ` Alan Mackenzie
2022-07-24 12:16                           ` Eli Zaretskii
2022-07-24 15:37                             ` Eli Zaretskii
2022-07-24 15:42                               ` Eli Zaretskii
2022-07-24 15:32                           ` Stefan Monnier
2022-07-24 15:49                             ` T.V Raman
2022-07-24 16:11                               ` Stefan Monnier
2022-07-24 18:21                                 ` T.V Raman
2022-07-24 18:50                                   ` Stefan Monnier
2022-07-24 16:19                               ` Eli Zaretskii
2022-07-19 16:27     ` Stefan Monnier
2022-07-20 18:36       ` Andrea Corallo
2022-07-21  7:20         ` 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=YtmZ0XJCa7BDfS2W@ACM \
    --to=acm@muc.de \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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).