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




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_hd hotmail com
To: lethalman88 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: lethalman88 gmail com
To: tal_hd 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                                                              
                    


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]