Re: [Vala] malloc/free CCode attributes



While don't you write an example of what your proposal would look like to the list?  I honestly don't understand how your proposed solution would work for non-gobject bindings.


On Wed, Jun 24, 2009 at 12:38 PM, Sam Liddicott <sam liddicott com> wrote:
Yes, but it is much cleaner and nicer to express it as an interface than a bunch of ccode attributes.

And not all structs of the same type are allocated by the same subsystem or want freeing with the same free function.



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