The behaviour has now changed to something different but also wrong:
> ":4\x[308]a".EVAL
a => 0
It should yield either a syntax error or the same thing as ":4a".
Given that "4\x[308]" is not being accepted as a digit in term context
or in Str.Int coercion, it should presumably yield a syntax erro
# New Ticket Created by Zefram
# Please include the string: [perl #128551]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=128551 >
> ":4\x[308]a".EVAL
Error encoding ASCII string: could not encode codepoint 776
It seems corre
