Re: [Vala] C Integration, it's cool



isn't that a source of memory leak?


In the example provided by Rodrigo, where a C external function is called
directly from Vala code as such, (i.e. without ensuring that the (memory
allocated to the) string returned by the external function is automatically
managed by the glib Object model) will said string (char *) be managed
automatically (reference counted and eventually disposed of when no longer
needed) by Vala or will it result in a dangling pointer (hence producing a
memory leak) ?


Serge.


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