Re: RfC: rethink OO inheritance strictness
| From: | Derick Rethans | Date: | Fri, 21 Jul 2006 09:29:07 +0000 |
| Subject: | Re: RfC: rethink OO inheritance strictness | ||
| References: | 1 2 3 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-24811@lists.php.net to get a copy of this message | ||
On Fri, 21 Jul 2006, Lukas Smith wrote:
> Richard Quadling wrote:
> > I agree with this point. The sub class is a valid entity in its own
> > right. The methods (and the parameters) it has are part of that class.
> > If they overwrite a parent class's method, then fine. Instance of
> > either class would have different parameters for the same named
> > method.
>
> Its not about being "right". Acedemically Marcus changes are correct. The
> question is just if we want to force this way of working onto PHP, or if it
> makes more sense to make it optional.
I would say that if you want to use it in the "wrong" lenient way that
you need to mark your classes as such and not the other way around. This
might also have the effect that people see PHP as a better language
(because of the OO stuff is "correct" by default.
regards,
Derick