From: lord.thom@...
Date: 2015-02-23T15:53:04+00:00
Subject: [ruby-core:68263] [Ruby trunk - Bug #10891] /[[:punct:]]/ POSIX group broken (with string literals?)

Issue #10891 has been updated by Tom Lord.


Nobuyoshi Nakada wrote:
> It occurs with UTF-8 encoding only.

Ahhhhh, of course - *that's* what the difference between `60.chr` and `"<"` is!

Like you said, the issue only affects UTF-8 encodings:

    #<Encoding:UTF-8>, #<Encoding:UTF8-MAC>, #<Encoding:UTF8-DoCoMo>, #<Encoding:UTF8-KDDI>, #<Encoding:UTF8-SoftBank>

----------------------------------------
Bug #10891: /[[:punct:]]/ POSIX group broken (with string literals?)
https://bugs.ruby-lang.org/issues/10891#change-51617

* Author: Tom Lord
* Status: Open
* Priority: Normal
* Assignee: ruby-core
* ruby -v: ruby 2.2.0p0 (2014-12-25 revision 49005) [x86_64-linux]
* Backport: 2.0.0: UNKNOWN, 2.1: UNKNOWN, 2.2: UNKNOWN
----------------------------------------
The regular expression: `/[[:punct:]]/` should match the following characters:

    ! " # $ % & ' ( ) * + , - . / : ; < = > ? @ [ \ ] ^ _ ` { | } ~

However, it only works for these characters:

    ! " # % & ' ( ) * , - . / : ; ? @ [ \\ ] _ { }

And does not work for these characters:

    $ + < = > ^ ` | ~

However, this is where it gets really weird... Consider the following:

    60.chr == "<" # true
    60.chr =~ /[[:punct:]]/ # => 0
    "<" =~ /[[:punct:]]/ # => nil

So, it seems that the regular expression only fails for string literals!



-- 
https://bugs.ruby-lang.org/