Re: Re: cvs: php4 /tests/classes interface_class.phpt interface_doubled.phpt interface_implemented.phpt interface_instantiate.phpt
interface_member.phpt interface_method.phpt interface_method_final.phpt interface_method_private.phpt interface_must_be_implemented.phpt
| From: | Andrei Zmievski | Date: | Wed, 12 Mar 2003 18:47:54 +0000 |
| Subject: | Re: Re: cvs: php4 /tests/classes interface_class.phpt interface_doubled.phpt interface_implemented.phpt interface_instantiate.phpt interface_member.phpt interface_method.phpt interface_method_final.phpt interface_method_private.phpt interface_must_be_implemented.phpt |
||
| References: | 1 2 3 4 | Groups: | php.dev |
| Request: | Send a blank email to php-dev+get-95095@lists.php.net to get a copy of this message | ||
On Wed, 12 Mar 2003, Sebastian Bergmann wrote:
> I have seen extended interfaces quite often in the Java world.
>
> IIRC, the following code currently runs without problems and it should
> stay that way, if it does not harm us in any way:
>
> <?php
> interface Foo {}
> interface Bar extends Foo {}
> class FooBar implements Bar {}
> ?>
I wasn't talking about interfaces extending interfaces - that is
perfectly fine. I was saying that "class blah extends <interface>" and
"class blah implements <interface>" is confusing.
-Andrei http://www.gravitonic.com/
When we eliminate the impossible, whatever remains,
however improbable, must be true. -- Sherlock Holmes