Mark H Weaver m...@netris.org writes:
Andreas Rottmann a.rottm...@gmx.at writes:
Mark H Weaver m...@netris.org writes:
Section 8.3 defines 'read' as follows:
Reads an external representation from textual-input-port and returns
the datum it represents. The read procedure operates in
Hello,
On Mon, Dec 17, 2012 at 2:05 PM, Andreas Rottmann a.rottm...@gmx.at wrote:
I think this is my assumption that you seem to disagree on: by using the
binding of `read' from `(rnrs io simple)', instead of the one provided
by Guile's core, the writer of the code using that binding has
Andreas Rottmann a.rottm...@gmx.at writes:
Mark H Weaver m...@netris.org writes:
Section 8.3 defines 'read' as follows:
Reads an external representation from textual-input-port and returns
the datum it represents. The read procedure operates in the same way
as get-datum, see section
Mark H Weaver m...@netris.org writes:
Hi Andreas,
Andreas Rottmann a.rottm...@gmx.at writes:
Mark H Weaver m...@netris.org writes:
Andreas Rottmann a.rottm...@gmx.at writes:
This patch series addresses the problem that `get-datum' is using the
global reader options, even for those options
Mark H Weaver m...@netris.org writes:
Hi Andreas,
Andreas Rottmann a.rottm...@gmx.at writes:
This patch series addresses the problem that `get-datum' is using the
global reader options, even for those options that have to have fixed
values to make the reader behave in an R6RS-compatible
Hi Andreas,
Andreas Rottmann a.rottm...@gmx.at writes:
Mark H Weaver m...@netris.org writes:
Andreas Rottmann a.rottm...@gmx.at writes:
This patch series addresses the problem that `get-datum' is using the
global reader options, even for those options that have to have fixed
values to make
Hi Andreas,
Andreas Rottmann a.rottm...@gmx.at writes:
This patch series addresses the problem that `get-datum' is using the
global reader options, even for those options that have to have fixed
values to make the reader behave in an R6RS-compatible way.
I'm sorry to have not done so earlier,
