From: Per Bothner <per@bothner.com>
To: Sunjoong Lee <sunjoong@gmail.com>
Cc: "Ludovic Courtès" <ludo@gnu.org>, guile-user@gnu.org
Subject: Re: SRFI-64 implementation for Guile 2.0
Date: Thu, 27 Dec 2012 19:22:53 -0800 [thread overview]
Message-ID: <50DD108D.3000307@bothner.com> (raw)
In-Reply-To: <CAK93xhp8k=H-2NjMyYzjVnUsrTB14D9CBBsFN5DHK-gKLWqbGw@mail.gmail.com>
I don't think we ever resolved this. It would be great if we could
get good support for Guile (and other Schemes). The way I like to
work (and this is standard in every well-managed Free Software project)
is I don't want to see your updated code; I want to see a patch
(created using 'diff -u' or the equivalent). I prefer a separate
for for each problem you're fixing or enhancement you're making,
so I can evaluate each patch by itself, and perhaps consider
alternative solutions.
The latest version of SRFI-64 (as checked into the Kawa resolitory) is here:
http://sourceware.org/viewvc/kawa/trunk/gnu/kawa/slib/testing.scm?view=co
It may be easier to create a patch if you check out the Kawa sources - see
this link for instructions
http://www.gnu.org/software/kawa/Getting-Kawa.html
--
--Per Bothner
per@bothner.com http://per.bothner.com/
prev parent reply other threads:[~2012-12-28 3:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-12 21:53 SRFI-64 implementation for Guile 2.0 Sunjoong Lee
2012-04-14 1:39 ` Sunjoong Lee
2012-04-14 2:06 ` Per Bothner
2012-04-14 12:43 ` Sunjoong Lee
2012-04-15 20:35 ` Sunjoong Lee
2012-04-20 2:50 ` Noah Lavine
2012-04-20 4:21 ` Per Bothner
2012-04-20 10:19 ` Sunjoong Lee
2012-04-20 18:27 ` Per Bothner
2012-04-20 20:53 ` Sunjoong Lee
2012-04-20 15:18 ` Ludovic Courtès
2012-04-20 17:36 ` Sunjoong Lee
2012-04-21 23:08 ` Ludovic Courtès
2012-04-23 6:07 ` Sunjoong Lee
2012-12-28 3:22 ` Per Bothner [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=50DD108D.3000307@bothner.com \
--to=per@bothner.com \
--cc=guile-user@gnu.org \
--cc=ludo@gnu.org \
--cc=sunjoong@gmail.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).