From: Per Bothner <per@bothner.com>
To: craven@gmx.net, kawa mailing list <kawa@sourceware.org>
Subject: Re: R7RS-large aliases for srfis
Date: Thu, 24 Jan 2019 18:52:00 -0000 [thread overview]
Message-ID: <a5112d09-923c-57e5-3047-5db9db30be83@bothner.com> (raw)
In-Reply-To: <87ef99rvik.fsf@nexoid.at>
On 1/18/19 10:50 PM, craven@gmx.net wrote:
> Would it be possible to add the r7rs-large aliases for existing srfis?
> For example, srfi-1 should also be loadable as (import (scheme list)).
> If there is no existing mechanism in kawa for aliases, something like
> the following would suffice:
>
> (define-library (scheme list)
> (import (srfi :1))
> (export xcons ...) ;; just re-export all identifiers
> )
>
> chibi does exactly that ;)
>
> Would be great to help with writing portable(r) code.
It seems a bit premature, since the contents of r7rs-large is still
being decided and debated.
--
--Per Bothner
per@bothner.com http://per.bothner.com/
next prev parent reply other threads:[~2019-01-24 18:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-19 6:50 craven
2019-01-24 18:52 ` Per Bothner [this message]
2019-01-24 20:18 ` Peter
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a5112d09-923c-57e5-3047-5db9db30be83@bothner.com \
--to=per@bothner.com \
--cc=craven@gmx.net \
--cc=kawa@sourceware.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).