From: Andy Wingo <wingo@pobox.com>
To: MON KEY <monkey@sandpframing.com>
Cc: emacs-devel@gnu.org
Subject: Re: Save `nil' from the mutant void, preserve the truth of falsehood, prevent the falsehood of truth
Date: Sun, 12 Sep 2010 13:04:14 +0200 [thread overview]
Message-ID: <m3r5gzdxzl.fsf@unquote.localdomain> (raw)
In-Reply-To: <AANLkTi=knVAJcjBeaPMZDPAChNAXXYhguT7dTwntVa9a@mail.gmail.com> (MON KEY's message of "Sat, 11 Sep 2010 19:33:07 -0400")
Hello,
On Sun 12 Sep 2010 01:33, MON KEY <monkey@sandpframing.com> writes:
> So, how do the Schemes handle this? Is it possible to define/set away
> #f?
In Scheme, #f and '() are not identifiers (symbols), so it is impossible
to set! them.
> This said, Guile 1.9.10 doesn't seem to mind me let-binding `nil':
>
> scheme@(guile-user)> (let ((nil 'bubba)) nil)
> ;=> bubba
Nil does not exist in Scheme, so it is not bound. However Guile does
provide a separate nil value, which may be read as "#nil" -- again, not
an identifier.
(There is also a %nil symbol bound to #nil in the default environment
with deprecated symbols enabled, but that is a relic.)
There are still some nil-is-a-symbol-in-elisp issues to work out in
Guile. In fact there are still a number of symbols-are-fat-in-elisp,
symbols-are-just-immutable-strings-in-scheme issues to work out...
I don't think my comments have much bearing on your original comment,
though :)
Andy
--
http://wingolog.org/
next prev parent reply other threads:[~2010-09-12 11:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-11 23:33 Save `nil' from the mutant void, preserve the truth of falsehood, prevent the falsehood of truth MON KEY
2010-09-12 0:16 ` Lars Magne Ingebrigtsen
2010-09-12 11:04 ` Andy Wingo [this message]
2010-09-12 14:00 ` Stefan Monnier
2010-09-13 0:16 ` MON KEY
2010-09-13 9:52 ` Stefan Monnier
2010-09-14 5:11 ` MON KEY
2010-09-14 11:14 ` Stefan Monnier
[not found] ` <51808.130.55.118.19.1284998205.squirrel@webmail.lanl.gov>
2010-09-22 1:37 ` MON KEY
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=m3r5gzdxzl.fsf@unquote.localdomain \
--to=wingo@pobox.com \
--cc=emacs-devel@gnu.org \
--cc=monkey@sandpframing.com \
/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).