unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: Taylan Ulrich Bayirli/Kammer <taylanbayirli@gmail.com>
To: 17502@debbugs.gnu.org
Subject: bug#17502: R6RS `library' form must have exports before imports
Date: Thu, 15 May 2014 23:02:25 +0200	[thread overview]
Message-ID: <8738ga7o2m.fsf@taylan.uni.cx> (raw)

[-- Attachment #1: Type: text/plain, Size: 398 bytes --]

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:


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: 0001-R6RS-library-documentation-fix.patch --]
[-- Type: text/x-diff, Size: 1164 bytes --]

From 7900da779f1ab267481ad1a08a0547083936d11f Mon Sep 17 00:00:00 2001
From: Taylan Ulrich B <taylanbayirli@gmail.com>
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


             reply	other threads:[~2014-05-15 21:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-15 21:02 Taylan Ulrich Bayirli/Kammer [this message]
2014-05-16  3:12 ` bug#17502: R6RS `library' form must have exports before imports dsmich
2014-06-05  1:24 ` Mark H Weaver
2014-06-05 17:31   ` Taylan Ulrich Bayirli/Kammer
2014-06-06 20:39     ` Mark H Weaver

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8738ga7o2m.fsf@taylan.uni.cx \
    --to=taylanbayirli@gmail.com \
    --cc=17502@debbugs.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).