From: David Kastrup <dak@gnu.org>
To: emacs-devel@gnu.org
Subject: Re: t and nil in pure memory?
Date: Sun, 22 Nov 2009 09:14:16 +0100 [thread overview]
Message-ID: <87ljhz6ko7.fsf@lola.goethe.zz> (raw)
In-Reply-To: 87einrxdf6.fsf@gnu.org
Sam Steingold <sds@gnu.org> writes:
>> * Chong Yidong <plq@fghcvqpuvpxra.pbz> [2009-11-20 00:47:18 -0500]:
>>
>> FWIW, in CLISP and CMUCL (unintern nil) and (unintern t) are no-ops
>> returning nil. Presumably the other CL implementations do likewise.
>
> This is not true about CLISP (and presumably other CL implementations).
>
> [2]> (unintern cl:t :cl)
>
> ** - Continuable Error
>
> i.e., it IS possible to remove the T symbol (with all the trouble this
> entails).
>
> As a CLISP maintainer, I don't think T & NIL are special enough.
I am quite appalled to what my reductio ad absurdum argument has lead.
The original topic was in the thread title, and I pointed out that
obarray chains ending in pure memory do not need further modification.
Then it was pointed out that unintern may change the game in that
respect, and I replied that I did not think this much of a concern for t
and nil.
From then things went downhill.
--
David Kastrup
next prev parent reply other threads:[~2009-11-22 8:14 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-11 20:23 t and nil in pure memory? Dan Nicolaescu
2009-11-11 22:56 ` Stefan Monnier
2009-11-12 8:21 ` Tobias C. Rittweiler
2009-11-12 15:22 ` Stefan Monnier
2009-11-13 5:24 ` Dan Nicolaescu
2009-11-13 14:39 ` Stefan Monnier
2009-11-14 11:23 ` Richard Stallman
2009-11-15 20:25 ` David Kastrup
2009-11-16 1:26 ` Stefan Monnier
2009-11-16 8:24 ` David Kastrup
2009-11-17 7:57 ` Richard Stallman
2009-11-17 13:16 ` Stefan Monnier
2009-11-17 13:55 ` David Kastrup
2009-11-18 12:11 ` Richard Stallman
2009-11-18 15:52 ` Stefan Monnier
2009-11-18 17:53 ` Daniel Colascione
2009-11-18 18:19 ` Stefan Monnier
2009-11-19 16:23 ` Richard Stallman
2009-11-19 20:08 ` Stefan Monnier
2009-11-20 4:12 ` Richard Stallman
2009-11-20 5:47 ` Chong Yidong
2009-11-22 6:48 ` Sam Steingold
2009-11-22 8:14 ` David Kastrup [this message]
2009-11-19 21:05 ` Dan Nicolaescu
2009-11-15 21:08 ` Dan Nicolaescu
2009-11-16 1:34 ` Stefan Monnier
2009-11-18 18:53 ` Ken Raeburn
2009-11-18 19:03 ` Daniel Colascione
2009-11-18 19:18 ` Tom Tromey
2009-11-18 19:13 ` Tom Tromey
2009-11-23 3:05 ` Ken Raeburn
2009-11-23 5:31 ` Stephen J. Turnbull
2009-11-24 16:03 ` Ken Raeburn
2009-11-24 16:28 ` Stefan Monnier
2009-11-19 1:01 ` Stefan Monnier
2009-11-12 4:06 ` Eli Zaretskii
2009-11-13 4:55 ` Richard Stallman
2009-11-13 8:37 ` Eli Zaretskii
2009-11-14 11:23 ` Richard Stallman
2009-11-14 11:46 ` Eli Zaretskii
2009-11-15 22:38 ` Richard Stallman
2009-11-13 4:56 ` Richard Stallman
-- strict thread matches above, loose matches on Subject: below --
2009-11-20 7:28 A. Soare
2009-11-20 8:09 ` David Kastrup
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=87ljhz6ko7.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 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).