GNU bug report logs - #15405
24.3; #[] freezes emacs

Previous Next

Package: emacs;

Reported by: Leo Liu <sdl.web <at> gmail.com>

Date: Wed, 18 Sep 2013 01:52:02 UTC

Severity: normal

Merged with 16512

Found in version 24.3

Fixed in version 24.4

Done: Barry OReilly <gundaetiapo <at> gmail.com>

Bug is archived. No further changes may be made.

Full log

Message #86 received at 15405 <at> debbugs.gnu.org (full text, mbox):

From: Stefan Monnier <monnier <at> IRO.UMontreal.CA>
To: Dmitry Antipov <dmantipov <at> yandex.ru>
Cc: Eli Zaretskii <eliz <at> gnu.org>, Barry OReilly <gundaetiapo <at> gmail.com>,
 15405 <at> debbugs.gnu.org, Leo Liu <sdl.web <at> gmail.com>, stephen.berman <at> gmx.net
Subject: Re: bug#15405: 24.3; #[] freezes emacs
Date: Wed, 25 Sep 2013 13:35:36 -0400

> Of course, this is technically possible. <IMHO> But I don't see
> a reason for this at all. Unlike 0 (zero) for arithmetic, "" for
> string operations, () (or nil) for lists, etc., #[] (empty bytecode
> string) makes no sense at all.  Again, if bytecomp never produces such
> an objects and they're never used somewhere else, it should be treated
> as "impossible" object and error should be signaled once such an
> object is found. </IMHO>.

Indeed, we could also disallow them.  If that's simpler, I'm fine with
this solution.


        Stefan
This bug report was last modified 11 years and 121 days ago.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.