From: Emanuel Berg <embe8573@student.uu.se>
To: help-gnu-emacs@gnu.org
Subject: Re: obarray
Date: Sun, 15 Dec 2013 02:37:19 +0100 [thread overview]
Message-ID: <87bo0irj13.fsf@nl106-137-194.student.uu.se> (raw)
In-Reply-To: mailman.9268.1387070101.10748.help-gnu-emacs@gnu.org
Juanma Barranquero <lekktu@gmail.com> writes:
> I think it's pretty clear: is a symbol table for
> (most) symbols. It is implemented as a vector, of
> prime length because of the way the hashing is done,
> and it does not make sense to examine it from Lisp
> *as a vector*, because its elements are not symbols,
> but have a more complex structure (basically, they
> implemented some kind of hash table). So the way to
> process all elements of that symbol table is to use
> mapatoms; looping over the vector won't give the
> symbols stored in the table.
Well, that description was a lot better.
So it is a hash table of symbols: variables, constants,
:keywords, functions, ...?
And when you do `defvar', is the symbol name inserted
into this data structure based on some property -
perhaps the name itself, or type (if a "symbol" isn't
atomic)?
Is the value inserted as well or do they use some sort
of pointer scheme?
--
Emanuel Berg, programmer-for-rent. CV, projects, etc at uXu
underground experts united: http://user.it.uu.se/~embe8573
next prev parent reply other threads:[~2013-12-15 1:37 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 ` Emanuel Berg [this message]
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 ` obarray Michael Heerdegen
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87bo0irj13.fsf@nl106-137-194.student.uu.se \
--to=embe8573@student.uu.se \
--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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.