Re: RFC: ext/mysql deprecation
| From: | Levi Morrison | Date: | Fri, 16 Nov 2012 18:14:12 +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 20 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-63937@lists.php.net to get a copy of this message | ||
I'm already working somewhat with the PhpStorm guys on other things
relating to PHP. I could spearhead that effort, but I won't bring it
up until this is decided.
On Fri, Nov 16, 2012 at 10:53 AM, Steve Clay <steve@mrclay.org> 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.
>
> Steve Clay
> --
> http://www.mrclay.org/
>
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>