From: Qiang Guo <qguo@ualberta.ca>
To: emacs-devel@gnu.org
Subject: Question about symbol_free_list
Date: Wed, 28 Dec 2011 17:14:16 -0700 [thread overview]
Message-ID: <m2boqstesn.fsf@ualberta.ca> (raw)
Hi,
When reading the gc_sweep(), I found symbol_free_list is set to NULL
everytime garbage collector kicks in. My understanding of this variable
is it holds up some free symbols and when Emacs is asked to allocate a
symbol object, it will first look into this list to see if there is one
available. It serves as kinda 'buffer'. My question is if
symbol_free_list is not empty when gc_sweep sets it to NULL, how about
the symbol objects in the list ? Where happened to them ?
Thanks
next reply other threads:[~2011-12-29 0:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-29 0:14 Qiang Guo [this message]
2011-12-30 11:41 ` Question about symbol_free_list Stefan Monnier
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=m2boqstesn.fsf@ualberta.ca \
--to=qguo@ualberta.ca \
--cc=emacs-devel@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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).