Re: [Vala] Issues will vala and pulse vapi

> From: Evan Nemerson > Sent: Sunday, 22 November 2015, 3:54 > Subject: Re: [Vala] Issues will vala and pulse vapi > > On Sat, 2015-11-21 at 20:48 -0600, Aaron Paden wrote: >> Right, the code compiles, but the linker fails because of the >> unresolved symbols. I didn't

Re: [Vala] help with writting vapi...

> From: Matrix > Sent: Sunday, 22 November 2015, 8:07 > Subject: [Vala] help with writting vapi... > > i'm writting hiredis vala's binding.. > > here is a function like this: > > redisContext *redisConnectWithTimeout(const char *ip, int port, const > struct timeval

Re: [Vala] help with writting vapi...

On Mon, 2015-11-23 at 01:03 +, Al Thomas wrote: > > From: Matrix > > > Sent: Sunday, 22 November 2015, 8:07 > > Subject: [Vala] help with writting vapi... > > > > i'm writting hiredis vala's binding.. > > > > here is a function like this: > > > > redisContext

Re: [Vala] Issues will vala and pulse vapi

On Mon, 2015-11-23 at 00:56 +, Al Thomas wrote: > > From: Evan Nemerson > > > Sent: Sunday, 22 November 2015, 3:54 > > Subject: Re: [Vala] Issues will vala and pulse vapi > > > > On Sat, 2015-11-21 at 20:48 -0600, Aaron Paden wrote: > > >  Right, the code compiles, but

Re: [Vala] help with writting vapi...

On Sun, 2015-11-22 at 16:07 +0800, Matrix wrote: > Hi : > > i'm writting hiredis vala's binding.. > > here is a function like this: > > redisContext *redisConnectWithTimeout(const char *ip, int port, const > struct timeval tv); > > so, how to tell the valac that the 3rd param is struct value

[Vala] help with writting vapi...

Hi : i'm writting hiredis vala's binding.. here is a function like this: redisContext *redisConnectWithTimeout(const char *ip, int port, const struct timeval tv); so, how to tell the valac that the 3rd param is struct value not struct pointer?

Re: [Vala] Issues will vala and pulse vapi

> From: Aaron Paden > Sent: Sunday, 22 November 2015, 2:48 > Subject: Re: [Vala] Issues will vala and pulse vapi >> From an object oriented design point of view your SinkSoureList >> class is doing too much. Initialisation should be done elsewhere >> and I think it is