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 sugge
> Hello,
>
> This is the second time I've tried to post to the list, but I haven't
> seen my first attempt show up in the vala-list archive yet, so I thought
> I would resend, just in case.
>
> I'm still learning my way around vala so I may be doing something wrong,
> but according to the docs
I believe it's a bug in the compiler. It's non-sense to require an instance
when those are class-level instances.
However as a workaround you can use static fields. You can still initialize
them with class construct { } or static construct { }.
Also if you were thinking of overriding a protected cl
Hello,
This is the second time I've tried to post to the list, but I haven't
seen my first attempt show up in the vala-list archive yet, so I thought
I would resend, just in case.
I'm still learning my way around vala so I may be doing something wrong,
but according to the docs at https://
> 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 stacke
On 29 September 2013 01:45, Luca Bruno 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 (compact and not)
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
in
