Re: [Evolution-hackers] Introspection enablement for libecal - huge changes needed?

[Milan Crha <mcrha redhat com>]

On Tue, 2014-05-20 at 11:07 +0200, Patrick Ohly wrote:
> Aren't you going to run into the same problem with a GObject-based
> proxies for these libical objects? The proxies are reference-counted,
> the libical objects are not, so they may go away before their proxies
> do. This would leave the proxy with a dangling pointer or (if it somehow
> tracks the lifetime of the owner of the object) in a state where it is
> unusable.

        Hi,
my idea was that an ICalComponent will hold its own icalcomponent and
any getter of an internal libical structure will reference also the
ICalComponent, which will make sure that the parent object will not die
before all the subobjects will be freed. These refs would be done across
whole new API.

Once also evolution will use these ICalComponent-s all what works will
keep working.
        Bye,
        Milan