From: "andrykonchin (Andrew Konchin) via ruby-core" <ruby-core@ml.ruby-lang.org>
To: ruby-core@ml.ruby-lang.org
Cc: "andrykonchin (Andrew Konchin)" <noreply@ruby-lang.org>
Subject: [ruby-core:117408] [Ruby master Misc#20406] Question about Regexp encoding negotiation
Date: Tue, 02 Apr 2024 17:19:43 +0000 (UTC) [thread overview]
Message-ID: <redmine.issue-20406.20240402171943.13553@ruby-lang.org> (raw)
In-Reply-To: redmine.issue-20406.20240402171943.13553@ruby-lang.org
Issue #20406 has been reported by andrykonchin (Andrew Konchin).
----------------------------------------
Misc #20406: Question about Regexp encoding negotiation
https://bugs.ruby-lang.org/issues/20406
* Author: andrykonchin (Andrew Konchin)
* Status: Open
----------------------------------------
I am wondering what are the rules to calculate Regexp literal encoding in case an encoding modifier is specified.
1.
From the documentstion:
> By default, a regexp with only US-ASCII characters has US-ASCII encoding:
> ...
> A regular expression containing non-US-ASCII characters is assumed to use the source encoding. This can be overridden with one of the following modifiers.
> //n ...
> //u ...
> //e ...
> //s ...
Looking at the following examples I would assume that these rules are followed except one case:
```ruby
p /\xc2\xa1/e .encoding # EUC-JP
p /#{ }\xc2\xa1/e .encoding # EUC-JP
p /a/e .encoding # EUC-JP
p /a #{} a/e .encoding # EUC-JP
p /#{} a/e .encoding # US-ASCII
```
The last Regexp `/#{} a/e` is supposed to have `EUC-JP` encoding but has `US-ASCII`. So I am wondering what rule is applied in this case.
2.
In case of interpolated Regexp with encoding modifier I suppose there is no any encoding negotiation as far as if a Regexp fragment's encoding doesn't match a fixed encoding a SyntaxError is raised. Is this assumption correct?
```ruby
/#{ "фв" } a/e
# regexp encoding option 'e' differs from source encoding 'UTF-8' (SyntaxError)
```
--
https://bugs.ruby-lang.org/
______________________________________________
ruby-core mailing list -- ruby-core@ml.ruby-lang.org
To unsubscribe send an email to ruby-core-leave@ml.ruby-lang.org
ruby-core info -- https://ml.ruby-lang.org/mailman3/postorius/lists/ruby-core.ml.ruby-lang.org/
next parent reply other threads:[~2024-04-02 17:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-02 17:19 andrykonchin (Andrew Konchin) via ruby-core [this message]
2024-04-03 6:10 ` [ruby-core:117421] [Ruby master Misc#20406] Question about Regexp encoding negotiation shyouhei (Shyouhei Urabe) via ruby-core
2024-04-03 9:57 ` [ruby-core:117426] " Eregon (Benoit Daloze) via ruby-core
2024-04-03 10:29 ` [ruby-core:117427] " Eregon (Benoit Daloze) via ruby-core
2024-04-03 10:33 ` [ruby-core:117428] " Eregon (Benoit Daloze) via ruby-core
2024-04-04 0:09 ` [ruby-core:117437] " duerst via ruby-core
2024-04-04 11:35 ` [ruby-core:117441] " Eregon (Benoit Daloze) via ruby-core
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.ruby-lang.org/en/community/mailing-lists/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=redmine.issue-20406.20240402171943.13553@ruby-lang.org \
--to=ruby-core@ruby-lang.org \
--cc=noreply@ruby-lang.org \
--cc=ruby-core@ml.ruby-lang.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).