From: merch-redmine@... Date: 2021-05-13T03:51:54+00:00 Subject: [ruby-core:103815] [Ruby master Bug#14367] Wrong interpretation of backslash C in regexp literals Issue #14367 has been updated by jeremyevans0 (Jeremy Evans). nobu (Nobuyoshi Nakada) wrote in #note-7: > Agree that the previous behavior might not be intentional, but commit:11ae581a4a7f5d5f5ec6378872eab8f25381b1b9 also seems something broken on other than US-ASCII encoding. > > ``` > $ LANG=en_US.UTF-8 ./ruby -vce '/\c\xFF/' > ruby 3.1.0dev (2021-05-13T01:55:43Z master 11ae581a4a) [x86_64-darwin19] > -e:1: invalid multibyte escape: /\x9F/ > -e:1: warning: possibly useless use of a literal in void context > ``` The previous behavior also ended up with a regexp which matches a 8-bit character, so maybe Ruby should have given the same error before? Alternatively, I can revert if that is better? ---------------------------------------- Bug #14367: Wrong interpretation of backslash C in regexp literals https://bugs.ruby-lang.org/issues/14367#change-91932 * Author: shyouhei (Shyouhei Urabe) * Status: Closed * Priority: Normal * 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: