unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Emanuel Berg <incal@dataswamp.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Functions with multiple optional arguments
Date: Fri, 21 Oct 2022 05:29:50 +0200	[thread overview]
Message-ID: <87fsfhluq9.fsf@dataswamp.org> (raw)
In-Reply-To: Y1G2637preTzSv76@protected.localdomain

Jean Louis wrote:

>>>> CL has another way, more practical probably, to assign
>>>> default values to optional arguments and that can be used
>>>> in Elisp as well with `cl-defun' ...
>>>
>>> I keep anything like Common Lisp for Common Lisp and
>>> strive to keep Emacs Lisp functions without CL stuff for
>>> clarity of my mind.
>> 
>> If so, relax, as `cl-defun' is as much Elisp as `defun' ...
>> 
>> C-h f cl-defun RET
>> 
>> It's in cl-macs.el ...
>
> I do not load what is not needed.

Well, it's not about what's needed or not, there are obviously
several ways to do this as we have seen in this thread
already, and what `cl-defun' offers is another such solution,
one that some people would say is more clean than the
solutions with `or' and `setq'/`let' ...

> And Emacs Lisp is not Common Lisp, no need to conform to it.

Again, there is no need to do any of this but it remains that
`cl-defun' is an Elisp macro ...

-- 
underground experts united
https://dataswamp.org/~incal




  reply	other threads:[~2022-10-21  3:29 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-16 21:04 Functions with multiple optional arguments Heime via Users list for the GNU Emacs text editor
2022-10-17  1:48 ` Emanuel Berg
2022-10-17  4:05 ` Jean Louis
2022-10-17  4:18   ` Emanuel Berg
2022-10-17 21:12     ` Jean Louis
2022-10-17 21:36       ` Emanuel Berg
2022-10-20 21:00         ` Jean Louis
2022-10-21  3:29           ` Emanuel Berg [this message]
2022-10-23  4:47             ` Jean Louis
2022-10-24  3:07               ` Emanuel Berg
2022-10-25  5:25                 ` Emanuel Berg
2022-10-17  5:42   ` Heime
2022-10-17 16:24     ` Heime
2022-10-17 16:52       ` [External] : " Drew Adams
2022-10-17 17:28         ` Heime
2022-10-17 17:38           ` 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

  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=87fsfhluq9.fsf@dataswamp.org \
    --to=incal@dataswamp.org \
    --cc=help-gnu-emacs@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.
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).