From: Drew Adams <drew.adams@oracle.com>
To: 17872@debbugs.gnu.org
Subject: bug#17872: 24.4.50; "primitive" in (elisp) `Advising Functions' and similar nodes
Date: Sun, 29 Jun 2014 07:35:37 -0700 (PDT) [thread overview]
Message-ID: <d0044a1c-bf28-45e7-98c5-6f1869b213b8@default> (raw)
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.
Usually, a function is implemented as a primitive because it is a
fundamental part of Lisp (e.g., `car'), or because it provides a
low-level interface to operating system services, or because it
needs to run fast. Unlike functions defined in Lisp, primitives
can be modified or added only by changing the C sources and
recompiling Emacs. See *note Writing Emacs Primitives::.
The things being referred to in node `Advising Functions' and other
nodes (its children, at least) as "primitives", are NOT primitives.
They are either macros (e.g. `add-function') or ordinary Lisp functions
(e.g. `advice-add'). This confuses rather than helps Emacs users.
In GNU Emacs 24.4.50.1 (i686-pc-mingw32)
of 2014-06-17 on ODIEONE
Bzr revision: 117359 monnier@iro.umontreal.ca-20140617193358-2t1nl1te9gc2mqrx
Windowing system distributor `Microsoft Corp.', version 6.1.7601
Configured using:
`configure --prefix=/c/Devel/emacs/snapshot/trunk
--enable-checking=yes,glyphs 'CFLAGS=-O0 -g3'
LDFLAGS=-Lc:/Devel/emacs/lib 'CPPFLAGS=-DGC_MCHECK=1
-Ic:/Devel/emacs/include''
next reply other threads:[~2014-06-29 14:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-29 14:35 Drew Adams [this message]
2019-08-04 11:56 ` bug#17872: 24.4.50; "primitive" in (elisp) `Advising Functions' and similar nodes Lars Ingebrigtsen
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=d0044a1c-bf28-45e7-98c5-6f1869b213b8@default \
--to=drew.adams@oracle.com \
--cc=17872@debbugs.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.
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.