Re: [Vala] using a non-glib C library in vala

[Jürg Billeter <j bitron ch>]

On Wed, 2009-09-16 at 15:41 -0400, Michael B. Trausch wrote:
> The bug is "memset code generation is incorrect", so I'm not sure how
> you can say "Vala should not generate invalid code, but this bug is
> indeed invalid".  The bug is that the code generation is incorrect.
>
> Whether or not the binding that triggers the incorrect code generation
> is itself incorrect is another, distinct issue.  If it is indeed
> incorrect, then there should be a Vala compiler diagnostic to catch it.
> So, if what you're saying is correct, that bug report really contains
> *two* valid bugs, one that isn't actually described, and the one that is
> (invalid code generation).

As bindings describe the mapping of a high-level API to the low-level C
API, there are unlimited possibilities how you can break code generation
with incorrect bindings. It's impossible for the compiler to detect all
of these cases.

That said, if this was a valid binding, the corresponding memset
compiler bug would be bug 578968¹.

Jürg

¹ https://bugzilla.gnome.org/show_bug.cgi?id=578968