Front page | perl.perl5.porters |
Postings from October 2016
On 10/27/2016 10:41 AM, Aristotle Pagaltzis wrote: > * Aristotle Pagaltzis <pagaltzis@gmx.de> [2016-10-27 10:28]: >> 0 0 26 >> 1 0 26 >> 1 1 702 >> 0 1 702 > FWIW I am uncomfortable with fixing this right away, since there might > be code which inadvertently relies on this. There is no question in my > mind about *whether* this ought to be fixed, since if there is any code > that depends on this bug, then with 100% certainty there is much more > code which expects this *not* to happen, which is therefore currently > broken (actively or passively). But I’d want to add a warning here first > to see what creepy-crawlies we scare out of their hiding places, if any, > and then take it from there. I understand the desire to prevent breakage. There were improvements here made in 5.12, 5.14, and 5.16. This means that there weren't deprecation cycles here. However, as you say, we're not at 5.18, but much further ahead, meaning at this point people possibly already use this. This does require additional considerations. I'm wondering if we could make the change sooner to "unicode_strings" (as it purports to handle these) with no warning.Thread Previous | Thread Next