[Vala] [PATCH] BytesArray members

I found the attached patch necessary to use the BytesArray. Cheers, -- :M: Index: vapi/glib-2.0.vapi === --- vapi/glib-2.0.vapi (Revision 2422) +++ vapi/glib-2.0.vapi (Arbeitskopie) @@ -3044,6 +3044,9 @@ public void sort (CompareF

Re: [Vala] How to wrap select(2)'s fd_set?

* Michael 'Mickey' Lauer wrote, On 05/02/09 15:39: Am Thursday 05 February 2009 15:03:57 schrieb Sam Liddicott: Ok, I now found out: FD_ZERO is defined as __FD_ZERO which in turn is defined as: /* We don't use `memset' because this would require a prototype and the array isn't too big. *

Re: [Vala] posix.vapi additions (signal)

On Thu, 2009-02-05 at 17:00 +0100, Michael 'Mickey' Lauer wrote: > Am Thursday 05 February 2009 16:04:04 schrieb Ed Schouten: > > * Jürg Billeter wrote: > > > On Tue, 2009-02-03 at 02:07 +0100, Michael 'Mickey' Lauer wrote: > > > > Please add to posix.vapi: > > > > > > Thanks, committed. > > > > W

Re: [Vala] posix.vapi additions (termios)

Am Thursday 05 February 2009 16:06:28 schrieb Ed Schouten: > Same comment as my previous email, this binding is awful in the fact > that it creates bindings for totally non-standard interfaces. The > inclusion of c_ispeed and c_ospeed is unneeded. The fields of struct > termios could have been made

Re: [Vala] posix.vapi additions (signal)

Am Thursday 05 February 2009 16:04:04 schrieb Ed Schouten: > * Jürg Billeter wrote: > > On Tue, 2009-02-03 at 02:07 +0100, Michael 'Mickey' Lauer wrote: > > > Please add to posix.vapi: > > > > Thanks, committed. > > Wouldn't it have been better to make this type safe? We could have used > enumerat

Re: [Vala] How to wrap select(2)'s fd_set?

Am Thursday 05 February 2009 15:03:57 schrieb Sam Liddicott: > >> Ok, I now found out: > >> > >> FD_ZERO is defined as __FD_ZERO which in turn is defined as: > >> > >> /* We don't use `memset' because this would require a prototype and > >> the array isn't too big. */ > >> #define __FD_ZERO(s) \

Re: [Vala] posix.vapi additions (termios)

Same comment as my previous email, this binding is awful in the fact that it creates bindings for totally non-standard interfaces. The inclusion of c_ispeed and c_ospeed is unneeded. The fields of struct termios could have been made type safe, to disallow assignments of, say, iflags to oflags, etc.

Re: [Vala] How to wrap select(2)'s fd_set?

* David Keijser wrote, On 05/02/09 13:07: 2009/2/5 Michael 'Mickey' Lauer : Am Friday 30 January 2009 14:26:51 schrieb Michael 'Mickey' Lauer: Am Friday 30 January 2009 08:30:43 schrieb Jürg Billeter: FdSet should be a struct, not a class, we do not need reference type semantics

Re: [Vala] How to wrap select(2)'s fd_set?

2009/2/5 Michael 'Mickey' Lauer : > Am Friday 30 January 2009 14:26:51 schrieb Michael 'Mickey' Lauer: >> Am Friday 30 January 2009 08:30:43 schrieb Jürg Billeter: >> > FdSet should be a struct, not a class, we do not need reference type >> > semantics here. This eliminates unnecessary heap allocat

Re: [Vala] How to wrap select(2)'s fd_set?

Am Friday 30 January 2009 14:26:51 schrieb Michael 'Mickey' Lauer: > Am Friday 30 January 2009 08:30:43 schrieb Jürg Billeter: > > FdSet should be a struct, not a class, we do not need reference type > > semantics here. This eliminates unnecessary heap allocation. FD_ZERO > > should be bound as ini

[Vala] posix.vapi additions (termios)

Please add to posix.vapi: [CCode (cheader_filename = "termios.h")] public const int B0; [CCode (cheader_filename = "termios.h")] public const int B50; [CCode (cheader_filename = "termios.h")] public const int B75; [CCode (cheader_filename = "termios.h")] public cons