I may not be understanding you correctly, but an interface is a gobject
mechanic. This is intended as a quick and simple mechanism for non-gobject
library bindings.
Free shouldn't actually be needed, since that's handled by the specified
unref_function, but something as simple as:
[Compact]
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.
Sam
Sam
-Original Message-
From: Arc Riley arcri...@ubuntu.com
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 s...@liddicott.com wrote:
Yes, but it is much cleaner and nicer to
Dear list,
I was trying to catch up with recent vala master branch, but I get this
error:
valacodevisitor.vala:308.34-308.37: error: The type name `Loop' could not be
found
public virtual void visit_loop (Loop stmt) {
