unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Christopher Dimech <dimech@gmx.com>
To: Drew Adams <drew.adams@oracle.com>
Cc: Help Gnu Emacs <help-gnu-emacs@gnu.org>
Subject: Re: RE: Symbol Properties having global context
Date: Sun, 6 Dec 2020 21:25:10 +0100	[thread overview]
Message-ID: <trinity-093046f0-8dfe-4618-92f9-ecb8942f867c-1607286310524@3c-app-mailcom-bs11> (raw)
In-Reply-To: <67c408b0-4ae4-41be-a766-413f336f10e8@default>

I got to "9.2 Defining Symbols".  It only mentions that defvar and defconst
define a symbol as a global variable.

Could something be written and your comments were very enlightening.

> Sent: Sunday, December 06, 2020 at 9:13 PM
> From: "Drew Adams" <drew.adams@oracle.com>
> To: "Christopher Dimech" <dimech@gmx.com>, "Help Gnu Emacs" <help-gnu-emacs@gnu.org>
> Subject: RE: Symbol Properties having global context
>
> > Am reading the section "9.4 Symbol Properties".  The section that not
> > say that
> > symbol properties such as "value" have a global context.
>
> It is symbols themselves that are global objects.
> It follows that their property values are also.
>
> (Of course, a Lisp value can be shared.)
>
> Symbols are stored in obarrays.  By default, they
> are stored in the obarray that is the value of
> global variable `obarray'.
>
> So you can have two symbols with the same name
> (the name is just one of a symbols properties,
> its `symbol-name'), but which have different
> values for other properties, such as
> `symbol-value'.
>
> E.g., you can have two symbols `foo', in two
> different obarrays, with two different values
> when used as a variable.  (They can also have
> different `symbol-function' value, etc.)
>



  reply	other threads:[~2020-12-06 20:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-06 20:09 Symbol Properties having global context Christopher Dimech
2020-12-06 20:13 ` Drew Adams
2020-12-06 20:25   ` Christopher Dimech [this message]
2020-12-06 23:01     ` Drew Adams
2020-12-06 23:20       ` Christopher Dimech
2020-12-06 23:52     ` Michael Heerdegen

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=trinity-093046f0-8dfe-4618-92f9-ecb8942f867c-1607286310524@3c-app-mailcom-bs11 \
    --to=dimech@gmx.com \
    --cc=drew.adams@oracle.com \
    --cc=help-gnu-emacs@gnu.org \
    /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).