[ruby-core:43441] [ruby-trunk - Feature #4513][Assigned] allow whitespace following EOL continuation backslash

[ruby-core:43441] [ruby-trunk - Feature #4513][Assigned] allow whitespace following EOL continuation backslash

[nahi]

Issue #4513 has been updated by nahi.

Description updated
Category set to core
Status changed from Open to Assigned
Assignee set to nobu

Regardless it's acceptable or not, we want to check nobu's local patches first. Don't you have that?
----------------------------------------
Feature #4513: allow whitespace following EOL continuation backslash
https://bugs.ruby-lang.org/issues/4513#change-24909

Author: Rich_Morin
Status: Assigned
Priority: Normal
Assignee: nobu
Category: core
Target version: 


=begin
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?
=end



-- 
http://bugs.ruby-lang.org/

[ruby-core:49706] [ruby-trunk - Feature #4513] allow whitespace following EOL continuation backslash

[mame (Yusuke Endoh)]

Issue #4513 has been updated by mame (Yusuke Endoh).

Target version set to next minor


----------------------------------------
Feature #4513: allow whitespace following EOL continuation backslash
https://bugs.ruby-lang.org/issues/4513#change-33231

Author: Rich_Morin (Rich Morin)
Status: Assigned
Priority: Normal
Assignee: nobu (Nobuyoshi Nakada)
Category: core
Target version: next minor


=begin
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?
=end



-- 
http://bugs.ruby-lang.org/

[ruby-core:51137] [ruby-trunk - Feature #4513] allow whitespace following EOL continuation backslash

[nobu (Nobuyoshi Nakada)]

Issue #4513 has been updated by nobu (Nobuyoshi Nakada).

Priority changed from Normal to Low

It is easy to change, but I doubt if it is useful.
----------------------------------------
Feature #4513: allow whitespace following EOL continuation backslash
https://bugs.ruby-lang.org/issues/4513#change-35076

Author: Rich_Morin (Rich Morin)
Status: Assigned
Priority: Low
Assignee: nobu (Nobuyoshi Nakada)
Category: core
Target version: next minor


=begin
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?
=end



-- 
http://bugs.ruby-lang.org/

[ruby-core:85679] [Ruby trunk Feature#4513] allow whitespace following EOL continuation backslash

[nobu]

Issue #4513 has been updated by nobu (Nobuyoshi Nakada).

Description updated

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?

----------------------------------------
Feature #4513: allow whitespace following EOL continuation backslash
https://bugs.ruby-lang.org/issues/4513#change-70476

* Author: Rich_Morin (Rich Morin)
* Status: Assigned
* Priority: Normal
* Assignee: nobu (Nobuyoshi Nakada)
* Target version: 
----------------------------------------
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?





-- 
https://bugs.ruby-lang.org/

[ruby-core:86292] [Ruby trunk Feature#4513][Closed] allow whitespace following EOL continuation backslash

[nobu]

Issue #4513 has been updated by nobu (Nobuyoshi Nakada).

Status changed from Feedback to Closed

Now:

```
$ ruby -e ' \ '
-e:1: syntax error, unexpected escaped space
```

Close this for now.

----------------------------------------
Feature #4513: allow whitespace following EOL continuation backslash
https://bugs.ruby-lang.org/issues/4513#change-71208

* Author: Rich_Morin (Rich Morin)
* Status: Closed
* Priority: Normal
* Assignee: nobu (Nobuyoshi Nakada)
* Target version: 
----------------------------------------
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?





-- 
https://bugs.ruby-lang.org/