On Nov 28, 2012, at 2:08 AM, Pierre Joye wrote: > hi, > > On Wed, Nov 28, 2012 at 10:55 AM, Alexey Zakhlestin <indey...@gmail.com> > wrote: >> I voted "no", "(b)" >> We should mention deprecation in manual as hard as possible, we should >> mention it in ext/mysql/config.m4 and any other place we can reach. >> Then, at some point (I'm fine with 5.6, but 6.0 would do also), we >> should just move it to PECL, without using E_DEPRECATED > > That's exactly why we should use E_DEPRECATED now and not in 5.x+1. > Also no way to kill it in 5.x, that would be worst than anything else.
The idea of adding E_DEPRECATED now, and then removing it in PECL, is not an opinion held by everyone. > That being said, let not start this thread, every argument has been > mentioned many times already. Let vote. The idea of moving it to PECL is not represented in the vote. But it's something to consider as it's a real possibility. It could both symbolize that we are serious about not using ext/mysql, and considering most Linux distros would simply switch to offering the PECL version, it'd probably not break much. Worth thinking about, at least. I'm not yet certain what we should do but this PECL topic is intriguing. Hopefully a few others will weigh in with their related thoughts. Regards, Philip -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
