unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Noah Lavine <noah.b.lavine@gmail.com>
To: Sunjoong Lee <sunjoong@gmail.com>
Cc: guile-devel@gnu.org
Subject: Re: SRFI-64 module and SRFI-78 module -- archive file attached
Date: Sat, 12 May 2012 13:30:49 -0400	[thread overview]
Message-ID: <CA+U71=N4rGMns6_gSRfkyEV9T-CJu4jhAKJZ2wZbUpWt4SCvBw@mail.gmail.com> (raw)
In-Reply-To: <87bolwmkmg.fsf@gmail.com>

Hello,

> I'd felt afraid of guile-devel@gnu.org because I'm just a newbie and a
> poor enghlish reader/writer; especially of language problem.

That's fine. I am sure that you will get used to it if you contribute a lot.

> My goal? Hum... Like other people, I'd googled when I'd needed a test
> suite. I'd heard the SRFI 64 and SRFI 78 but not been able to use it
> then. So, I'd tried with unit-test in guile-lib.
>
> unit-test is good but my concern was abnormal case, i.e., error or
> exception. unit-test supports assert-exception macro but I feel
> insufficient when unexpected exception occur. So, I was back to SRFI 64
> and made it work on Guile.
>
> I think there are people googling for test suite like me. If Guile
> include SRFI 64 in bundle, it would be helpful to them.

Thanks for doing that! I have only read SRFI-64 yet, but I have a few comments.

First of all, it would be nice you had tests for it. You might be able
to use SRFI-64 to test itself, which would be cool.

Second, since your changes add compatibility for several Scheme
implementations, have you thought about trying to make them part of
the reference implementation? You would probably have to email Per
Bothner to ask him, but that might be the best way to make your
changes available to all of the implementations you are making it for.
If not, I hope Guile would like to have it, but I think you are
targeting more than just Guile.

Noah



  reply	other threads:[~2012-05-12 17:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAK93xho3cVcXZe0o9_PeLXx1DdvcYt-oEzMmvTBVqpKJMBUpyQ@mail.gmail.com>
     [not found] ` <CAK93xhqT--JGaQfkdX8k_=X2PZJpw1g_XqhRPcjCAdk=MSHzuw@mail.gmail.com>
     [not found]   ` <CA+U71=PEZd2OpLc6iWSFJ1jVbQVVpubwfdm4fiauXi9gVmS0PQ@mail.gmail.com>
2012-05-10  9:49     ` SRFI-64 module and SRFI-78 module -- archive file attached Sunjoong Lee
2012-05-12 17:30       ` Noah Lavine [this message]
2012-05-13 21:22         ` Sunjoong Lee
2012-05-14 14:07   ` Sunjoong Lee

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='CA+U71=N4rGMns6_gSRfkyEV9T-CJu4jhAKJZ2wZbUpWt4SCvBw@mail.gmail.com' \
    --to=noah.b.lavine@gmail.com \
    --cc=guile-devel@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).