Hi,
no, you did not understand: I'm not trying to create object from an
interface. I'm having class Foo, that is _NOT_ inheriting Object, but
it's still a typed class, and it's implementing interface IFoo. This is
(or used to be) legal. I'm creating instances of that class, but the
reference is
On Sat, Dec 04, 2010 at 12:35:26 +0100, Marco Trevisan (Treviño) wrote:
Il giorno ven, 03/12/2010 alle 17.18 +0100, Abderrahim Kitouni ha
scritto:
session_proxy.name_acquired.connect (this.name_acquired);
What I would have done is:
session_proxy.name_acquired.connect ((name) =
On Fri, Dec 03, 2010 at 15:38:38 -0800, Anatol Pomozov wrote:
I have a class that contains a field and method with the same name,
and Valac does not like it. What is the reason? Other languages
(C#/Java) allow it.
Pardon me. C# does NOT allow that:
test.cs(3,17): error CS0102: The type `Foo'
vandr...@yandex.ru
___
vala-list mailing list
vala-list@gnome.org
http://mail.gnome.org/mailman/listinfo/vala-list
On Sun, Dec 05, 2010 at 17:32:17 +0100, Aleksander Wabik wrote:
I'm having class Foo, that is _NOT_ inheriting Object, but it's still
a typed class, and it's implementing interface IFoo. This is (or used to
be) legal.
No, it is not and never was legal. Interfaces depend on runtime support
On Sun, Dec 05, 2010 at 17:32:17 +0100, Aleksander Wabik wrote:
I'm having class Foo, that is _NOT_ inheriting Object, but it's still
a typed class, and it's implementing interface IFoo. This is (or used to
be) legal.
No, it is not and never was legal. Interfaces depend on runtime support
I am really sorry for flood, but it just came into my mind:
(CCing Jürg , as I think I've found a bug in the object system design)
On Sun, Dec 05, 2010 at 17:32:17 +0100, Aleksander Wabik wrote:
I'm having class Foo, that is _NOT_ inheriting Object, but it's still
a typed class, and it's
