From: Mike Gran <INVALID.NOREPLY@gnu.org>
To: "Andy Wingo" <wingo@pobox.com>,
"Göran Weinholt" <goran@weinholt.se>,
"Mike Gran" <spk121@yahoo.com>,
bug-guile@gnu.org
Subject: [bug #31680] R6RS string literal intraline whitespace removal
Date: Thu, 18 Nov 2010 21:51:51 +0000 [thread overview]
Message-ID: <20101118-215151.sv73118.97070@savannah.gnu.org> (raw)
In-Reply-To: <20101118-202400.sv20118.12854@savannah.gnu.org>
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/
next prev parent reply other threads:[~2010-11-18 21:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-17 12:15 [bug #31680] R6RS string literal intraline whitespace removal Göran Weinholt
2010-11-18 15:05 ` Mike Gran
2010-11-18 18:56 ` Andy Wingo
2010-11-18 19:45 ` Göran Weinholt
2010-11-18 20:24 ` Andy Wingo
2010-11-18 21:51 ` Mike Gran [this message]
2010-11-19 15:24 ` Andy Wingo
2010-11-19 17:57 ` Mike Gran
2011-01-21 7:35 ` Andy Wingo
2011-01-21 8:22 ` Andy Wingo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20101118-215151.sv73118.97070@savannah.gnu.org \
--to=invalid.noreply@gnu.org \
--cc=bug-guile@gnu.org \
--cc=goran@weinholt.se \
--cc=spk121@yahoo.com \
--cc=wingo@pobox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).