From: Mark H Weaver <mhw@netris.org>
To: Nala Ginrut <nalaginrut@gmail.com>
Cc: guile-devel@gnu.org
Subject: Re: [ANN] guile-csv 0.0.1 released!
Date: Fri, 08 Feb 2013 11:13:04 -0500 [thread overview]
Message-ID: <87bobu7pin.fsf@tines.lan> (raw)
In-Reply-To: <1360211746.2754.81.camel@Renee-desktop.suse> (Nala Ginrut's message of "Thu, 07 Feb 2013 12:35:46 +0800")
Nala Ginrut <nalaginrut@gmail.com> writes:
> Here is a CSV reader based on Andy's csv-reader.
> And it's ready for guildhall.
[...]
> PS: I'll call ijp to add it into the repo.
I haven't yet looked carefully at this code or its API, so this is no
judgement on you, but in general, I don't think we should follow the
model of "Hey, here's the first release of a library I just hacked up.
Please add it to Guildhall now." That's how we ended up with an ice-9
directory that's full of bitrotted implementations of half-baked APIs.
I'd much rather follow the example of Shiro Kawai, who is very cautious
to experiment with new APIs at length before adding them to Gauche, and
the result is IMO a beautiful and consistent set of APIs.
Maybe we can find a good compromise position between these two extremes.
What do other people think?
Mark
next prev parent reply other threads:[~2013-02-08 16:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-07 4:35 [ANN] guile-csv 0.0.1 released! Nala Ginrut
2013-02-08 16:13 ` Mark H Weaver [this message]
2013-02-08 16:26 ` Ludovic Courtès
2013-02-08 16:35 ` Noah Lavine
2013-02-08 16:59 ` Aleix Conchillo Flaqué
2013-02-09 4:17 ` Nala Ginrut
2013-02-09 3:55 ` Nala Ginrut
2013-02-10 14:05 ` Ian Price
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=87bobu7pin.fsf@tines.lan \
--to=mhw@netris.org \
--cc=guile-devel@gnu.org \
--cc=nalaginrut@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).