Re: RfC: rethink OO inheritance strictness
| From: | Lukas Smith | Date: | Fri, 04 Aug 2006 07:49:33 +0000 |
| Subject: | Re: RfC: rethink OO inheritance strictness | ||
| References: | 1 2 3 4 5 6 7 8 9 10 11 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-25194@lists.php.net to get a copy of this message | ||
Derick Rethans wrote:
- Add a new flag to methods (at the implementation level) that will allow to flag them as 'strict' - In case such a strict method is improperly overridden - error out (E_ERROR) - In case a non-strict method is improperly overridden - emit E_STRICTi am fine with that proposal .. if we do split up E_STRICT into E_STRICT (feature is not clean "proper" code) and E_DEPRECATED (feature will be dropped in the next major release) also note that the first two points in Derick's list only apply to classes on the C level .. userland classes will only trigger E_STRICT if they are improperly overwritten. will it be possible to get the information about the strictness of internal classes via the reflection API? or will we leave this to documentation only? regards, Lukas