[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: GNU Guile 2.1.7 released (beta)

From: Mike Gran
Subject: Re: GNU Guile 2.1.7 released (beta)
Date: Mon, 27 Feb 2017 19:32:54 +0000 (UTC)

On Sunday, February 26, 2017 9:58 AM, Andy Wingo <address@hidden> wrote:
On Fri 24 Feb 2017 18:46, Arne Babenhauserheide <address@hidden> writes:

>> The main strategical question I see for that is: Does anything make it
>> harder to complete or improve the lilypond transition to Guile 2?
>> Is there something which would need to be done before 2.2 which could
>> make it easier for lilypond developers?

>I don't know of any concrete points here.  2.2 is not dissimilar to 2.0.
>If you someone like to try to determine exactly what specific bits of
>Guile 2.2 impact Lilypond (and indeed any big application using the C
>interface), that would be welcome :)  I guess I'd start with NEWS to see
>what's up.

As far as I ever understood it, the Lilypond SCM problem went
something like the following. Is this something that the new
foreign objects can be adapted to handle?

A C++ STL container holds a set of STL-allocated (non-GC allocated)

Those STL-allocated structs are also used as the payloads of
SCM foreign objects.

STL destruction can free those objects.  That free
should not allow SCM foreign objects that continue to exist but
contain junk payloads.

Also should SCM GC free the SCM foreign objects, this GC
should not cause the non-GC-allocated payload to be freed.

But I only ever had a distant view of the Lilypond problems,
so this summary might be invalid.

-Mike Gran

reply via email to

[Prev in Thread] Current Thread [Next in Thread]