From: Lars Ingebrigtsen <larsi@gnus.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: 17872@debbugs.gnu.org
Subject: bug#17872: 24.4.50; "primitive" in (elisp) `Advising Functions' and similar nodes
Date: Sun, 04 Aug 2019 13:56:45 +0200 [thread overview]
Message-ID: <878ss9b0ua.fsf@mouse.gnus.org> (raw)
In-Reply-To: <d0044a1c-bf28-45e7-98c5-6f1869b213b8@default> (Drew Adams's message of "Sun, 29 Jun 2014 07:35:37 -0700 (PDT)")
Drew Adams <drew.adams@oracle.com> writes:
> Please use some other term than "primitive" for what is intended here.
> The term "primitive" already has a different meaning in Emacs, which you
> can find by using `i primitive RET' in the Elisp manual:
>
> "primitive"
> A function which is callable from Lisp but is actually written in
> C. Primitives are also called "built-in functions", or "subrs".
> Examples include functions like `car' and `append'. In addition,
> all special forms (see below) are also considered primitives.
Are you referring to (for instance) this text?
---
Emacs's advice system provides two sets of primitives for that: the core set,
for function values held in variables and object fields (with the corresponding
primitives being @code{add-function} and @code{remove-function}) and another
set layered on top of it for named functions (with the main primitives being
@code{advice-add} and @code{advice-remove}).
---
Nowhere in this node (and the subsequent nodes) is the word "primitive"
used in reference to a function or the like, but in the phrase "Core
Advising Primitives" or similar. I don't think there's much scope for
confusion with the other use of the word, so I'm closing this bug report.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2019-08-04 11:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-29 14:35 bug#17872: 24.4.50; "primitive" in (elisp) `Advising Functions' and similar nodes Drew Adams
2019-08-04 11:56 ` Lars Ingebrigtsen [this message]
2019-08-05 0:56 ` Drew Adams
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=878ss9b0ua.fsf@mouse.gnus.org \
--to=larsi@gnus.org \
--cc=17872@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
/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.