Re: RFC: ext/mysql deprecation

hi Anthony, On Mon, Nov 19, 2012 at 6:22 PM, Anthony Ferrara <ircmaxell@gmail.com> wrote: > Kris, > > >> By "NEXT" are you referring to 6.0 or 5.6? > > > Whatever the release after 5.5 is. Be it 5.6, or 6.0, NEXT indicates the > next temporal release... > > >> >> Also, can you add an option for raising E_DEPRECATED in 5.5 then removing >> support altogether in 6? > > > That's already in there. That's what I mean by hard-deprecating it for > 5.5... > > And in either case, removal would happen one release after hard > deprecation... I do not follow the logic. It is too heavy to use the right deprecation flag for the connect function only, but it is perfectly fine to kill one of the most widely used extension in php history in a minor version? I'd rather go with the flag and kill it in 6. Cheers, -- Pierre @pierrejoye | http://blog.thepimp.net | http://www.libgd.org