On 13 November 2012 16:07, Anthony Ferrara <ircmax...@gmail.com> wrote: > What I would suggest, is not adding E_DEPRECATED for 5.5. Instead, > officially deprecate it in the docs. Then start a PR campaign to get > projects like WP to switch away from it. Get the word out there as much as > possible. Then in 1 to 2 years when 5.6/6 is released, add E_DEPRECATED. >
A very brief interjection from the documentation team's side of the fence (though I can't speak for everyone). Extensions, functions, etc. marked as deprecated in the documentation reflect the reality in the code. If a function is deprecated in php-src, then we document it as such in the manual. Since ext/mysql is not yet deprecated in the source, we cannot "officially deprecate it in the docs" with the usual "this function is deprecated, blah, blah" messages. This is why we have adopted the "soft-deprecation" boxes in the manual especially for ext/mysql, to step forward with that PR campaign (which has been going on for years upon years) until such a time as the extension is actually marked as deprecated in php-src. Long story short, the manual reflects the source. Put the deprecation into a release and we can document the extension as such. Hold back on the deprecation in the source and we can't stick a paragraph in the docs saying "this is deprecated", rather we can only continue to say that its use is "discouraged". -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
