Awesome! That was really a missing part of the docs. Thanks for your work,
you have written so much and so good.
A couple of things:
The copy_function shouldn't be of any uses for classes (compact and not),
if I'm not wrong.
Vala does support multidimensional arrays very well: int[,] foo = new
On 29 September 2013 01:45, Luca Bruno lethalma...@gmail.com wrote:
Awesome! That was really a missing part of the docs. Thanks for your work,
you have written so much and so good.
Thanks. I'm happy to contribute.
A couple of things:
The copy_function shouldn't be of any uses for classes
Clarified. → Vala does not really do C-style stacked arrays (a.k.a. ragged
multi-dimensional arrays), so binding them is nigh impossible without extra
C code.
Ok, also note a possible syntax is pointers, that in vala should have the
same semantics as in C, thus are fine for bindings stacked
Small comment: Do we really have to call them legacy C libraries?
Legacy implies that these are old-style libraries that we eventually
want to move away from, but in fact the culture of Vala is happy
coexistence with C libraries now and in the future, so it's not a legacy
at all.
I suggest
After some discussion with nemequ, I've put together some documentation
about writing bindings for non-GLib C code.
http://wiki.gnome.org/Vala/LegacyBindings
I'm sure there are many other situations that need to be covered, or
alternatives to the ones proposed; please expand or let me know and