Re: RFC: glocal - automatically freeing memory when it goes out of scope

[Hub Figuière <hfiguiere teaser fr>]

On 22/11/11 01:48 AM, Emmanuele Bassi wrote:
> the obvious issue is: how does this interact with languages that do
> have a GC, and how does the API work to avoid making the life of
> developers for high-level languages apps and/or bindings a nightmare.
> if libraries start using this object for their internal allocations,
> for instance, or start relying on it when using their API.

I don't see it as being a problem with a GC. GObject does not know about
GC and language that have a GC built in already deal with that.

This GAutoreleasePool does not change the way object allocatios are
managed ; it just provide a mechanism to do the clean at a specific time.

For example, from the Gtkmm aspect (C++), I don't see an issue.


Hub