From: Marius Vollmer <mvo@zagadka.ping.de>
Cc: guile-user@gnu.org
Subject: Re: Passing lambda bindings to C for use as callback
Date: 26 Nov 2002 13:10:48 +0100 [thread overview]
Message-ID: <873cpojzuf.fsf@zagadka.ping.de> (raw)
In-Reply-To: <20021126032223.GB24594@buici.com>
Marc Singer <elf@buici.com> writes:
> I found the answer by browsing an old CVS archive of the guile code.
> Turned out to be quite easy.
You can also pass the SCM objects that you want to protect globally to
the function scm_gc_protect_object. Guile will then keep the data
structure for you. You can unprotect such an object with
scm_gc_unprotect_object. For objects that you wont ever unprotect you
can also use scm_permanent_object.
--
GPG: D5D4E405 - 2F9B BCCC 8527 692A 04E3 331E FAF8 226A D5D4 E405
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-user
next prev parent reply other threads:[~2002-11-26 12:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-26 2:45 Passing lambda bindings to C for use as callback Marc Singer
2002-11-26 3:22 ` Marc Singer
2002-11-26 12:10 ` Marius Vollmer [this message]
2002-11-26 20:55 ` Marc Singer
2002-11-26 21:56 ` Thien-Thi Nguyen
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=873cpojzuf.fsf@zagadka.ping.de \
--to=mvo@zagadka.ping.de \
--cc=guile-user@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).