Re: [Vala] Issues will vala and pulse vapi

2015-11-22 Thread Evan Nemerson
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: > > >  Righ

Re: [Vala] Issues will vala and pulse vapi

2015-11-22 Thread Al Thomas
> 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

Re: [Vala] Issues will vala and pulse vapi

2015-11-22 Thread Al Thomas
> 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

Re: [Vala] Issues will vala and pulse vapi

2015-11-21 Thread Evan Nemerson
On Sat, 2015-11-21 at 23:37 -0600, Aaron Paden wrote: > On Sat, Nov 21, 2015 at 11:07 PM, Evan Nemerson > wrote: > > On Sat, 2015-11-21 at 22:45 -0600, Aaron Paden wrote: > > > On Sat, Nov 21, 2015 at 9:54 PM, Evan Nemerson > > com> > > > wrote: > > > > > > > > That's not quite right; the VAPI s

Re: [Vala] Issues will vala and pulse vapi

2015-11-21 Thread Aaron Paden
On Sat, Nov 21, 2015 at 11:07 PM, Evan Nemerson wrote: > On Sat, 2015-11-21 at 22:45 -0600, Aaron Paden wrote: >> On Sat, Nov 21, 2015 at 9:54 PM, Evan Nemerson >> wrote: >> > >> > That's not quite right; the VAPI shouldn't indicate that a *type* >> > is >> > "unmanaged"… it's up to your code to

Re: [Vala] Issues will vala and pulse vapi

2015-11-21 Thread Evan Nemerson
On Sat, 2015-11-21 at 22:45 -0600, Aaron Paden wrote: > On Sat, Nov 21, 2015 at 9:54 PM, Evan Nemerson > wrote: > > > > That's not quite right; the VAPI shouldn't indicate that a *type* > > is > > "unmanaged"…  it's up to your code to indicate whether an instance > > is > > unowned.  However, the

Re: [Vala] Issues will vala and pulse vapi

2015-11-21 Thread Aaron Paden
On Sat, Nov 21, 2015 at 9:54 PM, Evan Nemerson wrote: > > That's not quite right; the VAPI shouldn't indicate that a *type* is > "unmanaged"… it's up to your code to indicate whether an instance is > unowned. However, the question is really what the proper way to > destroy an instance is. > > In

Re: [Vala] Issues will vala and pulse vapi

2015-11-21 Thread Evan Nemerson
On Sat, 2015-11-21 at 20:48 -0600, Aaron Paden wrote: > On Sat, Nov 21, 2015 at 6:33 AM, Al Thomas > wrote: > > > > > > This looks complex so I can only give a few pointers. > > > > Does the code actually compile or are you getting an error about an > > unresolved symbol? > > Right, the code c

Re: [Vala] Issues will vala and pulse vapi

2015-11-21 Thread Aaron Paden
On Sat, Nov 21, 2015 at 6:33 AM, Al Thomas wrote: > > > This looks complex so I can only give a few pointers. > > Does the code actually compile or are you getting an error about an > unresolved symbol? Right, the code compiles, but the linker fails because of the unresolved symbols. I didn't thi

Re: [Vala] Issues will vala and pulse vapi

2015-11-21 Thread Al Thomas
> From: Aaron Paden > Sent: Saturday, 21 November 2015, 0:17 > Subject: [Vala] Issues will vala and pulse vapi > > So I was asking around IRC (both channels) about why a personal > project[1] I was working on was generating a non-existent > pulse_audio_source_info_destr

[Vala] Issues will vala and pulse vapi

2015-11-20 Thread Aaron Paden
So I was asking around IRC (both channels) about why a personal project[1] I was working on was generating a non-existent pulse_audio_source_info_destroy, and it looks like the vapi file is possibly the issue. I'm not that familiar with either vala or pulse, so possibly I'm just doing something rea