unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 17872@debbugs.gnu.org
Subject: bug#17872: 24.4.50; "primitive" in (elisp) `Advising Functions' and similar nodes
Date: Sun, 4 Aug 2019 17:56:16 -0700 (PDT)	[thread overview]
Message-ID: <61729aef-9138-4324-8b26-e42f6bd15f84@default> (raw)
In-Reply-To: <878ss9b0ua.fsf@mouse.gnus.org>

> > 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}).

Yes, and as the bug title says, "and similar nodes".

> Nowhere in this node (and the subsequent nodes) is the word "primitive"
> used in reference to a function or the like, 
                       ^^^^^^^^^^^^^^^^^^^^^^

Uh, I beg to differ.  All of the "primitives" in the
text you just quoted are functions.  And that text
explicitly refers to them as functions.

They are _functions_, and they are not coded in C.

> 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,

The undefined term "core" here presumably means
that these are the basic, or fundamental functions
used for advice.  Though undefined here, "core" is
OK.  What's not OK (it's misleading) is "primitive".

"Core Advising Functions" or "Basic Advising
Functions" would be clearer, and would not invite
confusion with Emacs primitives, which are callable
from Lisp but written in C.

Either that or perhaps you would like to rewrite
the longstanding text that defines "primitive" as
a function or special form written in C.

> so I'm closing this bug report.

Unfortunate.





      reply	other threads:[~2019-08-05  0: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
2019-08-05  0:56   ` Drew Adams [this message]

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=61729aef-9138-4324-8b26-e42f6bd15f84@default \
    --to=drew.adams@oracle.com \
    --cc=17872@debbugs.gnu.org \
    --cc=larsi@gnus.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 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).