Hi On 13 November 2012 00:29, Rasmus Lerdorf <ras...@lerdorf.com> wrote: > That is simply not true. If you download PHP and do ./configure && make > install you do not get MySQL support. You have to explicitly specify > that you want it.
My apologies then. I actually checked a ./configure output, and saw under Configuring extensions "checking for MySQL support... no" I assumed it was going to try to enable it if it was available. Lots of other extensions have the wording "checking whether to enable", which is why I differentiated it from those. On 13 November 2012 09:03, Lester Caine <les...@lsces.co.uk> wrote: > YES people can simply switch off the checks, but again that misses the whole > problem! Having switched off the checks - you have no idea what is about to > blow up. If users wish to deliberately ignore (or worse, specifically disable) informative messages during development, that is their own problem. When ext/mysql is finally removed, nobody will be able to say they didn't have enough warning. The sooner we get this warning out there (i.e. E_DEPRECATED + message in the documentation starting with 5.5), the sooner wider community can start adjusting for it. There is no point delaying it as much as possible. As Sherif said, there has been far too much procrastination on the subject already. Lets get E_DEPRECATED in for the first RC so all of the social-focused php sites can get their rants out early, and get a few users thinking about the future of their codebases as soon as possible. Maybe even some of them will decide to contribute back and write some adoption guides and/or cheat sheets. -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
