wrongly used the regular expression pattern to match any code point, not any character.
Only if you're using the newly broken 5.14 semantics. I'm not.
And anyone who is (should) know they are and take the appropriate action.
I won't be any time soon. Eventually someone will fix this mess, and there's no point in learning something you're only going to have to unlearn again once people realise how stupid it is.
Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.
| [reply] |
Huh? What are you talking about?
The regular expression pattern to match Unicode graphemes was introduced many years ago in Perl 5.8. What "newly broken 5.14 semantics" are you referring to? And how are they relevant to this discussion?
By the way, I'm running Perl 5.8.8 and Perl 5.12.3. I haven't upgraded to Perl 5.14 yet.
| [reply] |
Huh? What are you talking about?
Since this is, to my memory, the first time anyone has suggested what you are suggesting is possible, I assumed that you had to be talking about the new 5.14 regex modifiers: a, d, l and u These modifiers, new in 5.14, affect which character-set semantics (Unicode, ASCII, etc.) are used, as described below in Character set modifiers."
Of course, if you would demonstrate rather than allude, it wouldn't be necessary for all us lesser beings to guess what you are alluding to with your pronouncements from on high.
Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.
| [reply] |