"Dr. Arne Babenhauserheide" <[email protected]> writes: > Hi, > > In the intro the view on R7RS was a bit more pessimistic than warranted > given the recent progress of R7RS-large, so I’d suggest adjusting the > wording (see the patch). > > Best wishes, > Arne > > From 1b8ef87953ade599952df6b0bd68a7cd32014466 Mon Sep 17 00:00:00 2001 > From: Arne Babenhauserheide <[email protected]> > Date: Sat, 26 Sep 2026 11:03:54 +0200 > Subject: [PATCH] doc: mention the existing progress in R7RS. > > * doc/ref/intro.texi (Guile and Scheme): reword paragraph > --- > doc/ref/intro.texi | 12 ++++++------ > 1 file changed, 6 insertions(+), 6 deletions(-) > > diff --git a/doc/ref/intro.texi b/doc/ref/intro.texi > index a9d017b66..517afb239 100644 > --- a/doc/ref/intro.texi > +++ b/doc/ref/intro.texi > @@ -99,12 +99,12 @@ taking control of the official Scheme standardization > track and in 2013 > released a more limited R7RS, essentially consisting of R5RS, plus a > module system. Guile supports R7RS also. @xref{R7RS Support}. > > -With R6RS and R7RS, the unified Scheme standardization process appears > -to have more or less run its course. There will continue to be more > -code written in terms of both systems, and modules defined using the > -SRFI process, and Guile will support both. However for future > -directions, Guile takes inspiration from other related language > -communities: Racket, Clojure, Concurrent ML, and so on. > +While R7RS yielded a unified Scheme standard, named r7rs-small, work is > +underway to support a wider scope of programs with r7rs-large. There > +will continue to be more code written in terms of both systems, and
I think in the new text the "both systems" reads as "r7rs-small and r7rs-large", with no mention of r6rs. Is that intentional? > +modules defined using the SRFI process, and Guile will support both. > +However for future directions, Guile also takes inspiration from other > +related language communities: Racket, Clojure, Concurrent ML, and so on. > > In summary, Guile supports writing and running code written to the R5RS, > R6RS, and R7RS Scheme standards, and also supports a number of SRFI -- There are only two hard things in Computer Science: cache invalidation, naming things and off-by-one errors.
