From: MON KEY <monkey@sandpframing.com>
To: Chong Yidong <cyd@stupidchicken.com>
Cc: 7146@debbugs.gnu.org
Subject: bug#7146: (make-symbol "") issues
Date: Sun, 3 Oct 2010 19:48:51 -0400 [thread overview]
Message-ID: <AANLkTikaEUboXp1-xGjZL1d=F8e52KO07+4Mpb+UPYOw@mail.gmail.com> (raw)
In-Reply-To: <87aamvw1e2.fsf@stupidchicken.com>
On Sun, Oct 3, 2010 at 2:56 PM, Chong Yidong <cyd@stupidchicken.com> wrote:
> MON KEY <monkey@sandpframing.com> writes:
>
>> So, IIUC is the rationale for doing this is that there aren't really
>> any particularly good reasons to intern the empty string given that
>> the reader is incapable of reading it correctly?
>
> The only reason is that it can lead to a crash.
So the potential for a crashed Emacs is rationale enough, whereas
potential for an inexplicably hung and thoroughly corrupted Emacs is
just grist for the mill?
> There are plenty of
> reasons to shoot yourself in the foot in Lisp in you're determined to do
And a good deal of these apply equally even for the undetermined and
un-intentioned, not to mention the ill-intentioned.
> so; it's not profitable to address them unless a real world problem
> surfaces.
>
OK.
--
/s_P\
prev parent reply other threads:[~2010-10-03 23:48 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-02 4:19 bug#7146: (make-symbol "") issues Frank
2010-10-03 0:44 ` Frank
2010-10-03 1:32 ` Chong Yidong
2010-10-03 3:44 ` Frank
2010-10-03 4:05 ` Chong Yidong
2010-10-03 4:14 ` Frank
2010-10-03 4:36 ` Juanma Barranquero
2010-10-03 10:28 ` Johan Bockgård
2010-10-03 14:55 ` Chong Yidong
2010-10-03 23:12 ` Stefan Monnier
2011-07-14 14:25 ` Lars Magne Ingebrigtsen
2011-07-14 16:24 ` Andreas Schwab
2011-07-17 3:16 ` Stefan Monnier
2011-07-17 8:15 ` Andreas Schwab
2011-07-18 15:30 ` Stefan Monnier
2011-07-21 19:25 ` Chong Yidong
2011-07-28 21:11 ` Andreas Schwab
2011-07-17 21:41 ` David De La Harpe Golden
2010-10-03 18:45 ` MON KEY
2010-10-03 18:56 ` Chong Yidong
2010-10-03 23:48 ` MON KEY [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='AANLkTikaEUboXp1-xGjZL1d=F8e52KO07+4Mpb+UPYOw@mail.gmail.com' \
--to=monkey@sandpframing.com \
--cc=7146@debbugs.gnu.org \
--cc=cyd@stupidchicken.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.