Pierre wrote:
if foo-1.2.1 is E_STRICT compliant with 5.1.4 and foo-1.2.2 with
5.2.0, update to 1.2.2 must be the way. It is the safest way, the past
shown us that some E_STRICT can be related to (sometimes critical)
bugs and we should treat them as bugs. Also, I do not like the
additions of pedantic E_STRICT, but that's another issue.
I would hate to start to add such notice detections in any of my code,
including pear.
That requires that E_STRICT will not be added for any feature that is
not available since the first release of a given major version.
Otherwise you can't publish 1.2.2 without increasing the lowest
compatible php version. Which in turn is impractical as the PHP world
will never be fast enough to keep up with patch or even minor PHP
releases. Hosters are always behind 1 or 2 minor versions, at best.
regards,
Lukas
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
