unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Mark H Weaver <mhw@netris.org>
To: Per Bothner <per@bothner.com>
Cc: guile-devel@gnu.org
Subject: Latest version of SRFI-64 testing.scm?
Date: Fri, 24 Jan 2014 14:22:14 -0500	[thread overview]
Message-ID: <87fvodi3rt.fsf@netris.org> (raw)

Hi Per,

I'd like to include a fully-featured SRFI-64 in the upcoming Guile
2.0.10 release, and to do so in such a way that most of the changes can
be folded back into your upstream version.

I'm aware of the earlier work by Sunjoong Lee in 2012, but it seems that
he made extensive stylistic changes to your code, and I'd prefer to stay
closer to your upstream version.

Where can I find your latest versions of testing.scm and
srfi-64-test.scm?

    Regards,
      Mark



             reply	other threads:[~2014-01-24 19:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-24 19:22 Mark H Weaver [this message]
2014-01-24 20:33 ` Latest version of SRFI-64 testing.scm? Per Bothner
2014-01-29  8:57   ` [PATCH] Changes to SRFI-64 testing.scm to support Guile 2, etc Mark H Weaver
2014-01-29 15:46     ` Per Bothner
2014-01-30 15:18       ` Mark H Weaver
2014-02-06 17:49         ` Per Bothner

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=87fvodi3rt.fsf@netris.org \
    --to=mhw@netris.org \
    --cc=guile-devel@gnu.org \
    --cc=per@bothner.com \
    /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).