From: Emanuel Berg <incal@dataswamp.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Calling a function with undefined symbol
Date: Sat, 05 Nov 2022 15:32:02 +0100 [thread overview]
Message-ID: <87sfixfp5p.fsf@dataswamp.org> (raw)
In-Reply-To: 87tu3egbj2.fsf@web.de
Michael Heerdegen wrote:
>> (setq print-circle t)
>>
>> (setq x #1=(quote #1#))
>>
>> (eq 'x x) ; nil
>> (equal 'x x) ; nil
>>
>> ?
>
> I don't see any place in your code where a quote-quine is
> quoted. You correctly assign a quote-quine to a variable.
> But then you only quote the symbol, not the value, and
> compare the quote-quine with the symbol you had bound it to.
>
> IOW: It's a trap!
>
> So how could a correct `equal'ity test of a quote-quine and
> that quote-quine quoted be achieved?
Beats me!
Because quoting it will just add another level/layer of the
same, and in the same way, to something that is
already infinite.
(setq print-circle t)
(setq x #1=(quote #1#))
(equal x #1=(quote #1#)) ; t
(equal x (quote #1=(quote #1#))) ; t
(equal x (quote (quote #1=(quote #1#)))) ; and so on
So I give my tongue to the cat then?
--
underground experts united
https://dataswamp.org/~incal
next prev parent reply other threads:[~2022-11-05 14:32 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
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 [this message]
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=87sfixfp5p.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).