'Unicode::Collate' is core, so it could be used a lot in the future, as it should be. But a lot of production environments will be affected if they don't know in advance that the code points of ASCII have been redefined.
A text sort looks nothing at all like a code point sort. You seem to think that 7 bit code points should not sort as a text. That completely defaults the whole purpose.

Watch here to see what really happens: 

$ perl -MUnicode::Collate -E 'for (Unicode::Collate->new->sort(map { c
+hr } 0..127)) { say "chr ", ord, "\t",  /\p{graph}/ ? $_ : "(unprinta
+ble)" }'
chr 0   (unprintable)
chr 1   (unprintable)
chr 2   (unprintable)
chr 3   (unprintable)
chr 4   (unprintable)
chr 5   (unprintable)
chr 6   (unprintable)
chr 7   (unprintable)
chr 8   (unprintable)
chr 14  (unprintable)
chr 15  (unprintable)
chr 16  (unprintable)
chr 17  (unprintable)
chr 18  (unprintable)
chr 19  (unprintable)
chr 20  (unprintable)
chr 21  (unprintable)
chr 22  (unprintable)
chr 23  (unprintable)
chr 24  (unprintable)
chr 25  (unprintable)
chr 26  (unprintable)
chr 27  (unprintable)
chr 28  (unprintable)
chr 29  (unprintable)
chr 30  (unprintable)
chr 31  (unprintable)
chr 127 (unprintable)
chr 9   (unprintable)
chr 10  (unprintable)
chr 11  (unprintable)
chr 12  (unprintable)
chr 13  (unprintable)
chr 32  (unprintable)
chr 96  `
chr 94  ^
chr 95  _
chr 45  -
chr 44  ,
chr 59  ;
chr 58  :
chr 33  !
chr 63  ?
chr 46  .
chr 39  '
chr 34  "
chr 40  (
chr 41  )
chr 91  [
chr 93  ]
chr 123 {
chr 125 }
chr 64  @
chr 42  *
chr 47  /
chr 92  \
chr 38  &
chr 35  #
chr 37  %
chr 43  +
chr 60  <
chr 61  =
chr 62  >
chr 124 |
chr 126 ~
chr 36  $
chr 48  0
chr 49  1
chr 50  2
chr 51  3
chr 52  4
chr 53  5
chr 54  6
chr 55  7
chr 56  8
chr 57  9
chr 97  a
chr 65  A
chr 98  b
chr 66  B
chr 99  c
chr 67  C
chr 100 d
chr 68  D
chr 101 e
chr 69  E
chr 102 f
chr 70  F
chr 103 g
chr 71  G
chr 104 h
chr 72  H
chr 105 i
chr 73  I
chr 106 j
chr 74  J
chr 107 k
chr 75  K
chr 108 l
chr 76  L
chr 109 m
chr 77  M
chr 110 n
chr 78  N
chr 111 o
chr 79  O
chr 112 p
chr 80  P
chr 113 q
chr 81  Q
chr 114 r
chr 82  R
chr 115 s
chr 83  S
chr 116 t
chr 84  T
chr 117 u
chr 85  U
chr 118 v
chr 86  V
chr 119 w
chr 87  W
chr 120 x
chr 88  X
chr 121 y
chr 89  Y
chr 122 z
chr 90  Z

[download]
See? A text sort looks nothing whatsoever like a code point sort. If you expect the UCA to do a code-point sort on 7-bit code points but a text sort on everything else, I fear that you have gravely misunderstood its purpose and consequences.

So what may I do to help you understand this better? I would seriously like to know. chr 40 ( chr 41 ) chr 91

In reply to Re^5: RFC: Is this the correct use of Unicode::Collate? by tchrist
in thread RFC: Is this the correct use of Unicode::Collate? by flexvault

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.