From: divoplade <d@divoplade.fr>
To: Chris Vine <vine35792468@gmail.com>, guile-user@gnu.org
Subject: Re: Calling back scheme from C
Date: Tue, 22 Sep 2020 12:36:15 +0200 [thread overview]
Message-ID: <e997993cfbdb882f140a8bd00e18025f743fbb34.camel@divoplade.fr> (raw)
In-Reply-To: <20200922105026.5783d9ab0dd3641391cdd8c9@gmail.com>
Hello,
Le mardi 22 septembre 2020 à 10:50 +0100, Chris Vine a écrit :
> This may not be your issue. I offer it as something I had to deal
> with
> in code of my own to prevent incorrect collection for closures of
> callbacks executed by a C event loop.
It does not seem to fix it on my side. Could you share your callback
closure example?
divoplade
next prev parent reply other threads:[~2020-09-22 10:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-22 6:25 Calling back scheme from C divoplade
2020-09-22 9:50 ` Chris Vine
2020-09-22 10:36 ` divoplade [this message]
2020-09-22 14:47 ` Chris Vine
2020-09-22 15:48 ` divoplade
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=e997993cfbdb882f140a8bd00e18025f743fbb34.camel@divoplade.fr \
--to=d@divoplade.fr \
--cc=guile-user@gnu.org \
--cc=vine35792468@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).