Hi,
well it seems that the initial vision of E_STRICT to denote future
deprecation is no longer valid. Then again it might have been a
misunderstanding from the beginning as E_DEPRECATED would have been the
more obvious name in that case.
I still think that a flag on a per class basis would be the better
solution, but I guess I can accept this change.
This reminds me again about my question of how E_STRICT warnings are
added and how things are then handled (E_STRICT becomes E_ERROR or the
feature is removed entirely) with the future releases. I think a clear,
written down policy is needed (and as always may be overwritten via
common sense on a case by case basis).
regards,
Lukas
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
