# Deprecate INTL_IDNA_VARIANT_2003 - Thread: https://externals.io/message/97164 - Original archive: https://news-web.php.net/php.internals/97164 - Started by Christoph M. Becker on 2016-11-24T18:25:39+00:00 - Messages: 7 - Reply by email to internals@lists.php.net - More for agents: search with https://externals.io/search.md?q={query} · JSON API at https://externals.io/api · documentation at https://externals.io/llms.txt --- ## #97164 — Christoph M. Becker — 2016-11-24T18:25:39+00:00 URL: https://externals.io/message/97164#97164 Hi! 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? [1] -- Christoph M. Becker --- ## #99026 — Niklas Keller — 2017-05-13T15:14:04+00:00 URL: https://externals.io/message/97164#99026 · In reply to: #97164 2016-11-24 19:25 GMT+01:00 Christoph M. Becker : > Hi! > > 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. --- ## #99027 — Christoph M. Becker — 2017-05-13T15:30:06+00:00 URL: https://externals.io/message/97164#99027 · In reply to: #99026 > 2016-11-24 19:25 GMT+01:00 Christoph M. Becker : > > > […] > > 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. Changing the defaults in PHP 7.4 first has been part of the accepted RFC, see . -- Christoph M. Becker --- ## #99028 — lists@rhsoft.net — 2017-05-13T15:39:05+00:00 URL: https://externals.io/message/97164#99028 · In reply to: #99027 Am 13.05.2017 um 17:30 schrieb Christoph M. Becker: > > > > […] > > Changing the defaults in PHP 7.4 first has been part of the accepted > RFC, see > . 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 that --- ## #99029 — Niklas Keller — 2017-05-14T07:41:59+00:00 URL: https://externals.io/message/97164#99029 · In reply to: #99027 2017-05-13 17:30 GMT+02:00 Christoph M. Becker : > > > > […] > > Changing the defaults in PHP 7.4 first has been part of the accepted > RFC, see > . I've missed that, could we please have a follow-up RFC that changes that to 7.2? I don't see a reason to touch it twice. Regards, Niklas --- ## #99031 — Christoph M. Becker — 2017-05-14T15:20:05+00:00 URL: https://externals.io/message/97164#99031 · In reply to: #99029 > 2017-05-13 17:30 GMT+02:00 Christoph M. Becker : > > > […] > > I've missed that, could we please have a follow-up RFC that changes that to > 7.2? I don't see a reason to touch it twice. Not changing the default in PHP 7.2 has been suggested by Sara[1], and it was part of the vote, so I don't think a follow-up RFC would be in order. If you think otherwise, feel free to submit a new RFC. :) [1] -- Christoph M. Becker --- ## #99032 — Niklas Keller — 2017-05-14T15:58:39+00:00 URL: https://externals.io/message/97164#99032 · In reply to: #99031 > > Not changing the default in PHP 7.2 has been suggested by Sara[1], and > it was part of the vote, so I don't think a follow-up RFC would be in > order. If you think otherwise, feel free to submit a new RFC. :) > > [1] It was part of the RFC, but no vote option or something like that. @Sara: What's your current stance on this? Regards, Niklas