[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[bug #31680] R6RS string literal intraline whitespace removal
|
From: |
Mike Gran |
|
Subject: |
[bug #31680] R6RS string literal intraline whitespace removal |
|
Date: |
Thu, 18 Nov 2010 21:51:51 +0000 |
|
User-agent: |
Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 5.1; Trident/4.0; .NET CLR 2.0.50727; .NET CLR 3.0.04506.30; .NET CLR 3.0.04506.648; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729; .NET CLR 1.1.4322; .NET4.0C; .NET4.0E) |
Follow-up Comment #5, bug #31680 (project guile):
> I think the deal is that all (?) of the other escapes can be
> dealt with via the equivalent of a `case' expression. This
> one requires a property lookup. It's not as nice.
> Also note the thread at
> http://lists.r6rs.org/pipermail/r6rs-discuss/2010-November/006146.html.
> Is there a use case for allowing intraline spaces before
> the newline? Disallowing that would eliminate a state
> in the parser.
I don't think there is a valid use case for allowing that
initial intraline space. If (according to the discussion
in the R6RS list) the intention was to work around broken
editors, those bugs should be fixed with the editors, and
not become workarounds enshrined in a language spec.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?31680>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/