From: Stefan Israelsson Tampe <stefan.tampe@spray.se>
To: guile-devel@gnu.org
Subject: Re: new match system bug?
Date: Sat, 4 Sep 2010 17:17:55 +0200 [thread overview]
Message-ID: <201009041717.55140.stefan.tampe@spray.se> (raw)
In-Reply-To: <87wrr1wo34.fsf@gnu.org>
On Saturday, September 04, 2010 05:00:31 pm Ludovic Courtès wrote:
> Hi Stefan!
>
> Stefan Israelsson Tampe <stefan.tampe@spray.se> writes:
> > How true, It's just that the code we took has an extension with a Bug in
> > it. It was intended to work for that case as well.
> >
> > From match.upstream.scm:
> > ;; 2007/07/21 - allowing ellipse patterns in non-final list positions
>
> Then how about reporting it upstream Cc: guile-devel? :-)
>
> Thanks,
> Ludo’.
I'll have a chat with the people at #scheme
next prev parent reply other threads:[~2010-09-04 15:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-04 12:38 new match system bug? Stefan Israelsson Tampe
2010-09-04 12:44 ` Ludovic Courtès
2010-09-04 13:29 ` Stefan Israelsson Tampe
2010-09-04 15:00 ` Ludovic Courtès
2010-09-04 15:17 ` Stefan Israelsson Tampe [this message]
2010-09-04 15:02 ` Stefan Israelsson Tampe
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=201009041717.55140.stefan.tampe@spray.se \
--to=stefan.tampe@spray.se \
--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).