It seems like you can pass multiple encoding flags to regular expression literals, but I think this should be a warning or possibly syntax error.
For example:
x=/foo/nupx.encoding
n says the RE should be ASCII-8BIT, and u says it should be UTF-8. The last flag wins, so in this case the regular expression gets UTF-8 encoding. However, I think it should be a warning or even a syntax error if you specify multiple encoding options on a regular expression. It seems like a mistake if programmers specify multiple.
I think it's a good idea, but am curious as to what (if any) led you to want to prohibit this.
Did you get in trouble because of this? Or did you just notice it (while implementing Prism or something)?
I think it's a good idea, but am curious as to what (if any) led you to want to prohibit this.
Did you get in trouble because of this? Or did you just notice it (while implementing Prism or something)?
No, it didn't cause any trouble. @eileencodes (Eileen Uchitelle) and I just noticed this while implementing regular expression support with Prism.