Re: Write down a deprecation policy
| From: | Rowan Collins | Date: | Thu, 25 Aug 2016 11:28:20 +0000 |
| Subject: | Re: Write down a deprecation policy | ||
| References: | 1 2 3 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-95443@lists.php.net to get a copy of this message | ||
On 25/08/2016 12:10, Lester Caine wrote:
Is there any well documented alternative way of achieving the same results as provided by these functions? Much of the time there is on-list debates on how something should be done, but it gets somewhat watered down in a migration guide ... if it makes it there at all.In this specific case, look at http://php.net/manual/en/function.iconv.php or http://php.net/manual/en/function.mb-convert-encoding.php But in general, yes, as Dave Walker mentioned, documenting proper migration steps should be a standard part of any deprecation. Much as I appreciate the Meaningless Internet Points it's earning me, this Stack Overflow post explaining preg_replace_callback should really have been a prominently-linked page in the official manual: http://stackoverflow.com/a/15454454/157957 Regards, -- Rowan Collins [IMSoP]