Re: RfC: rethink OO inheritance strictness
| From: | Derick Rethans | Date: | Thu, 03 Aug 2006 07:46:43 +0000 |
| Subject: | Re: RfC: rethink OO inheritance strictness | ||
| References: | 1 2 3 4 5 6 7 8 9 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-25164@lists.php.net to get a copy of this message | ||
On Thu, 3 Aug 2006, Pierre wrote:
> Hello,
>
> On 8/3/06, Derick Rethans <derick@php.net> wrote:
>
> > > In this particular case I think it should be possible to mark certain
> > > internal
> > > methods as strict and keep userspace methods loose.
> >
> > But I would like to see atleast an e_strict warning of signatures are
> > violated to give atleast the options to be strict and get warnings for
> > it. I am pretty sure Edin doesn't give a **** about e_strict warnings...
> > so that will work fine. I think that Zeev suggested something like this.
>
> For what I understand (and agree), he meant the other way 'round.
> Users who like strictness will have to use an extra keyword in the
> declaration. Users who don't care will not have to change anything in
> their (working) code.
No, he said that with that strict keyword it would E_ERROR out, but
without it it would simply throw an E_STRICT.
Derick