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: | Andi Gutmans | Date: | Wed, 12 Mar 2003 20:32:36 +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 | Groups: | php.dev |
| Request: | Send a blank email to php-dev+get-95121@lists.php.net to get a copy of this message | ||
At 08:53 AM 3/12/2003 -0500, Andrei Zmievski wrote:
I have 2 questions: 1. Do the interface functions have to be explicitly specified as abstract?Nope. It shouldn't be allowed to be abstract because it's abstract by definition.
interface Foo {This shouldn't work. I guess there's a bug someplace. It's new code so I'm sure there will be some small things which need to be fixed. Andifunction bar();} Because this runs fine for me with no errors. 1. What is the difference between the following: interface Foo { } class Boo extends Foo { }
and class Zoo implements Foo { }-Andrei http://www.gravitonic.com/"In this age, which believes that there is a short cut to everything, the greatest lesson to be learned is that the most difficult way is, in the long run, the easiest."-Henry Miller, The Books in My Life-- PHP Development Mailing List <http://www.php.net/> To unsubscribe, visit: http://www.php.net/unsub.php