Hi Julian,
Thanks for the nice R6RS doc! Looks to me like it’s both a good
tutorial and a convenient reference.
Some nitpicking:
"Julian Graham" <julian.gra...@aya.yale.edu> writes:
> +have the option to create modules using the portable ``library'' form
Should be @code{library}.
> +libraries created in this format by other programmers. Guile's R6RS
> +libraries implementation takes advantage of the flexibility built
“library implementation” rather?
> +into the module system by expanding the R6RS library form into a
> +corresponding Guile ``define-module'' form that specifies equivalent
@code{define-module}
> +Central to the mechanics of R6RS libraries is the concept of import
> +and export ``levels,'' which control the visibility of bindings at
@dfn{levels}
> +Guile's libraries implementation uses a technique called ``implicit
@dfn{implicit phasing}
> +phasing'' (see @cite{Implicit Phasing for R6RS Libraries} by
> +Abdulaziz Ghuloum and R. Kent Dybvig), which allows the expander and
This is a non-free document (ACM...) so I think we should not refer to
it. Perhaps instead this could read along the lines of:
... a technique called @dfn{implicit phasing} (first described by
Abdulaziz Ghuloum and R. Kent Dybvig) ...
Thoughts?
> +Each @var{import-spec} must be either an ``import set'' (see below)
@dfn{import set}
> +...@deffn syntax import import-spec ...
I’d rather use �...@deffn {Scheme Syntax}’ or �...@deffn {Syntax}’ but other
forms are also found in the manual.
Thanks,
Ludo’.
