Feature #4513
closed
allow whitespace following EOL continuation backslash
Added by Rich_Morin (Rich Morin) about 13 years ago.
Updated about 6 years ago.
Description
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?
- 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?
- Target version set to 2.6
- Priority changed from Normal to 3
It is easy to change, but I doubt if it is useful.
- Target version deleted (
2.6)
- Description updated (diff)
Warning for a backslash followed by spaces is:
Old:
$ ruby2.5 -e ' \ '
-e:1: syntax error, unexpected $undefined
Now:
$ ruby -e ' \ '
-e:1: syntax error, unexpected backslash
Does this help you?
- Status changed from Assigned to Feedback
- Related to Bug #14597: Ripper Issue - introduced between 62674 & 62681 added
- Status changed from Feedback to Closed
Now:
$ ruby -e ' \ '
-e:1: syntax error, unexpected escaped space
Close this for now.
- Description updated (diff)
Also available in: Atom
PDF
Like0
Like0Like0Like0Like0Like0Like0Like0Like0Like0