From: Mike Gran <INVALID.NOREPLY@gnu.org>
To: "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 15:05:13 +0000 [thread overview]
Message-ID: <20101118-150512.sv73118.96725@savannah.gnu.org> (raw)
In-Reply-To: <20101117-131540.sv2373.30272@savannah.gnu.org>
Follow-up Comment #1, bug #31680 (project guile):
Yeah it is true that this isn't implemented and should be.
Ludo, Andy, I did in fact write an implementation of this in r6rs-strings
tree, but, I never committed it to master.
The commit was cff6adf899dbc0336c7c017d52504f8138c89b3d and the part of the
commit specific to this bug is all in read.c in scm_read_string and
SCM_READ_SPACE_LINE_SPACE
I didn't commit it because, at the time, I took exception with the r6rs spec
itself.
It states that <intraline-whitespace><line-ending><intraline-whitespace>
expands to nothing. And then it calls out that whitespace and line-ending are
any characters in the Unicode whitespace and line ending families!
I guarantee that no one will ever put something like <U+005d "backslash">
<U+205F "medium mathematical space"> <U+2028 "line separator"> <U+2006 "6 per
em space"> in the middle of a source code file. It will never, ever happen.
But writing the code to allow for all those cases lead to an ugly patch.
_______________________________________________________
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 15:05 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 [this message]
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
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-150512.sv73118.96725@savannah.gnu.org \
--to=invalid.noreply@gnu.org \
--cc=bug-guile@gnu.org \
--cc=goran@weinholt.se \
--cc=spk121@yahoo.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).