From: ludo@gnu.org (Ludovic Courtès)
To: guile-devel@gnu.org
Subject: Re: [PATCH] Preserve additional R6RS library name components after srfi :n
Date: Sun, 04 Nov 2012 21:35:06 +0100 [thread overview]
Message-ID: <87fw4p6r9h.fsf@gnu.org> (raw)
In-Reply-To: 87bofdhqj1.fsf@tines.lan
Mark H Weaver <mhw@netris.org> skribis:
> Here's another patch to help with R6RS libraries. Right now, if you use
> R6RS syntax to import (srfi :99 records procedural), the components
> after the :99 will be silently dropped and it will treat this as if you
> imported (srfi :99). I suspect this is simply a bug.
>
> Does anyone see a reason not to commit this to stable-2.0?
Fine with me!
Ludo’.
prev parent reply other threads:[~2012-11-04 20:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-04 5:43 [PATCH] Preserve additional R6RS library name components after srfi :n Mark H Weaver
2012-11-04 20:35 ` Ludovic Courtès [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=87fw4p6r9h.fsf@gnu.org \
--to=ludo@gnu.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).