From: Kevin Ryde <user42@zip.com.au>
Subject: srfi-6 re-exports (was: frisk versus srfi-1 filter)
Date: Tue, 03 Jun 2003 09:53:29 +1000 [thread overview]
Message-ID: <87fzmsf346.fsf@zip.com.au> (raw)
In-Reply-To: xy78yv53yxd.fsf@nada.kth.se
[-- Attachment #1: Type: text/plain, Size: 514 bytes --]
Mikael Djurfeldt <djurfeldt@nada.kth.se> writes:
>
> The "frisk" script correctly uses :select to explicitly ask for the
> binding "filter" in srfi-1. Of course people should be able to do
> this for *all* bindings of srfi-1, which means that we must re-export
> all core bindings.
Is this a general rule? For instance I wonder if srfi-6 string ports
should re-export similarly. (Below, untested.)
Of course being entirely in the core I don't suppose it's ever
occurred to anyone to use a module at all :-).
[-- Attachment #2: srfi-6.scm.re-export.diff --]
[-- Type: text/plain, Size: 719 bytes --]
--- srfi-6.scm.~1.5.~ 2003-04-07 08:05:30.000000000 +1000
+++ srfi-6.scm 2003-05-25 08:36:58.000000000 +1000
@@ -1,6 +1,6 @@
;;; srfi-6.scm --- Basic String Ports
-;; Copyright (C) 2001, 2002 Free Software Foundation, Inc.
+;; Copyright (C) 2001, 2002, 2003 Free Software Foundation, Inc.
;;
;; This library is free software; you can redistribute it and/or
;; modify it under the terms of the GNU Lesser General Public
@@ -22,7 +22,8 @@
;;; Code:
-(define-module (srfi srfi-6))
+(define-module (srfi srfi-6)
+ #:re-export (open-input-string open-output-string get-output-string))
;; Currently, guile provides these functions by default, so no action
;; is needed, and this file is just a placeholder.
[-- Attachment #3: Type: text/plain, Size: 142 bytes --]
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2003-06-02 23:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-23 22:46 frisk versus srfi-1 filter Kevin Ryde
2003-03-24 9:18 ` Mikael Djurfeldt
2003-06-02 23:53 ` Kevin Ryde [this message]
2003-06-03 11:21 ` srfi-6 re-exports Mikael Djurfeldt
2003-06-06 22:35 ` Kevin Ryde
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=87fzmsf346.fsf@zip.com.au \
--to=user42@zip.com.au \
/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).