Re: RFC: ext/mysql deprecation

From: Date: Fri, 16 Nov 2012 18:15:01 +0000
Subject: Re: RFC: ext/mysql deprecation
References: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19  Groups: php.internals 
Request: Send a blank email to internals+get-63938@lists.php.net to get a copy of this message
Steve Clay wrote:
On 11/15/12 3:11 PM, Anthony Ferrara wrote:
That's my suggestion. Officially deprecate it, but don't add E_DEPRECATED to it in 5.5. Update the documentation, and start a PR campaign to get off
This may be a narrow PR channel, but I'd focus on getting @deprecated into the built-in function stubs in all the IDEs. In PhpStorm I see lines through the function name, and there's a deprecation section in the "Inspect Code" report. I'm much more likely to notice those than notice changes in online docs or error log notices. But more importantly, anyone writing *new* code will see that feedback immediately.
The same should work with Eclipse and PDT or PHPEclipse. If the documentation is suitably marked then any usage will flag up the situation ... educate rather than penalise? -- Lester Caine - G8HFL ----------------------------- Contact - http://lsces.co.uk/wiki/?page=contact L.S.Caine Electronic Services - http://lsces.co.uk EnquirySolve - http://enquirysolve.com/ Model Engineers Digital Workshop - http://medw.co.uk Rainbow Digital Media - http://rainbowdigitalmedia.co.uk

« previous php.internals (#63938) next »