From: shyouhei@...
Date: 2018-01-17T10:28:17+00:00
Subject: [ruby-core:84905] [Ruby trunk Bug#14367] Wrong interpretation of backslash C in regexp literals

Issue #14367 has been updated by shyouhei (Shyouhei Urabe).


Hanmac (Hans Mackowiak) wrote:
> the problem is this:
> 
> ~~~ ruby
> /\c\xFF/.source == "\\c\\xFF"
> ~~~

No, I believe that isn't the problem.  For instance /\c\x7F/ works.

```sh
% LC_ALL=C ruby -ve 'p(/\c\x7F/ =~ "\c\x7F")'
ruby 2.0.0p648 (2015-12-16 revision 53162) [universal.x86_64-darwin15]
0
```

> EDIT: this works
> 
> ~~~ ruby
> /\x9F/ =~ "\c\xFF" #=> 0
> ~~~

Yeah, that's why I titled this issue a "wrong interpretation of backslash C in regexp literals".  This is about `/...\c.../`.

----------------------------------------
Bug #14367: Wrong interpretation of backslash C in regexp literals
https://bugs.ruby-lang.org/issues/14367#change-69610

* Author: shyouhei (Shyouhei Urabe)
* Status: Open
* Priority: Normal
* Assignee: 
* Target version: 
* ruby -v: ruby 2.6.0dev (2018-01-16 trunk 61875) [x86_64-darwin15]
* Backport: 2.3: UNKNOWN, 2.4: UNKNOWN, 2.5: UNKNOWN
----------------------------------------
Following ruby code returns nil.

```sh
% LC_ALL=C ruby -ve 'p(/\c\xFF/ =~ "\c\xFF")'
ruby 2.6.0dev (2018-01-16 trunk 61875) [x86_64-darwin15]
nil
```

Is this intentional?



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

Unsubscribe: <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>