Re: [Vala] Implicating two interface, when methods name are different(name conflict)

2011-08-09 Thread Tal Hadad

I don't know if you've noticed, but how should the syntax would be when the 
interface have already implicate this?
AFAIK, it happens in two cases:
* Automatic property in interface.
* The interface implicate method.
Have you noticed that? How shell them decelerate as explicit?
I think it should be this way:
(return_type) (interface_name).(method_name) ([args]);
Where methods which isn't implicated in the interface(implicated in class) is 
that way:

(return_type) (interface_name).(method_name) ([args]) { }

Same goes for properties.
What do you think?

Tal

From: tal...@hotmail.com
To: lethalma...@gmail.com
Date: Sat, 6 Aug 2011 22:11:10 +0300
CC: vala-list@gnome.org
Subject: Re: [Vala] Implicating two interface, when methods name are 
different(name conflict)

 
Thanks for quick response and quick patch Luca!
I'll hope it will merge into Vala.
 
Tal
 
> Date: Sat, 6 Aug 2011 20:42:01 +0200
> From: lethalma...@gmail.com
> To: tal...@hotmail.com
> CC: vala-list@gnome.org
> Subject: Re: [Vala] Implicating two interface, when methods name are 
> different(name conflict)
> 
> On Sat, Aug 06, 2011 at 09:33:49PM +0300, Tal Hadad wrote:
> > 
> > I has some C#/.Net past and it possible to implicate two different 
> > interface, where both contains "foo" method.
> > The idea behinds this solution, is that one of the implication must be 
> > explicit:
> 
> https://bugzilla.gnome.org/show_bug.cgi?id=652098
> 
> -- 
> http://www.debian.org - The Universal Operating System
  

___
vala-list mailing list
vala-list@gnome.org
http://mail.gnome.org/mailman/listinfo/vala-list
  ___
vala-list mailing list
vala-list@gnome.org
http://mail.gnome.org/mailman/listinfo/vala-list


Re: [Vala] Implicating two interface, when methods name are different(name conflict)

2011-08-06 Thread Tal Hadad

Thanks for quick response and quick patch Luca!
I'll hope it will merge into Vala.

Tal

> Date: Sat, 6 Aug 2011 20:42:01 +0200
> From: lethalma...@gmail.com
> To: tal...@hotmail.com
> CC: vala-list@gnome.org
> Subject: Re: [Vala] Implicating two interface, when methods name are 
> different(name conflict)
> 
> On Sat, Aug 06, 2011 at 09:33:49PM +0300, Tal Hadad wrote:
> > 
> > I has some C#/.Net past and it possible to implicate two different 
> > interface, where both contains "foo" method.
> > The idea behinds this solution, is that one of the implication must be 
> > explicit:
> 
> https://bugzilla.gnome.org/show_bug.cgi?id=652098
> 
> -- 
> http://www.debian.org - The Universal Operating System
  ___
vala-list mailing list
vala-list@gnome.org
http://mail.gnome.org/mailman/listinfo/vala-list


Re: [Vala] Implicating two interface, when methods name are different(name conflict)

2011-08-06 Thread Luca Bruno
On Sat, Aug 06, 2011 at 09:33:49PM +0300, Tal Hadad wrote:
> 
> I has some C#/.Net past and it possible to implicate two different interface, 
> where both contains "foo" method.
> The idea behinds this solution, is that one of the implication must be 
> explicit:

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

-- 
http://www.debian.org - The Universal Operating System
___
vala-list mailing list
vala-list@gnome.org
http://mail.gnome.org/mailman/listinfo/vala-list


[Vala] Implicating two interface, when methods name are different(name conflict)

2011-08-06 Thread Tal Hadad

I has some C#/.Net past and it possible to implicate two different interface, 
where both contains "foo" method.
The idea behinds this solution, is that one of the implication must be explicit:
public interface ISampleInterface1
{
void Foo();
}

public interface ISampleInterface2
{
void Foo();
}


class ImplementationClass : ISampleInterface
{
// Explicit interface member implementation: 
void ISampleInterface1.Foo()
{
// Method implementation.
}

// Explicit interface member implementation: 
void ISampleInterface2.Foo()
{
// Method implementation.
}

// Not an interface member implementation: 
public void Foo()
{
// Method implementation.
}

static void Main()
{
// Declare an class instance.
ImplementationClass obj = new ImplementationClass();
// Call the member of class.
obj.SampleMethod();

ISampleInterface1 obj1 = obj;
// Call the member of ISampleInterface1
obj1.SampleMethod();


ISampleInterface2 obj2 = obj;
// Call the member of ISampleInterface1
obj2.SampleMethod();
}
}

This code is based on MSDN(with modifications).
I don't know weather it's possible to do this in GObject and Vala, and how to 
if possible?
Does this approach and model is wrong?(Because I know Vala interface are more 
powerful than most langs)

Yours,
Tal
  ___
vala-list mailing list
vala-list@gnome.org
http://mail.gnome.org/mailman/listinfo/vala-list