Re: Interface inheritance
| From: | Derick Rethans | Date: | Mon, 19 Apr 2004 12:19:12 +0000 |
| Subject: | Re: Interface inheritance | ||
| References: | 1 2 3 4 5 6 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-9380@lists.php.net to get a copy of this message | ||
On Mon, 19 Apr 2004, Zeev Suraski wrote:
> At 14:40 19/04/2004, Christian Schneider wrote:
> >Zeev Suraski wrote:
> >>In my opinion it doesn't, because it breaks the interface of the parent
> >>class. I.e., you can no longer use code you've written to work with an
> >>object of the parent class, with an object of the child class, which
> >>breaks one of the most fundamental principals of OO. In turn, it
> >
> >What about the generic/specialized class example? At least the constructor
> >has to be allowed to be different, no? Or was that what you meant by
> >"Maybe now that's constructors are out of the picture"?
>
> That's exactly what I meant, constructors don't have implementation checks
> any longer...
> If we can agree that for everything else we can apply these rules,
> including regular methods, it's a big step :)
I don't want it for regular methods, it's going to break BC. I can live
with anything, as long as it doesn't break PHP 4 code (not even with
E_STRICT on).
regards,
Derick