From: Michael Heerdegen <michael_heerdegen@web.de>
To: help-gnu-emacs@gnu.org
Subject: Re: obarray
Date: Sun, 15 Dec 2013 05:47:47 +0100 [thread overview]
Message-ID: <87mwk2d8jw.fsf@web.de> (raw)
In-Reply-To: barmar-DC4996.23173714122013@news.eternal-september.org
Barry Margolin <barmar@alum.mit.edu> writes:
> Values are unrelated to whether a symbol is in the obarray. An
> uninterned symbol can have a value.
>
> (setq uninterned-symbol (make-symbol "foo"))
> (setf (symbol-value uninterned-symbol) 'bar)
The last line easier without cl'ish setf:
(set uninterned-symbol 'bar)
> This symbol "foo" won't be in the obarray, but it still has a value.
And to answer the next question: "What are uninterned symbols good for"?
They are useful especially when writing macros, as a way to avoid
collisions with already used symbols. But that doesn't matter here.
All that need to know is that obarray is a thing that holds all
essential symbols (variables), and that it is a valid COLLECTION
argument for `completing-read'.
Regards,
Michael.
next prev parent reply other threads:[~2013-12-15 4:47 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-15 0:54 obarray Emanuel Berg
2013-12-15 1:14 ` obarray Juanma Barranquero
[not found] ` <mailman.9268.1387070101.10748.help-gnu-emacs@gnu.org>
2013-12-15 1:37 ` obarray Emanuel Berg
2013-12-15 1:56 ` obarray Michael Heerdegen
2013-12-15 1:59 ` obarray Juanma Barranquero
[not found] ` <mailman.9271.1387072648.10748.help-gnu-emacs@gnu.org>
2013-12-15 4:17 ` obarray Emanuel Berg
2013-12-15 4:17 ` obarray Barry Margolin
2013-12-15 4:47 ` Michael Heerdegen [this message]
2013-12-15 4:55 ` obarray Emanuel Berg
2013-12-15 6:04 ` obarray Barry Margolin
2013-12-15 17:43 ` obarray Emanuel Berg
2013-12-16 17:44 ` obarray Barry Margolin
2013-12-17 1:47 ` obarray Michael Heerdegen
[not found] ` <mailman.9442.1387244871.10748.help-gnu-emacs@gnu.org>
2013-12-17 2:11 ` obarray Emanuel Berg
2013-12-17 2:55 ` obarray Michael Heerdegen
[not found] ` <mailman.9452.1387248989.10748.help-gnu-emacs@gnu.org>
2013-12-17 3:01 ` obarray Emanuel Berg
2013-12-17 17:32 ` obarray Barry Margolin
2013-12-17 17:42 ` obarray Emanuel Berg
[not found] ` <mailman.9279.1387082898.10748.help-gnu-emacs@gnu.org>
2013-12-15 5:11 ` obarray Emanuel Berg
2013-12-15 5:36 ` obarray Emanuel Berg
2013-12-15 6:17 ` obarray Michael Heerdegen
[not found] ` <mailman.9283.1387088419.10748.help-gnu-emacs@gnu.org>
2013-12-15 17:51 ` obarray Emanuel Berg
2013-12-15 6:15 ` obarray Michael Heerdegen
[not found] ` <mailman.9282.1387088166.10748.help-gnu-emacs@gnu.org>
2013-12-15 17:47 ` obarray Emanuel Berg
2013-12-15 5:58 ` obarray Barry Margolin
2013-12-15 17:28 ` obarray Emanuel Berg
2013-12-17 14:38 ` obarray jack-mac
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=87mwk2d8jw.fsf@web.de \
--to=michael_heerdegen@web.de \
--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).