realbasic-plugins
[Top] [All Lists]

Re: Interface cannot be inherited from other interface?

To: REALbasic Plugins <realbasic-plugins at lists dot realsoftware dot com>
Subject: Re: Interface cannot be inherited from other interface?
From: Aaron Ballman <aaron at realsoftware dot com>
Date: Thu, 27 May 2004 12:31:41 -0500
Delivered-to: realbasic-plugins at lists dot realsoftware dot com
List-help: <mailto:realbasic-plugins-request@lists.realsoftware.com?subject=help>
List-id: REALbasic Plugins <realbasic-plugins.lists.realsoftware.com>
List-post: <mailto:realbasic-plugins@lists.realsoftware.com>
References: <BCDBFF45 dot 1C11E%sunshine at public dot kherson dot ua>
Why?


In OO design this is allowed.

In COM this is allowed. I.e. In Visual BASIC also allowed.

In Java allowed.

Why not in REALbasic?

Or this is tmp problem ?

You seem confused to me. We do support classes implementing multiple interfaces. You just separate the interfaces by a comma.

Unless you are talking about combining multiple interfaces...

With RB, you _implement_ an interface. And since an interface itself cannot have code in it (which means it cannot implement anything), then an interface can't inherit in the traditional sense (for example, via the Super).

That being said, I don't think there's any reason we can't have an Interface that passes along other interfaces as an aggregate. It's just a tricky thing to word since an interface can't implement anything. Of course, Mars may come along and correct my view on this too. ;-)

~Aaron
--
In response to a stupid question I once asked: "My brain uses patterns to format responses to your inputs, but I don't have one for that. Do you speak German?" ~ Zola
_______________________________________________
Unsubscribe or switch delivery mode:
<http://support.realsoftware.com/listmanager/>

Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>

<Prev in Thread] Current Thread [Next in Thread>