From: David Kastrup <dak@gnu.org>
To: emacs-devel@gnu.org
Subject: Re: symbol equality --cl-rest-- help-function-arglist member vs member* and also equal, eql, and eq
Date: Wed, 23 Dec 2009 09:59:44 +0100 [thread overview]
Message-ID: <87ljgujcan.fsf@lola.goethe.zz> (raw)
In-Reply-To: d2afcfda0912221557iddb71e1tf52bb7f9e933d516@mail.gmail.com
MON KEY <monkey@sandpframing.com> writes:
> Stephen
>> Apparently --cl-rest-- is an uninterned symbol. This is done so that
>> the symbol cannot shadow an definition in code outside the cl-arglist
>> processing module.
>
> Miles
>> It looks like `--cl-rest--' is an uninterned symbol.
>> This is a good thing.
>
> Ok, thanks to you both for explaining.
>
> However, I'm not able to make that to jibe... still missing something
> I'm sure.
>
> I understand why there needs to be a reserved 'anonymous' symbol for
> the --rest-of-cl-- e.g. --cl-rest-- and that this symbol should remain
> uninterned but what I am missing on is why --cl-keys-- is converted to
> `cl-keys' whereas --cl-rest-- can't/isn't in the `cl-do-arglist'
> function? For example,
>
> In the following both `body' and `--cl-rest--' show as being interned whereas
> the `*-wombats' aren't:
>
> (intern-soft "body") ;=> t
> (intern-soft "--cl-rest--") ;=> t
> (intern-soft "scary-flying-wombats") ;=> nil
For what it's worth, cl-macroexpand-all uses the _symbols_ body and
--cl-rest--. Note that even if you let-bind or lambda-bind a literal
symbol in Elisp, it gets interned permanently by the Lisp reader.
That does not mean that you can't use make-symbol to generate
_different_ symbols with the _same_ symbol-name.
--
David Kastrup
next prev parent reply other threads:[~2009-12-23 8:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-22 1:16 symbol equality --cl-rest-- help-function-arglist member vs member* and also equal, eql, and eq MON KEY
2009-12-22 2:22 ` Miles Bader
2009-12-22 23:57 ` MON KEY
2009-12-23 8:59 ` David Kastrup [this message]
2009-12-22 2:32 ` Stephen J. Turnbull
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=87ljgujcan.fsf@lola.goethe.zz \
--to=dak@gnu.org \
--cc=emacs-devel@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 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.