From: Rob Browning <rlb@defaultvalue.org>
Subject: Re: cond-expand srfi-6 string ports
Date: Wed, 07 Jul 2004 12:30:15 -0500 [thread overview]
Message-ID: <87smc367yw.fsf@trouble.defaultvalue.org> (raw)
In-Reply-To: <87fz87qqr1.fsf@zip.com.au> (Kevin Ryde's message of "Mon, 05 Jul 2004 09:47:30 +1000")
Kevin Ryde <user42@zip.com.au> writes:
> 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?
Sounds reasonable to me.
--
Rob Browning
rlb @defaultvalue.org and @debian.org; previously @cs.utexas.edu
GPG starting 2002-11-03 = 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
prev parent reply other threads:[~2004-07-07 17:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-04 23:47 cond-expand srfi-6 string ports Kevin Ryde
2004-07-07 17:30 ` Rob Browning [this message]
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=87smc367yw.fsf@trouble.defaultvalue.org \
--to=rlb@defaultvalue.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).