allow whitespace following EOL continuation backslash
In a few programming languages, the displayed or printed program can hide
critical syntactic and/or semantic information. For example, in make(1)
and Python, the difference between initial tabs and spaces can cause bugs
that are not visually apparent.
Ruby has a minor instance of this problem, in that spaces or tabs
between a backslash and the EOL will prevent the line from being continued:
>> a \ ?> = 2 => 2 >> b \ SyntaxError: compile error (irb):3: syntax error, unexpected $undefined, expecting $end from (irb):3
Could Ruby open up its syntax to allow any number of intervening spaces or tabs before the EOL?
parse.y: named backslash
- parse.y: named backslash to show unexpected character.
parse.y: named whitespaces
- parse.y: named escaped whitespaces to show unexpected character. bare whitespaces should not appear outside of word_list.
parse.y: tSPACE for old bison
- parse.y (tSPACE): define a separate token for escaped space, to
redefining user token number of ' 'error at word list separator on bison 2.
Updated by nahi (Hiroshi Nakamura) almost 7 years ago
- Description updated (diff)
- Category set to core
- Status changed from Open to Assigned
- Assignee set to nobu (Nobuyoshi Nakada)
Regardless it's acceptable or not, we want to check nobu's local patches first. Don't you have that?