[R6RS] library.tex edits

Matthew Flatt mflatt at cs.utah.edu
Tue Sep 5 22:33:08 EDT 2006

At Tue, 05 Sep 2006 22:01:39 -0400, dyb at cs.indiana.edu wrote:
> I've committed a new version of library.tex that eliminates the export
> "for" syntax and specifies how export phases are determined.  I've
> also added text to library.tex specifying the default export phases
> of bindings exported from standard libraries, and added a note to
> complib.tex mentioning that it exports all of its bindings for both
> run and expand.
> Matthew, since I'm getting this to you so late, I'll give you until
> 11:00pm EDT (an hour from now) to commit any fixes to my changes.

I had trouble getting through the rationale on the composite library,
so I modified that part (and there's one other small edit). Otherwise,
it looks good to me.



 The export phase of an exported binding is {\cf run} for all bindings
-defined within the exporting library, and the export phases of a
+that are defined within the exporting library. The export phases of a
 reexported binding, i.e., an export imported from another library, are the
 same as the effective import phases of that binding within the reexporting
@@ -371,10 +371,10 @@
 and {\cf expand}.
-The {\cf r6rs} library is intended as a convenience when finer control
-over the precise set of visible standard bindings and their phases is not
-required, and it is most convenient for the purposes of writing macros for
-its bindings to be exported for {\cf expand} as well as for {\cf run}.
+The {\cf r6rs} library is intended as a convenient import for libraries where fine
+control over imported bindings is not necessary or desirable. The {\cf r6rs} module
+exports all bindings for {\cf expand} as well as {\cf run} so that it is convenient
+for writing macros as well as run-time code.
 The effective import phases implicitly determine when information about a

More information about the R6RS mailing list