From: "Basil L. Contovounesios" <contovob@tcd.ie>
To: Richard Stallman <rms@gnu.org>
Cc: Stefan Monnier <monnier@iro.umontreal.ca>, emacs-devel@gnu.org
Subject: cl-defun vs defun (was: Should diff.elisp.xfuncname match cl-lib macros?)
Date: Sat, 16 Mar 2019 15:33:10 +0000 [thread overview]
Message-ID: <877ecyg7gp.fsf_-_@tcd.ie> (raw)
In-Reply-To: <E1h50QY-0005zJ-Js@fencepost.gnu.org> (Richard Stallman's message of "Fri, 15 Mar 2019 23:56:06 -0400")
Richard Stallman <rms@gnu.org> writes:
> What is the feature for which people typically use cl-defun?
> Maybe we should make it a standard, builtin feature of defun.
As described under "(cl) Argument Lists", cl-defun extends defun to
support CL argument lists (with default values for optional arguments,
keyword arguments, etc.) and enclose the function body in an implicit
block. In my limited experience, the former is by far the more
frequently used feature.
I, for one, would welcome support for CL argument lists in vanilla
defun. Has this been discussed before?
--
Basil
next prev parent reply other threads:[~2019-03-16 15:33 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-15 16:42 Should diff.elisp.xfuncname match cl-lib macros? Basil L. Contovounesios
2019-03-15 18:21 ` Stefan Monnier
2019-03-16 3:56 ` Richard Stallman
2019-03-16 15:33 ` Basil L. Contovounesios [this message]
2019-03-17 2:41 ` cl-defun vs defun (was: Should diff.elisp.xfuncname match cl-lib macros?) Richard Stallman
2019-03-16 15:30 ` Should diff.elisp.xfuncname match cl-lib macros? Basil L. Contovounesios
2019-03-16 16:42 ` Eli Zaretskii
2019-03-16 17:12 ` Stefan Monnier
2019-03-16 17:33 ` Eli Zaretskii
2019-03-16 18:14 ` Stefan Monnier
2019-03-16 21:55 ` Basil L. Contovounesios
2019-03-16 21:54 ` Basil L. Contovounesios
2019-03-17 3:37 ` Eli Zaretskii
2019-03-17 8:14 ` Andreas Schwab
2019-03-17 15:22 ` Basil L. Contovounesios
2019-03-17 21:33 ` Juri Linkov
2019-03-18 1:14 ` Stefan Monnier
2019-03-18 21:02 ` Juri Linkov
2019-05-13 1:40 ` Basil L. Contovounesios
2019-05-20 15:03 ` Basil L. Contovounesios
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=877ecyg7gp.fsf_-_@tcd.ie \
--to=contovob@tcd.ie \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=rms@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 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).