I suggest that we add E_STRICT now, but not include E_STRICT into
E_ALL, so people who are not using E_STRICT error reporting level
don't have their applications start spewing strict messages.
We cannot force people to change their code, all we can reasonably do
is provide notification mechanism, for those who do.
On 15-May-06, at 9:16 AM, Derick Rethans wrote:
On Mon, 15 May 2006, Ilia Alshanetsky wrote:
My opinion is that if we intend to make something stop working
(give fatal
error) in future releases we need to provide some form of notice
be it
E_STRICT or E_NOTICE to our users now, so they can anticipate the
change. As
far as inclusion of E_STRICT into E_ALL, I think this is a good
idea, but is
probably premature for the 5.2 release.
Then when do you suggest we add it (before 6.0)?
regards,
Derick
Ilia Alshanetsky
Advanced Internet Designs Inc.
[EMAIL PROTECTED]
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
