Re^2: Regarding the new \w regexp escape in 5.11

If we're going to make this change (which appears to be compatible with other Unicode-handling modern regexen such as Python and PCRE), we should at least provide a way out for the user who wants true Unicode support without having to jump through lots of hoops. Python, for example, does this with (?u). Since Perl 5 uses (?letter) to map to the modifier letters, it seems obvious to make this a modifier :u, which should probably be turned on by default with "use locale".

Doing that gives the expected behavior for POSIX-friendly uses and yet avoids snubbing users of P5 regexes who routinely match text from other languages/regions.

naïveté (n) - Assuming your experiences map cleanly to the set of all experiences....

Comment on Re^2: Regarding the new \w regexp escape in 5.11

Replies are listed 'Best First'.
Re^3: Regarding the new \w regexp escape in 5.11 by demerphq (Chancellor) on Oct 06, 2009 at 09:54 UTC
Im wondering if you somehow dropped a "not" in your first parenthetical remark. The fundamental problem here is that \w and behaves different if the string is utf8 or not. We want to make it so \w does the same thing regardless. That means that we end up breaking someones code. I really dont want to have to support three modes, one for the current broken behaviour, one for utf8 and one for ascii. I would much rather just support one mode, and have it be able to cover all the bases. Whether this is feasable or not going forward isnt clear. Feel free to provide more details on how these issues are tackled in other languages. --- $world=~s/war/peace/g	[reply]

Replies are listed 'Best First'.

Re^3: Regarding the new \w regexp escape in 5.11
by demerphq (Chancellor) on Oct 06, 2009 at 09:54 UTC

Im wondering if you somehow dropped a "not" in your first parenthetical remark.

The fundamental problem here is that \w and behaves different if the string is utf8 or not. We want to make it so \w does the same thing regardless. That means that we end up breaking someones code. I really dont want to have to support three modes, one for the current broken behaviour, one for utf8 and one for ascii. I would much rather just support one mode, and have it be able to cover all the bases. Whether this is feasable or not going forward isnt clear.

Feel free to provide more details on how these issues are tackled in other languages.

---
$world=~s/war/peace/g

[reply]