Antony Dovgal wrote:
Well, that's what major versions are for, right?
Bugfix releases are for bugfixes, while major versions may introduce new
things and features.
Err we add features in minor (and even patch level) versions all the time.
Sorry, I still fail to see a reason to "filter" error messages..
The point of E_STRICT is to encourage forward compatible code. However
as I pointed out for many developers it will not be feasible to always
target the latest version of PHP. This means that they will be coding
against some other, yet defined PHP version.
So for example
5.2.1 is the latest version
5.1.2 is the target for development.
Now there might be several new E_STRICT messages that cannot be worked
around without increasing the target development version.
This means that either:
1) I turn off E_STRICT on my development box to retain my sanity
2) I have some filter mechanism that ensures I only get E_STRICT
messages that existed in 5.1.2
What I am proposing is a tiny weeny change in PHP to make it trivial to
implement 2) in userland.
This makes sense because as time progresses I might increase my target
version. Maybe even port to a new major version. In which case I am much
better off having code that is already E_STRICT compliant uptil 5.1.2.
So there will be much less work for me to do. Code generally will be
much easier to port to new major versions that drop deprecated features.
Adoption rates of new major versions can go up. Everybody is happy.
regards,
Lukas
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
