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_STRICT
i 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
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
