From: Michael Heerdegen <michael_heerdegen@web.de>
To: help-gnu-emacs@gnu.org
Subject: Re: Calling a function with undefined symbol
Date: Wed, 02 Nov 2022 17:40:37 +0100 [thread overview]
Message-ID: <877d0d8g3e.fsf@web.de> (raw)
In-Reply-To: lzzgd9l9gr.fsf@3c22fb11fdab.ant.amazon.com
Sam Steingold <sds@gnu.org> writes:
> > '''''''''''''''''''''''''''''''''...
>
> i.e.,
>
> (defconst x #1=(quote #1#))
>
> right?
Yep. Or #1='#1#. What strange things we can have in Elisp!
> > i.e. a value that is a quoted thing where the thing is the same value
> > again (such a value exists in Elisp!) - what would evaluating
> >
> > (eq 'x x)
> > (equal 'x x)
>
> nil: you are comparing a symbol 'x' with a circular list
> (quote (quote ...))
>
> what you probably meant was [...]
No, I really meant what I wrote. It was intended as that simple
question.
Symbols are values in Elisp, expressions can eval to symbols. That's
what Stefan was talking about.
The exercise's goal was to recognize that `'x` evals to a symbol, which
is something entirely different than adding another quote to that
strange `'''....` value (which is not a symbol in any case). If you
have understood that the first value is a symbol, it's easy to give the
intended answers: two times "no".
Michael.
next prev parent reply other threads:[~2022-11-02 16:40 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-31 8:15 Calling a function with undefined symbol Heime
2022-10-31 8:32 ` Jean Abou Samra
2022-10-31 8:42 ` tomas
2022-10-31 8:57 ` Heime
2022-10-31 9:07 ` tomas
2022-10-31 9:24 ` Jean Abou Samra
2022-10-31 9:43 ` Heime
2022-10-31 9:58 ` Jean Abou Samra
2022-10-31 10:57 ` Heime
2022-10-31 17:00 ` [External] : " Drew Adams
2022-10-31 17:10 ` Emanuel Berg
2022-11-01 4:11 ` Drew Adams
2022-11-01 5:24 ` tomas
2022-11-01 15:58 ` Drew Adams
2022-11-01 16:13 ` tomas
2022-11-01 19:22 ` Drew Adams
2022-10-31 12:29 ` Stefan Monnier via Users list for the GNU Emacs text editor
2022-10-31 15:37 ` Emanuel Berg
2022-11-02 12:14 ` Michael Heerdegen
2022-11-02 14:25 ` Sam Steingold
2022-11-02 16:40 ` Michael Heerdegen [this message]
2022-11-02 17:28 ` Emanuel Berg
2022-11-02 23:04 ` Emanuel Berg
2022-11-03 11:09 ` Michael Heerdegen
2022-11-03 12:15 ` Emanuel Berg
2022-11-04 12:16 ` Michael Heerdegen
2022-11-05 14:32 ` Emanuel Berg
2022-11-05 23:22 ` Michael Heerdegen
2022-11-06 20:17 ` Emanuel Berg
2022-11-07 16:03 ` Michael Heerdegen
2022-11-07 16:50 ` [External] : " Drew Adams
2022-11-07 16:52 ` Emanuel Berg
2022-11-08 15:52 ` Michael Heerdegen
2022-11-08 19:15 ` tomas
2022-11-08 19:57 ` Michael Heerdegen
2022-11-08 20:47 ` tomas
2022-11-08 21:35 ` Sam Steingold
2022-11-08 23:53 ` Michael Heerdegen
2022-11-09 15:32 ` Sam Steingold
2022-11-09 15:59 ` Michael Heerdegen
2022-11-16 19:07 ` Emanuel Berg
2022-11-16 21:40 ` [External] : " Drew Adams
2022-11-16 21:55 ` Emanuel Berg
2022-11-04 14:33 ` Michael Heerdegen
2022-11-05 12:57 ` Emanuel Berg
2022-10-31 11:34 ` Emanuel Berg
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=877d0d8g3e.fsf@web.de \
--to=michael_heerdegen@web.de \
--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).