Hi Chris,
I'm terribly sorry for the long delay on this. For better or worse,
I've become extremely concerned about computer security, and so I feel a
heavy responsibility to be extra careful about code that is expected to
parse hostile data.
I was also looking for a cleaner way to express this
I wrote:
> I was also looking for a cleaner way to express this parser, and to add
> better error reporting, while allowing flexibility for users to
> customize the Scheme representation.
I forgot to mention that another goal was to minimize heap allocations,
e.g. eliminating the allocation of in
I wrote:
> and real numbers cannot simply be printed using 'display' because of
> infinities and NaNs.
... and exact rationals.
Mark
Hi Freja,
Freja Nordsiek writes:
> Was fiddling around with using Chibi's R7RS test-suite in Guile and
> found a major R7RS syntax feature currently missing from Guile. The
> feature is R7RS bytevector notation, which uses the #u8 prefix like
> SRFI-4 unsigned 8-bit integer vectors instead of the
Freja Nordsiek writes:
> Was fiddling around with using Chibi's R7RS test-suite in Guile and
> found a major R7RS syntax feature currently missing from Guile. The
> feature is R7RS bytevector notation, which uses the #u8 prefix like
> SRFI-4 unsigned 8-bit integer vectors instead of the R6RS pref
Hi Alex and John,
I believe I've found a few mistakes in the formal denotational semantics
for R7RS-small. The scheme-reports mailing list seems to be gone, so
I'm not sure where to send this.
First, if I understand correctly, the 'pathup' and 'pathdown' auxiliary
functions associate the wrong d
Mark,
I saw the stuff in the bytevectors code where the SRFI-4 u8 vectors and
bytevectors are essentially the same but with different flavors. The reader
option was to make #u8 make bytectors that are exactly the same as #vu8.
Merging the two types solves the reading problem completely since i
