unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Dmitry Gutov <dgutov@yandex.ru>,
	Marcin Borkowski <mbork@mbork.pl>,
	Philipp <p.stephani2@gmail.com>
Cc: Help Gnu Emacs mailing list <help-gnu-emacs@gnu.org>
Subject: RE: [External] : Re: Which Elisp types are mutable?
Date: Sun, 6 Jun 2021 01:57:15 +0000	[thread overview]
Message-ID: <SA2PR10MB4474E0E050C37529AA838647F3399@SA2PR10MB4474.namprd10.prod.outlook.com> (raw)
In-Reply-To: <82d0fa43-f0e1-f141-0433-526a5a9e717b@yandex.ru>

> > Lisp symbols are a kind of object.  They have
> > attributes, including name, value (as a variable),
> > function definition, and an unlimited slew of
> > other attributes: their `symbol-properties'.
> 
> A symbol does not contain its properties. They're
> stored in some alist externally.

You're missing the point, it seems.  The distinction
is conceptual, not implementation.  Contain / have /
point to ... distinctions don't matter here.  And
their possible implementations matter even less.

By your criterion a cons cell doesn't contain its
cdr either - or its car.  A symbol is a thing that
has properties / attributes, whatever you want to
call them.  How it has them / where they're stored
is a completely different matter (and irrelevant here).

"Parts" of both a cons and a symbol are changeable.
They're both mutable, and that's the case using just
Lisp.  ("Parts", not "the parts".  Not all parts of
a symbol are changeable - e.g., the name isn't.)

  reply	other threads:[~2021-06-06  1:57 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-03  4:03 Which Elisp types are mutable? Marcin Borkowski
2021-06-03 12:11 ` Philipp
2021-06-05 11:22   ` Marcin Borkowski
2021-06-05 12:58     ` Philipp
2021-06-05 14:25       ` Stefan Monnier via Users list for the GNU Emacs text editor
2021-07-05 18:40         ` Philipp
2021-07-05 20:19           ` Stefan Monnier
2021-07-05 20:44             ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-07-05 20:58               ` Stefan Monnier via Users list for the GNU Emacs text editor
2021-07-05 21:03                 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-06-05 19:19       ` Marcin Borkowski
2021-06-05 20:17         ` [External] : " Drew Adams
2021-06-05 20:36           ` Dmitry Gutov
2021-06-06  1:57             ` Drew Adams [this message]
2021-07-05 18:41         ` Philipp
2021-07-05 18:48           ` Eli Zaretskii
2021-07-05 18:55             ` tomas
2021-07-05 19:26               ` [External] : " Drew Adams
2021-07-05 19:40                 ` tomas
2021-07-05 20:03                   ` Drew Adams
2021-07-05 20:12                     ` tomas
2021-07-05 20:39                       ` Drew Adams
2021-07-05 20:58                         ` Emanuel Berg via Users list for the GNU Emacs text editor

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=SA2PR10MB4474E0E050C37529AA838647F3399@SA2PR10MB4474.namprd10.prod.outlook.com \
    --to=drew.adams@oracle.com \
    --cc=dgutov@yandex.ru \
    --cc=help-gnu-emacs@gnu.org \
    --cc=mbork@mbork.pl \
    --cc=p.stephani2@gmail.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.
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).