From: nahi <nakahiro@...>
Date: 2012-03-18T19:13:17+09:00
Subject: [ruby-core:43441] [ruby-trunk - Feature #4513][Assigned] allow whitespace following EOL continuation backslash


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/