From: Mike Gran <spk121@yahoo.com>
To: 20907@debbugs.gnu.org
Subject: bug#20907: [PATCH] Manual bug for scm_gc_protect_object
Date: Fri, 26 Jun 2015 23:00:32 +0000 (UTC) [thread overview]
Message-ID: <1019343405.630040.1435359632144.JavaMail.yahoo@mail.yahoo.com> (raw)
Manual claims C globals weren't scanned by GC in 1.8. The opposite
is true.
* doc/ref/api-memory.texi [scm_gc_protect_object]: modified
---
doc/ref/api-memory.texi | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/doc/ref/api-memory.texi b/doc/ref/api-memory.texi
index 0e37d16..3496cc5 100644
--- a/doc/ref/api-memory.texi
+++ b/doc/ref/api-memory.texi
@@ -42,7 +42,7 @@ as it was protected. It is an error to unprotect an object more times
than it has been protected. Returns the SCM object it was passed.
Note that storing @var{obj} in a C global variable has the same
-effect@footnote{In Guile up to version 1.8, C global variables were not
+effect@footnote{In Guile up to version 1.8, C global variables were
scanned by the garbage collector; hence, @code{scm_gc_protect_object}
was the only way in C to prevent a Scheme object from being freed.}.
@end deftypefn
--
2.1.0
next reply other threads:[~2015-06-26 23:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-26 23:00 Mike Gran [this message]
2015-09-02 1:59 ` bug#20907: [PATCH] Manual bug for scm_gc_protect_object Mark H Weaver
2015-09-02 12:08 ` Ludovic Courtès
2015-09-02 15:36 ` Mike Gran
2015-09-02 16:16 ` Mark H Weaver
2015-09-02 16:52 ` Mark H Weaver
2015-09-02 17:12 ` Mike Gran
2015-09-02 18:05 ` Mark H Weaver
2015-09-02 18:34 ` Mike Gran
2016-06-24 6:58 ` Andy Wingo
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=1019343405.630040.1435359632144.JavaMail.yahoo@mail.yahoo.com \
--to=spk121@yahoo.com \
--cc=20907@debbugs.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).