Estevo,

I think I completely lost you about what you are trying to achieve.

Please clarify, what particular use of wills do you find dangerous?

Is it that.. you find it tricky to get in place a particular sequence of C FFI structure release function invocation on their GC???

Something along the lines that if you have a C structure A that contains in it a reference to another C structure B, and you want Gambit's GC to automatically take care of this relationship in the sense that it will not release B before A??

Feel free to describe the totality of the problem you see as one or two sentences, so an elementary school kid would get it :)

Also feel free to describe some practical goal or usecase that cannot be achieved right now because of this

Mikael

2013/12/25 Estevo <euccastro@gmail.com>
I think how wills work is fine.  It's the particular usage of wills I described before that I find dangerous.  The problem with Gambit is that it doesn't offer a better way to do that.

As I said, I'm working on a patch that enables a better way.  As soon as I have a coherent proposal I'll ask the list for opinions/alternatives/suggestions.


On Wed, Dec 25, 2013 at 2:11 PM, Mikael <mikael.rcv@gmail.com> wrote:
Right. Just to clarify: Right now, do you see a problem about what's happening or do you consider all spinning fine?


2013/12/25 Estevo <euccastro@gmail.com>
> [...] But since none of these references is strong, the will that has it as testator
> will be made executable in the next garbage collection[1].

(Sorry, by "the next" garbage collection I don't mean a different one, just the same one I trigger by calling (##gc).)