[PATCH][weston] animation: Fix potential leak of memory pointed to by move

Free move before return if animation is null. Signed-off-by: Lucas Tanure --- src/animation.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/src/animation.c b/src/animation.c index cc7482d..2c7943f 100644 --- a/src/animation.c +++ b/src/animation.c @@

[PATCH weston 1/2] compositor: don't crash if destroying a compositor without a backend

Calling weston_compositor_destroy() on a pointer returned by weston_compositor_create() should be always valid, even if the compositor does not have yet a backend. Signed-off-by: Giulio Camuffo --- src/compositor.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)

[PATCH weston 2/2] main: fix destroying the compositor on error while starting

Signed-off-by: Giulio Camuffo --- src/main.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/src/main.c b/src/main.c index a98570e..1591018 100644 --- a/src/main.c +++ b/src/main.c @@ -730,16 +730,16 @@ int main(int argc, char *argv[])

Re: Enums, bitfields and wl_arrays

Hi, Pekka Paalanen wrote: > Adding these attributes to XML must not change the signatures generated > by wayland-scanner. > > Why: these are also used in C++, which does not implicitly covert > between enums and other stuff, which would break the build. >

Re: Enums, bitfields and wl_arrays

The enum discussion seems to become a lengthy one and it's becoming hard to see the forest for the trees. I'll give my input as a Java bindings dev. Please correct any bad assumptions or observations I've made. >From what I see in Auke's patches: - Defining an uint (bitfield) or int (single