On Sun, 21 Dec 2014 06:49:49 +0300, Xinchen Hui <larue...@php.net> wrote:
Hey:
On Sun, Dec 21, 2014 at 11:43 AM, Pierre Joye <pierre....@gmail.com>
wrote:
On Dec 21, 2014 10:23 AM, "Xinchen Hui" <larue...@php.net> wrote:
Hey:
I am strongly against to remove ext/mysql
that means, all wordpress users/maintainers, will not able to upgrade
to PHP7 without pain.
https://make.wordpress.org/core/2014/04/07/mysql-in-wordpress-3-9/
Basically wp and mysql are wrong arguments.
we have upgrade issues, they also have that..
I know lots of sites are based on old version wordpress, and they did
lot's of custom developing on it..
they will not able to upgrade to any new wordpress..
Also last time we discussed that there were a couple of oppositions to
remove deprecated features in 7.
yes..
My take is that we should not have a mass vote but options for each
feature.
Also if we do not remove deprecated features we may as a well remove the
deprecation as it makes no sense to keep it if we never actually remove
the
affected features.
I agree..
for ext/mysql, I think it's okey to remove the deprecated warning..
thanks
Cheers,
Pierre
Hey Xinchen,
Couldn't we just write a compatibility layer, like Anthony did for
password_hash? (but in the opposite direction, for people who are stuck
with ext/mysql and want to upgrade to 7)
There'll be one problem with mysqli being an object and not a resource,
but I'm sure would be able to solve it.
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
