From: Stefan Monnier <monnier@iro.umontreal.ca>
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: Mon, 13 Sep 2010 11:52:31 +0200 [thread overview]
Message-ID: <jwvocc2vv3x.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <AANLkTimF-5XPaZosB3B+Ns6VbOYmt-mn-bXwmPfiPTrC@mail.gmail.com> (MON KEY's message of "Sun, 12 Sep 2010 20:16:26 -0400")
> `#1=', and related reader syntax constructs aren't bad.
In source code, they are. In source code, you have other ways to
express sharing, such as `let', which are much preferred.
> Indeed, they are quite prevalent in byte-code files and the language
> would be hamstrung without them.
Which language? Note that AFAIC .el and .elc files use
2 different languages.
>> - unintern takes a symbol as argument, not a boolean, so it should
>> not be called with the return value of (fboundp ...)
> No, the argument to `unintern' can be a symbol or string.
Who cares, it's still not a boolean.
>> - calling unintern without an obarray arg is a bad idea.
> Yeah,
So: why do you do it?
>> Maybe we should make the second argument mandatory.
> That would be nice.
Indeed.
>> since `intern' only takes a string rather than a symbol.
> Yeah, but again there is the weird corner case of interning the 0
> length string.
What's weird about it?
Stefan
next prev parent reply other threads:[~2010-09-13 9:52 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
2010-09-12 14:00 ` Stefan Monnier
2010-09-13 0:16 ` MON KEY
2010-09-13 9:52 ` Stefan Monnier [this message]
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=jwvocc2vv3x.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--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).