From: Taylan Ulrich Bayirli/Kammer <taylanbayirli@gmail.com>
To: Mark H Weaver <mhw@netris.org>
Cc: 17502@debbugs.gnu.org
Subject: bug#17502: R6RS `library' form must have exports before imports
Date: Thu, 05 Jun 2014 19:31:47 +0200 [thread overview]
Message-ID: <878upbp8jg.fsf@taylan.uni.cx> (raw)
In-Reply-To: <87d2eotagj.fsf@yeeloong.lan> (Mark H. Weaver's message of "Wed, 04 Jun 2014 21:24:28 -0400")
[-- Attachment #1: Type: text/plain, Size: 93 bytes --]
Hi Mark, thanks for the comments. :-)
Here the improved patch, against stable-2.0/73ff8e3:
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: R6RS library documentation patch --]
[-- Type: text/x-diff, Size: 818 bytes --]
From 73ff8e3d19430f305a44cce839a588f68a0704d1 Mon Sep 17 00:00:00 2001
From: Taylan Ulrich B <taylanbayirli@gmail.com>
Date: Thu, 5 Jun 2014 19:27:53 +0200
Subject: [PATCH] R6RS library documentation fix
* doc/ref/api-modules.texi (R6RS Libraries): Move 'export' before
'import' in the example library form, as required by R6RS.
---
doc/ref/api-modules.texi | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/doc/ref/api-modules.texi b/doc/ref/api-modules.texi
index 286a37d..0f54e01 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:
--
1.8.4
next prev parent reply other threads:[~2014-06-05 17:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-15 21:02 bug#17502: R6RS `library' form must have exports before imports Taylan Ulrich Bayirli/Kammer
2014-05-16 3:12 ` dsmich
2014-06-05 1:24 ` Mark H Weaver
2014-06-05 17:31 ` Taylan Ulrich Bayirli/Kammer [this message]
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=878upbp8jg.fsf@taylan.uni.cx \
--to=taylanbayirli@gmail.com \
--cc=17502@debbugs.gnu.org \
--cc=mhw@netris.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).