From: Thien-Thi Nguyen <ttn@gnuvola.org>
To: Chengqi Song <songcq@gmail.com>
Cc: guile-user <guile-user@gnu.org>
Subject: Re: typo in guile doc?
Date: Sun, 27 Dec 2009 12:24:10 +0100 [thread overview]
Message-ID: <87skawhd7p.fsf@ambire.localdomain> (raw)
In-Reply-To: <20091226232250.GA4209@lars-x200s.resnet.ust.hk> (Chengqi Song's message of "Sun, 27 Dec 2009 07:22:50 +0800")
() Chengqi Song <songcq@gmail.com>
() Sun, 27 Dec 2009 07:22:50 +0800
"By calling this function, the garbage collector learns
about all references that your SMOB has to other SCM values."
what is "has to other SCM values"? is it a typo?
Perhaps that object contains (points to, references) other
sub-objects. The SMOB's mark function must call (back to) Guile's
mark function for those sub-objects. In this way the collector learns.
If the mark function fails to do that, the collector remains ignorant.
thi
next prev parent reply other threads:[~2009-12-27 11:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-26 23:22 typo in guile doc? Chengqi Song
2009-12-27 11:24 ` Thien-Thi Nguyen [this message]
2009-12-27 12:52 ` Neil Jerram
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/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87skawhd7p.fsf@ambire.localdomain \
--to=ttn@gnuvola.org \
--cc=guile-user@gnu.org \
--cc=songcq@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).