Re: Deprecate INTL_IDNA_VARIANT_2003
| From: | lists@rhsoft.net | Date: | Sat, 13 May 2017 15:39:05 +0000 |
| Subject: | Re: Deprecate INTL_IDNA_VARIANT_2003 | ||
| References: | 1 2 3 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-99028@lists.php.net to get a copy of this message | ||
Am 13.05.2017 um 17:30 schrieb Christoph M. Becker:
On 13.05.2017 at 17:14, Niklas Keller wrote:then supress the deprecation warning in case it's the internal default enforce people changing their PHP code which relies on "well, normally the defaults should just work" is doomed - in the next iteration a few years later you have to touch it again *because* of that2016-11-24 19:25 GMT+01:00 Christoph M. Becker <cmbecker69@gmx.de>:Changing the defaults in PHP 7.4 first has been part of the accepted RFC, see <https://wiki.php.net/rfc/deprecate-and-remove-intl_idna_variant_2003>.I've just noticed that ICU has deprecated the IDNA 2003 related functions as of ICU 55[1]. Therefore I suggest that we deprecate INTL_IDNA_VARIANT_2003 as of PHP 7.2, make INTL_IDNA_VARIANT_UTS46 the default as of PHP 8.0(?) (or even remove this parameter?), and remove INT_IDNA_VARIANT_2003 as of PHP 8.0. Otherwise we may get into trouble if ICU removes these functions. Thoughts? Does this change require an RFC?Please update the defaults for e.g. http://php.net/manual/en/function.idn-to-ascii.php, too. A default call shouldn't result in a deprecation notice IMO.