At 00:33 13/07/2005, Nicholas Telford wrote:
Firstly, a major version number increment implies a major change (4.2.0 and 4.3.0 had much more major changes than this iirc).
That's the thing, though. 4.4.0 was not pitched as a major release. It was, and still is, pitched as a bugfix release. Quoting php.net:
"he increased middle digit was required because the fix that corrected the problem with references changed PHP's internal API. PHP 4.4.0 does not have any new features, and is solely a bugfix release."
The average user, or even fairly informed user, should have no reason to guess that he should be auditing his code because he installed a bugfix release.
Secondly, as far as I'm aware, it doesn't issue a warning, it issues notices which, and this has been stressed on many occasions, should not be displayed on production servers.
Sorry for nitpicking, but no type of errors, whether they're warnings, notices or fatal errors, should be displayed on production systems. I don't see a real difference between warnings and notices, it depends primarily on the type of developer, rather than the stage of the application. Some developers, such as myself - would not be willing to deploy code that is not 'E_NOTICE complaint', and would clean E_NOTICEs just as much as E_WARNINGs. They'd log them or display them in exactly the same way.
Lastly, there IS a note in the announcement stating that the major version increase is due to a non-BC change, I don't see what everyone is complaining about. Perhaps you should request that your users read what they're downloading before they download it.
Wrong, read the announcement again. It mentions the internal API. It gives nobody any reason to even remotely suspect that their code needs to be altered in order to be complaint.
Zeev -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
