From: Drew Adams <drew.adams@oracle.com>
To: arthur miller <arthur.miller@live.com>,
tomas@tuxteam.de, emacs-devel@gnu.org
Subject: RE: Docs for &optional and &rest arguments together
Date: Thu, 31 Dec 2020 10:19:32 -0800 (PST) [thread overview]
Message-ID: <f3114415-7c6e-4554-bc9d-2b60371c622b@default> (raw)
In-Reply-To: <AM0PR06MB6577B7DEE2DE5A00D2E3166E96D60@AM0PR06MB6577.eurprd06.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 1846 bytes --]
> I have glanced through though, maybe I am missing it.
Don't just glance. Give it the attention that it and your understanding both deserve. If that CL doc didn't help you then I really suggest you sit down, take it slowly, and reread carefully.
Both the Elisp doc and the CL doc about this are clear and complete, I think. I suggest with respect that you're maybe just not paying enough attention.
Don't be in a hurry. The info is there; just give it a chance - and another read.
The CL link is not documentation, it is an essay, entire novel :-). But interestingly, that do not touch on that case either . I have glanced through though, maybe I am missing it.
> > I don't read it says both c and d are required
> > when &rest is also used.
>
> You just have to squint the other way .-)
> They are not "required". They are provided -- in the call. It's just
> that c is served first, d next, and all the rest (if any) goes to e:
If someone finds the Elisp doc about lambda lists,
I recommend consulting the Common Lisp doc (CLTL2)
about it. Common Lisp lambda lists allow more stuff
(&keys, &aux etc.), but for the things that Elisp
has (&optional, &rest) the behavior is the same.
The language in CLTL2 is quite precise. It too
merits being read carefully, but I think it spells
things out quite clearly.
This is the section about lambda lists, which covers
&optional and &rest:
HYPERLINK "https://urldefense.com/v3/__https:/www.cs.cmu.edu/Groups/AI/html/cltl/clm/node64.html*SECTION00922000000000000000__;Iw!!GqivPVa7Brio!PxyUBvVt3a4Eze6ZtyLlEC6A236XgfttZKnn-7gkT1H6p1FBymyit-C_eQf2-wZH$"https://www.cs.cmu.edu/Groups/AI/html/cltl/clm/node64.html#SECTION00922000000000000000
With that, plus the Elisp doc, plus this thread,
I think things will become more clear. HTH.
[-- Attachment #2: Type: text/html, Size: 5286 bytes --]
next prev parent reply other threads:[~2020-12-31 18:19 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-29 13:26 Docs for &optional and &rest arguments together Arthur Miller
2020-12-29 15:10 ` Adam Porter
2020-12-29 17:06 ` arthur miller
2021-01-01 14:33 ` Arthur Miller
2020-12-30 3:12 ` Lars Ingebrigtsen
2020-12-30 12:19 ` Arthur Miller
2020-12-30 12:54 ` Yuri Khan
2020-12-31 4:43 ` Lars Ingebrigtsen
2020-12-31 7:55 ` arthur miller
2020-12-31 11:26 ` tomas
2020-12-31 16:45 ` Drew Adams
2020-12-31 17:04 ` Drew Adams
2020-12-31 17:28 ` arthur miller
2020-12-31 18:19 ` Drew Adams [this message]
2020-12-31 20:01 ` arthur miller
2020-12-31 20:27 ` Drew Adams
2020-12-31 17:08 ` arthur miller
2020-12-31 17:30 ` Daniel Brooks
2020-12-31 19:53 ` arthur miller
2020-12-31 19:40 ` tomas
-- strict thread matches above, loose matches on Subject: below --
2020-12-31 20:04 arthur miller
2020-12-31 20:35 ` tomas
2020-12-31 23:18 ` arthur miller
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=f3114415-7c6e-4554-bc9d-2b60371c622b@default \
--to=drew.adams@oracle.com \
--cc=arthur.miller@live.com \
--cc=emacs-devel@gnu.org \
--cc=tomas@tuxteam.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 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).