Front page | perl.perl5.porters |
Postings from May 2011
On 05/01/2011 07:50 PM, Tom Christiansen wrote: > Karl came up with this list of possible directions: > > 1) Ship 5.14 as-is > 2) Exclude just the ß=>ss multi-char fold in character classes in > some manner: > 2a) Exclude ß in just an inverted class. > 2b) Exclude ß in just an inverted class unless there is an > explicit code point above 255. > 2c) Exclude ß in any class unless there is a code point > above 255. > 2d) Exclude ß in any class always. > 3) Exclude all multi-char folds in classes in some manner > 3a) in just inverted classes > 3b) in all classes > 3c) in all classes except those that optimize to EXACTF nodes > 4) Use simple folding in classes and non-classes unless specify > new pragma 'use re qw(folding full)' > 5) Change regex default to /aa > > Summary of a long conversation: > > We don't need to have the same long-term goals as short-term ones. > > We cannot know how, when, or even whether The Unicode Consortium > is going to change their minds about UTS#18, so that cannot be > a factor in any short-term measure I disagree here. It has been my impression that Unicode will not admit error if they can possibly avoid it. That they are even contemplating this is significant, and so is valid for us to take into consideration. > Perhaps it would be possible or desirable to emit some sort of warning, and > if so, when. Maybe that could accompany some of the hairier choices above. > That would directly address the problem of things silently behaving > differently, weirdly, or unexpectedly. That might make more of the > possible short-term measures above more acceptable, even option 1. I think you must mean, not option 1 which is to make absolutely no changes, but a new option 6) which adds a warning instead of the other things that have been discussed.Thread Previous | Thread Next