Subject: R6RS `library' form must have exports before imports

From: Taylan Ulrich Bayirli/Kammer <[email-masked]>
Date: Thu, 15 May 2014 23:02:25 +0200

The R6RS `library' form requires the (export ...) list to appear
before the (import ...) list.  I'm not sure if this itself is a bug;
R6RS consistently uses that order, doesn't mention the order to be
irrelevant, and seems to me to imply that it's indeed mandatory.  I
didn't check for what other R6RS implementations do though.

Here's a corresponding documentation patch against master/3be43fb:

>From 7900da779f1ab267481ad1a08a0547083936d11f Mon Sep 17 00:00:00 2001
From: Taylan Ulrich B <[email-masked]>
Date: Thu, 15 May 2014 22:55:40 +0200
Subject: [PATCH] R6RS library documentation fix

* doc/ref/api-modules.texi: In the R6RS `library' form, exports must
  appear before imports.
---
 doc/ref/api-modules.texi | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/doc/ref/api-modules.texi b/doc/ref/api-modules.texi
index 286a37d..47171c6 100644
--- a/doc/ref/api-modules.texi
+++ b/doc/ref/api-modules.texi
@@ -584,8 +584,8 @@ expression:
 
 @lisp
   (library (mylib (1 2))
-    (import (otherlib (3)))
-    (export mybinding))
+    (export mybinding)
+    (import (otherlib (3))))
 @end lisp
 
 is equivalent to the module definition:
@@ -597,6 +597,8 @@ is equivalent to the module definition:
     #:export (mybinding))
 @end lisp
 
+Note that exports must appear before imports in the `library' form.
+
 Central to the mechanics of R6RS libraries is the concept of import
 and export @dfn{levels}, which control the visibility of bindings at
 various phases of a library's lifecycle --- macros necessary to 
-- 
1.8.4