unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Andy Wingo <wingo@pobox.com>
To: guile-devel <guile-devel@gnu.org>
Subject: (define-module (foo) #:import (...)), a la r6rs
Date: Thu, 28 Jul 2011 12:37:42 +0200	[thread overview]
Message-ID: <87fwlqvgg9.fsf@pobox.com> (raw)

Hi,

I was hacking on Dorodango today, in a script that happened to have a
Guile-style (define-module ...) block, and I was importing pieces of an
rnrs library.  Then I needed to update the import set to provide what
was needed.  In the middle of making a keyboard macro to add
#:use-module before the library names, I realized that `library' is
actually a lot better in this regard, in that you just have one `import'
block, and all the libraries are listed there without having a prefix on
each one.

So what do you all think about:

  (define-module (foo)
    #:import ((bar)
              (only (baz) qux foo)
              ...))

Or even:

  (define-module (foo)
    (import (bar)
            (only (baz) qux foo)
            ...))

We would continue to support the #:use-module syntax indefinitely, of
course.

It looks like the upcoming R7RS standard will support these import specs
in the same way as the r6rs, though without version specifiers
(thankfully).

Andy
-- 
http://wingolog.org/



             reply	other threads:[~2011-07-28 10:37 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-28 10:37 Andy Wingo [this message]
2011-07-28 21:23 ` (define-module (foo) #:import (...)), a la r6rs Ludovic Courtès
2011-11-09 23:08   ` Andy Wingo
2011-11-09 23:50     ` Ludovic Courtès
2011-12-06 11:30       ` Andy Wingo
2012-01-07  0:23         ` Andy Wingo
2012-01-08 16:28         ` Ludovic Courtès
2012-01-08 16:44           ` Andy Wingo
2011-11-10 12:35     ` David Pirotte
2011-07-28 21:40 ` Mike Gran
2011-07-28 21:52 ` Jose A. Ortega Ruiz

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=87fwlqvgg9.fsf@pobox.com \
    --to=wingo@pobox.com \
    --cc=guile-devel@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).