> The main argument is that we haven't actually made it clear in the > manual that the extension is going to be deprecated. There is a user > note on http://www.php.net/manual/en/book.mysql.php and a "This > extension is not recommended for writing new code" on > http://www.php.net/manual/en/intro.mysql.php > > As Anthony mentioned, this is a very weak best-practice type of message > that we are only barely whispering here. To go from that to start > throwing deprecation warnings on what is perhaps the most heavily used > PHP extension ever is a rather drastic step. Your argument seems to be, > "Well, there is no point documenting it because people won't read it > anyway", which may be true, but we haven't actually tried that yet and > for something like this I think it should be the first step.
I wanted to clarify that it was intentional to not use the word "deprecated" in the documentation because it's not deprecated. However, the documentation for *every* ext/mysql function begins with a pink box that says it's discouraged, and these boxes suggest alternatives via mysqli/pdo_mysql. Whatever the case, we'll update the documentation now. It'll clarify that one day this extension will be deprecated. The only question here is the "how" and "when" but that's not a showstopper for the docs. As for the ext/mysql->mysqli conversion script. It's outdated and difficult to find but we'll make an official php.net version and promote/update it so eventually it'll become awesome. It's certainly not ready today. I suspect people will also want an ext/mysql->pdo_mysql version. No promises there… :) Regards, Philip -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
