1.8 char const + \u esc seq should be invalid syntax

[cremno]

$ ruby-parse --18 -e "?\u267F"
(int 226)

$ ruby -e "?\u267F"
-e:1: syntax error, unexpected tINTEGER, expecting $end

[whitequark]

Do not expect me to fix this.

[cremno]

Somewhat related because 1.8 doesn't support \u at all: "\u0041" should be equal to "u0041", not "A". Should I submit a new issue? Rename this one?

[whitequark]

That's a documented incompatibility. I've looked at it and deemed it unworthy of fixing because of miniscule impact and severe changes required to lexer.

[whitequark]

FWIW I think this should be added to README and then closed, too.

[mbj]

1.8 is not supported anymore, I suggest we close this issue for that reason.

[whitequark]

Huh? When did that happen?

[mbj]

@whitequark I saw #747 which is the reason I made that statement.

Now I realize that there is a difference between: Versions parser supports and runtime parser gets executed on. I suspect that there is only evidence for the runtime support, not the syntax support.

Please disregard my comment.