On 16/11/2012 08:55, Rasmus Lerdorf wrote: > I still don't see the point of using E_DEPRECATED like this for an > entire extension. And I think it will hurt more than it will help for an > extension this heavily used. It is going to encourage people to simply > turn off that warning because they will get it on every single request > which means they will never see the more subtle and granular > E_DEPRECATED warnings from other parts of their code.
Catch 22 - if you do nothing people will keep using it, even for new stuff and progress is never made. This sort of thing is obviously a horendous nightmare - I personally wonder if flat out shiping it to PECL with a warning on the PECL page but no E_DEPRECATED might be the better solution. At least then people who are installing it will be actively aware they're doing it, without the 'scary' errors spat out when they connect to a server. Anybody who needs this will ask their host for it or more likely their host will already have it installed, but people installing PHP for local dev machines will probably have to go find it (and the developers are the target audience for these sorts of things) - which should be enough to tell them there's something different about this extension, and they'll see the notice on the site. I honestly can't see a situation where that would bother people more than keeping it but throwing E_DEPRECATED fairly often with a view to moving it later anyway - rip the plaster off in one go so to speak. Maybe PHP has a lot of users that are somewhat unstable and incapable of using PECL, I dunno ;) -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
