From: ludo@gnu.org (Ludovic Courtès)
To: Mark H Weaver <mhw@netris.org>
Cc: Andy Wingo <wingo@pobox.com>, guile-devel@gnu.org
Subject: Re: Mark procedures and LilyPond
Date: Fri, 06 Nov 2015 14:50:00 +0100 [thread overview]
Message-ID: <87d1vnkzjr.fsf@gnu.org> (raw)
In-Reply-To: <87io5ftij0.fsf_-_@netris.org> (Mark H. Weaver's message of "Fri, 06 Nov 2015 07:32:51 -0500")
Mark H Weaver <mhw@netris.org> skribis:
> Unfortunately, I doubt this will be sufficient for LilyPond. The small
> example case in <http://bugs.gnu.org/19883>, which is apparently
> representative of how things are typically done in LilyPond, has
> structures like this:
>
> __________ __________
> Objects in | | | |
> GC-managed | SMOB 1 | | SMOB 2 |
> heap |__________| |__________|
> | ^ | ^
> .....................|...|.........................|...|..........
> __v___|___ _________ __v___|___
> Objects in | | | STL | | |
> normal heap |C++ object|--->|container|-->|C++ object|
> (not scanned |__________| |_________| |__________|
> by GC)
Thanks for the picture, that’s very helpful!
I still think we should be able to get rid of GC mark procedures in this
case, sidestepping the bug you describe.
This pattern is very common when writing bindings. I can’t imagine that
there's something insurmountable here. Am I missing something?
Ludo’.
next prev parent reply other threads:[~2015-11-06 13:50 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-04 10:10 Mark procedures Andy Wingo
2015-11-04 12:01 ` Stefan Israelsson Tampe
2015-11-04 17:01 ` Mark procedures, LilyPond, and backward compatibility Mark H Weaver
2015-11-05 10:16 ` Foreign object API Ludovic Courtès
2016-02-01 22:50 ` Foreign objects removed from ‘stable-2.0’ Ludovic Courtès
2015-11-05 14:46 ` Mark procedures, LilyPond, and backward compatibility Andy Wingo
2015-11-05 10:29 ` Mark procedures Ludovic Courtès
2015-11-05 13:11 ` Andy Wingo
2015-11-05 14:17 ` Ludovic Courtès
2015-11-06 12:32 ` Mark procedures and LilyPond Mark H Weaver
2015-11-06 13:50 ` Ludovic Courtès [this message]
2015-11-06 15:05 ` Stefan Monnier
2016-01-24 8:58 ` Hans Åberg
2016-06-20 10:34 ` Mark procedures Andy Wingo
2016-06-20 12:15 ` Ludovic Courtès
2021-05-18 15:46 ` Ephemerons, self-referentality in weak hashtables Christopher Lemmer Webber
2021-06-20 15:01 ` Maxime Devos
2021-06-21 17:15 ` Maxime Devos
2021-09-08 16:18 ` Christine Lemmer-Webber
2021-09-08 20:11 ` Maxime Devos
2021-09-08 20:50 ` Christine Lemmer-Webber
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=87d1vnkzjr.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guile-devel@gnu.org \
--cc=mhw@netris.org \
--cc=wingo@pobox.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).