unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Joel Reicher <joel.reicher@gmail.com>
To: Michael Heerdegen via "Emacs development discussions."
	<emacs-devel@gnu.org>
Cc: Michael Heerdegen <michael_heerdegen@web.de>
Subject: Re: Commands, term "closure" and online help
Date: Sun, 14 Jul 2024 18:48:37 +1000	[thread overview]
Message-ID: <86plrgcqai.fsf@gmail.com> (raw)
In-Reply-To: <87sewc8m9m.fsf@web.de> (Michael Heerdegen via's message of "Sun,  14 Jul 2024 09:29:09 +0200")

Michael Heerdegen via "Emacs development discussions." 
<emacs-devel@gnu.org> writes:

> Joel Reicher <joel.reicher@gmail.com> writes:
>
>>> Aren't "dynamically defined functions" bytecode functions when 
>>> running compiled code?  So this would not be a better term.
>>
>> Which bit of the documentation are you thinking of? I can't 
>> find that phrase with reference to bytecode.
>
> We are talking about the generated documentation in *Help*, 
> right?  I've just been using my own words.

In my question above I was referring to the Info documentation. I 
think it's helpful for the generated and static documentation to 
use consistent terminology.

> But: Note that the wording used in the generated help pages has 
> changed since the start of this thread: we are currently saying 
> (at least in master) "interactive interpreted-function" or 
> "interactive byte-code-function".  Can you live with that?

Oh I see! Just had a poke around in the repo; I didn't realise the 
elisp respresentations themselves had changed, and I thought this 
was still just a documentation matter.

I can't really offer an opinion until I understand the way the new 
types are being used, but I think the OP's main concern was that 
the term "closure" be avoided because it's a little opaque to some 
people unfamiliar with language implementation.

Thanks and regards,

       - Joel



  reply	other threads:[~2024-07-14  8:48 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-15 14:51 Commands, term "closure" and online help T.V Raman
2024-04-15 14:56 ` Eli Zaretskii
2024-04-15 15:09   ` Eli Zaretskii
2024-04-15 15:49     ` T.V Raman
2024-04-15 16:17       ` Eli Zaretskii
2024-07-14  5:06         ` Joel Reicher
2024-07-14  5:55           ` Michael Heerdegen via Emacs development discussions.
2024-07-14  6:20             ` Joel Reicher
2024-07-14  7:29               ` Michael Heerdegen via Emacs development discussions.
2024-07-14  8:48                 ` Joel Reicher [this message]
2024-07-14 10:36                   ` Michael Heerdegen

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=86plrgcqai.fsf@gmail.com \
    --to=joel.reicher@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=michael_heerdegen@web.de \
    /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).