maybe we should get another E_, E_NEARLY_DEPRECATED that way we can set this to that, and then 5.5 we can move it to E_DEPRECATED, that way people have to go read the docs, the amount of people even those who have been in the field for years, that dont know about php.net/<func> and still look stuff up on google makes me wonder that no matter how soft you make the change by doing it in the docs, wont make that much difference to how people react to it being dropped
On Mon, Jul 11, 2011 at 3:40 PM, Adam Harvey <ahar...@php.net> wrote: > On 11 July 2011 01:03, Philip Olson <phi...@roshambo.org> wrote: > > What this means to ext/mysql: > > > > - Softly deprecate ext/mysql with education (docs) starting today > > - Not adding E_DEPRECATED errors in 5.4, but revisit for 5.5/6.0 > > - Add pdo_mysql examples within the ext/mysql docs that mimic the > current > > examples, but occasionally introduce features like prepared statements > > - Focus energy on cleaning up the pdo_mysql and mysqli documentation > > - Create a general "The MySQL situation" document that explains the > situation > > I'm hugely +1 on this. (Which won't be a shock to anyone on IRC.) It's > time to start softening the user base up for the idea that, one day, > ext/mysql will in fact go away, and probably won't be terribly > mourned. > > Adam > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > >
