From: Rob Browning <rlb@defaultvalue.org>
To: guile-devel@gnu.org
Subject: Modules that work with 2.2 and 3.0 with re-export-and-replace
Date: Tue, 25 Feb 2020 18:07:35 -0600 [thread overview]
Message-ID: <87eeuitdmg.fsf@trouble.defaultvalue.org> (raw)
I might be misunderstanding, but it looks like I've hit some cases where
3.0 wants #:re-export-and-replace, and 2.2 rejects it, and I'd like
to create modules that work cleanly with both.
At first I imagined I might use cond-expand, but it won't work inside a
define-module form. Another option might be a procedural
re-export-and-replace! that could be called conditionally after the
define-module.
Yet another option might be to add #:re-export-and-replace to 2.2,
perhaps even as just an alias for #:replace (if that's adequate in 2.2),
but that has the disadvantage of requiring a 2.2 update, which decreases
it's appeal.
In any case, if I'm not misunderstanding, I'm happy to help work on
whatever improvement we prefer.
Thanks
--
Rob Browning
rlb @defaultvalue.org and @debian.org
GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0 39E9 ED1B 597A
GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4
reply other threads:[~2020-02-26 0:07 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=87eeuitdmg.fsf@trouble.defaultvalue.org \
--to=rlb@defaultvalue.org \
--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).