From: Drew Adams <drew.adams@oracle.com>
To: Michael Heerdegen <michael_heerdegen@web.de>,
Marcin Borkowski <mbork@mbork.pl>
Cc: Help Gnu Emacs mailing list <help-gnu-emacs@gnu.org>
Subject: RE: (interactive) call or form?
Date: Sun, 8 Apr 2018 06:56:53 -0700 (PDT) [thread overview]
Message-ID: <8efe7db8-b86e-48f0-9ade-bac28d931ec4@default> (raw)
In-Reply-To: <87h8omyrfk.fsf@web.de>
> > So, is it better to call it a "form" or a "call"?
>
> The manual very often calls it a "form", so it's probably ok to use this
> term.
>
> Personally I would prefer something else ("spec" maybe), to accentuate
> that it's rather something like a declaration: it's semantics imply more
> than the effect of calling it.
Yes. It is a special form that is used as a spec or
declaration of how the args are created/provided to
the function body.
That said, the code used as the arg to `interactive',
apart from the literal-string case, is not declarative
at all.
next prev parent reply other threads:[~2018-04-08 13:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-08 3:52 (interactive) call or form? Marcin Borkowski
2018-04-08 9:32 ` Michael Heerdegen
2018-04-08 13:56 ` Drew Adams [this message]
[not found] ` <mailman.11853.1523179956.27995.help-gnu-emacs@gnu.org>
2018-04-08 14:52 ` Emanuel Berg
2018-04-08 15:55 ` Michael Heerdegen
[not found] ` <mailman.11888.1523202939.27995.help-gnu-emacs@gnu.org>
2018-04-08 16:38 ` Emanuel Berg
2018-04-09 14:39 ` Michael Heerdegen
2018-04-09 19:48 ` Marcin Borkowski
[not found] ` <mailman.11931.1523284766.27995.help-gnu-emacs@gnu.org>
2018-04-09 18:46 ` Emanuel Berg
[not found] <mailman.11840.1523159602.27995.help-gnu-emacs@gnu.org>
2018-04-08 4:32 ` Emanuel Berg
2018-04-09 19:54 ` Marcin Borkowski
[not found] ` <mailman.11946.1523303724.27995.help-gnu-emacs@gnu.org>
2018-04-09 20:58 ` Emanuel Berg
2018-04-10 4:29 ` Marcin Borkowski
[not found] ` <mailman.11960.1523334628.27995.help-gnu-emacs@gnu.org>
2018-04-10 18:32 ` Emanuel Berg
2018-04-13 14:40 ` Marcin Borkowski
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=8efe7db8-b86e-48f0-9ade-bac28d931ec4@default \
--to=drew.adams@oracle.com \
--cc=help-gnu-emacs@gnu.org \
--cc=mbork@mbork.pl \
--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 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.