From: Kevin Ryde <user42@zip.com.au>
Subject: cond-expand srfi-6 string ports
Date: Mon, 05 Jul 2004 09:47:30 +1000 [thread overview]
Message-ID: <87fz87qqr1.fsf@zip.com.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 358 bytes --]
Since srfi-6 string ports are builtin to guile, should srfi-6 be
always true in cond-expand? Ie. true before doing any use-module?
I don't suppose it makes much difference, but if the feature is
available it may as well be indicated.
* boot-9.scm (%cond-expand-features): Add srfi-6 which is in the core.
(This could be for the 1.6 branch too.)
[-- Attachment #2: boot-9.scm.cond-expand.diff --]
[-- Type: text/plain, Size: 651 bytes --]
--- boot-9.scm.~1.332.~ 2004-06-17 08:08:25.000000000 +1000
+++ boot-9.scm 2004-07-05 09:47:14.000000000 +1000
@@ -3183,14 +3183,18 @@
;;;
;;; Currently, the following feature identifiers are supported:
;;;
-;;; guile r5rs srfi-0
+;;; guile r5rs srfi-0 srfi-6
;;;
;;; Remember to update the features list when adding more SRFIs.
;;;
(define %cond-expand-features
;; Adjust the above comment when changing this.
- '(guile r5rs srfi-0))
+ '(guile
+ r5rs
+ srfi-0 ;; cond-expand itself
+ srfi-6 ;; open-input-string etc, in the guile core
+ ))
;; This table maps module public interfaces to the list of features.
;;
[-- Attachment #3: Type: text/plain, Size: 143 bytes --]
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next reply other threads:[~2004-07-04 23:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-04 23:47 Kevin Ryde [this message]
2004-07-07 17:30 ` cond-expand srfi-6 string ports Rob Browning
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=87fz87qqr1.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).