ActionsLike0
Bug #20504
closedInterpolated string literal in regexp encoding handling
Description
There is some very odd behavior that I'm not sure is intentional or not, so I'm looking for guidance. In here:
# encoding: us-ascii
interp = "\x80"
regexp = /#{interp}/
the regexp
variable is a ascii-8bit regular expression with the byte interpolated into the middle. However, if you inline that interpolation:
# encoding: us-ascii
regexp = /#{"\x80"}/
you get a syntax error, saying it's an invalid multi-byte character. I'm not sure what the rule is here, as it seems inconsistent. Is this the correct behavior?
I would prefer if it would create an ascii-8bit regular expression like the first example, which would be consistent.
Updated by Eregon (Benoit Daloze) 11 months ago
- Tracker changed from Misc to Bug
- Backport set to 3.1: UNKNOWN, 3.2: UNKNOWN, 3.3: UNKNOWN
ActionsLike0