GNU bug report logs - #40671
[DOC] modify literal objects

Previous Next

Full log

View this message in rfc822 format

From: Michael Heerdegen <michael_heerdegen <at> web.de>
To: Paul Eggert <eggert <at> cs.ucla.edu>
Cc: Mattias Engdegård <mattiase <at> acm.org>, ke.vigouroux <at> laposte.net, 40671 <at> debbugs.gnu.org, Richard Stallman <rms <at> gnu.org>, Dmitry Gutov <dgutov <at> yandex.ru>
Subject: bug#40671: [DOC] modify literal objects
Date: Sun, 17 May 2020 07:02:13 +0200

Paul Eggert <eggert <at> cs.ucla.edu> writes:

> ... and symbol-name is one of the cases.

I'm wondering about this one for a while, too.  Is it that the resulting
string is really like the "object is part of an evaluated program"
cases, or is it just that modifying it has an unwanted side effect
(changing the name of the symbol, and Emacs doesn't handle this
correctly).  I mean, you can modify a lot of objects in Emacs and that
will cause trouble.  We surely don't want to call them all constant or
not safely mutable or whatever.  How is the result of `symbol-name'
different from these other cases?  Is it only that the side effect/ mess
is not visible from Lisp?  Where do you draw the line?  Yes, the hidden
question is still what your definition of safely mutable is.

Thanks,

Michael.

Previous Next

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