[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#17872: 24.4.50; "primitive" in (elisp) `Advising Functions' and simi
From: |
Lars Ingebrigtsen |
Subject: |
bug#17872: 24.4.50; "primitive" in (elisp) `Advising Functions' and similar nodes |
Date: |
Sun, 04 Aug 2019 13:56:45 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux) |
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
- bug#17872: 24.4.50; "primitive" in (elisp) `Advising Functions' and similar nodes,
Lars Ingebrigtsen <=