From: "Göran Weinholt" <goran@weinholt.se>
To: guile-devel@gnu.org
Subject: Re: [bug #31680] R6RS string literal intraline whitespace removal
Date: Tue, 08 Feb 2011 00:13:48 +0100 [thread overview]
Message-ID: <878vxrxwsz.fsf@industria.weinholt.se> (raw)
In-Reply-To: <20110121-082232.sv20118.64753@savannah.gnu.org> (Andy Wingo's message of "Fri, 21 Jan 2011 08:22:33 +0000")
[-- Attachment #1: Type: text/plain, Size: 1105 bytes --]
Andy Wingo <INVALID.NOREPLY@gnu.org> writes:
> Update of bug #31680 (project guile):
>
> Status: None => Fixed
> Open/Closed: Open => Closed
>
> _______________________________________________________
>
> Follow-up Comment #9:
>
> Fixed in git. You have to enable a reader option:
>
> (read-enable 'hungry-eol-escapes)
I'm wondering if it wouldn't make more sense to have these reader
options by associated with each port. Maybe I'm missing something, but
if one enables hungry-eol-escapes, wouldn't there be some problems when
reading files that assume hungry-eol-escapes is disabled?
A benefit of having the reader options kept on a port-by-port basis is
that the #!r6rs datum can enable whatever options are needed to properly
read R6RS code (r6rs-hex-escapes, hungry-eol-escapes, are there more?)
without interfering with non-R6RS code.
Regards,
--
Göran Weinholt <goran@weinholt.se>
"I AM LEARNING HANDSHAKES FROM AROUND THE WORLD!!!" -- POKEY THE PENGUIN
[-- Attachment #2: Type: application/pgp-signature, Size: 835 bytes --]
next parent reply other threads:[~2011-02-07 23:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20101117-131540.sv2373.30272@savannah.gnu.org>
[not found] ` <20101118-150512.sv73118.96725@savannah.gnu.org>
[not found] ` <20101118-185600.sv20118.39996@savannah.gnu.org>
[not found] ` <20101118-204517.sv2373.2325@savannah.gnu.org>
[not found] ` <20101118-202400.sv20118.12854@savannah.gnu.org>
[not found] ` <20101118-215151.sv73118.97070@savannah.gnu.org>
[not found] ` <20101119-152417.sv20118.80187@savannah.gnu.org>
[not found] ` <20101119-175733.sv73118.4023@savannah.gnu.org>
[not found] ` <20110121-073516.sv20118.98584@savannah.gnu.org>
[not found] ` <20110121-082232.sv20118.64753@savannah.gnu.org>
2011-02-07 23:13 ` Göran Weinholt [this message]
2011-02-08 19:35 ` [bug #31680] R6RS string literal intraline whitespace removal Andy Wingo
2011-02-08 21:24 ` Ludovic Courtès
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=878vxrxwsz.fsf@industria.weinholt.se \
--to=goran@weinholt.se \
--cc=guile-devel@gnu.org \
/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).