develooper Front page | perl.perl5.porters | Postings from October 2016

Re: Does the range operator still have the Unicode Bug?

Thread Previous | Thread Next
Aristotle Pagaltzis
October 30, 2016 18:11
Re: Does the range operator still have the Unicode Bug?
Message ID:
* Sawyer X <> [2016-10-30 12:36]:
> 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.

I don’t understand what that solves. The `unicode_string` feature gets
enabled by `use 5.012`, meaning lots of code would get the change with
no grace period of any kind. This falls under “do we want people to be
able to upgrade their perl without fear of breakage?”

If you want a repeat of the 5.12 strategy, you would have to add a new
feature for this change.

But using the feature mechanism in any way for this would mean having to
preserve both code paths going forward: it makes the codebase worse, not

I would prefer to see this just fixed, for everyone, with cleaner code.
And it’s very *likely* that that can be done… just not *known*. A cycle
or two with warnings would give us data to calibrate the guess.

Aristotle Pagaltzis // <>

Thread Previous | Thread Next Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at | Group listing | About