From: Marius Vollmer <mvo@zagadka.de>
Subject: Re: doc srfi-0 cond-expand
Date: Mon, 16 Aug 2004 00:06:03 +0200 [thread overview]
Message-ID: <87d61sawfo.fsf@zagadka.ping.de> (raw)
In-Reply-To: <87658k3o68.fsf@zip.com.au> (Kevin Ryde's message of "Mon, 19 Jul 2004 09:12:31 +1000")
Kevin Ryde <user42@zip.com.au> writes:
> Some new words below for cond-expand,
Nice. We might also want to add some more words on how cond-expand is
implemented, including docs for cond-expand-provide.
Very briefly: cond-expand-provide adds a feature symbol to a given
module and cond-expand looks at each 'used' module whether one of them
has the requested feature.
Thus, cond-expand can behave differently in different modules and the
list of provided SRFIs is not a global property.
--
GPG: D5D4E405 - 2F9B BCCC 8527 692A 04E3 331E FAF8 226A D5D4 E405
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2004-08-15 22:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-18 23:12 doc srfi-0 cond-expand Kevin Ryde
2004-08-15 22:06 ` Marius Vollmer [this message]
2004-08-17 23:54 ` Kevin Ryde
2004-08-18 10:15 ` Marius Vollmer
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=87d61sawfo.fsf@zagadka.ping.de \
--to=mvo@zagadka.de \
/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).