* Re: [bug #31680] R6RS string literal intraline whitespace removal
[not found] ` <20110121-082232.sv20118.64753@savannah.gnu.org>
@ 2011-02-07 23:13 ` Göran Weinholt
2011-02-08 19:35 ` Andy Wingo
0 siblings, 1 reply; 3+ messages in thread
From: Göran Weinholt @ 2011-02-07 23:13 UTC (permalink / raw)
To: guile-devel
[-- 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 --]
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [bug #31680] R6RS string literal intraline whitespace removal
2011-02-07 23:13 ` [bug #31680] R6RS string literal intraline whitespace removal Göran Weinholt
@ 2011-02-08 19:35 ` Andy Wingo
2011-02-08 21:24 ` Ludovic Courtès
0 siblings, 1 reply; 3+ messages in thread
From: Andy Wingo @ 2011-02-08 19:35 UTC (permalink / raw)
To: Göran Weinholt; +Cc: guile-devel
On Tue 08 Feb 2011 00:13, Göran Weinholt <goran@weinholt.se> writes:
> I'm wondering if it wouldn't make more sense to have these reader
> options by associated with each port.
Probably, yes. Would be a larger refactor, though.
> if one enables hungry-eol-escapes, wouldn't there be some problems when
> reading files that assume hungry-eol-escapes is disabled?
Yes, though there are no files like that within Guile itself. If you
want it in your code, you can safely turn it on globally. Not a perfect
solution, but oh well.
Cheers,
Andy
--
http://wingolog.org/
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [bug #31680] R6RS string literal intraline whitespace removal
2011-02-08 19:35 ` Andy Wingo
@ 2011-02-08 21:24 ` Ludovic Courtès
0 siblings, 0 replies; 3+ messages in thread
From: Ludovic Courtès @ 2011-02-08 21:24 UTC (permalink / raw)
To: guile-devel
Hello,
Andy Wingo <wingo@pobox.com> writes:
> On Tue 08 Feb 2011 00:13, Göran Weinholt <goran@weinholt.se> writes:
>
>> I'm wondering if it wouldn't make more sense to have these reader
>> options by associated with each port.
>
> Probably, yes. Would be a larger refactor, though.
I think ports and reader syntax are orthogonal.
Instead I’m in favor of multiple ‘read’ procedures and using the
‘current-reader’ fluid to make sure the current reader is inherited.
Thanks,
Ludo’.
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2011-02-08 21:24 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[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 ` [bug #31680] R6RS string literal intraline whitespace removal Göran Weinholt
2011-02-08 19:35 ` Andy Wingo
2011-02-08 21:24 ` Ludovic Courtès
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).