caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Alain.Frisch@ens.fr
To: Markus Mottl <markus@oefai.at>
Cc: Inria Ocaml Mailing List <caml-list@inria.fr>
Subject: Re: [Caml-list] PostgreSQL-OCaml 1.0.1
Date: Thu, 29 Jan 2004 19:18:48 +0100 (MET)	[thread overview]
Message-ID: <Pine.SOL.4.44.0401290922110.17012-100000@clipper.ens.fr> (raw)
In-Reply-To: <20040128232131.GA22126@fichte.ai.univie.ac.at>

On Thu, 29 Jan 2004, Markus Mottl wrote:

> Alain hasn't changed anything in three years so I suppose this library
> would otherwise have been unmaintained anyway?

Ahem. The last release is dated 2004-01-20 ;-)  (added support for
escaping strings).

The library is used by a non-negligible number of people, including by
some companies and for other libraries (e.g. mod_caml, Chartpak, DBForge,
...). And according to some mails I got, the users are quite satisfied
with the current library. Moreover, it has been packaged for some Linux
distributions.

It's a good thing to add documentation (even though the users would need
to read the libpq doc anyway). Actually, this is the only feature request
for Postgres that I have not honoured. But changing the interface
(changing names, types, and removing all the non-OO low-level interface)
would force existing users to rewrite there code for no benefit (AFAICT).
So I'm not going to stop maintaining the existing library, even though I'd
be glad to give maintenance to you since I'm not using the library, and
even though I feel it's somewhat a waste of resources for the community
to maintain and package two libraries.

I would have appreciated to know about your intention to "fork" the
library before the public annoucement so that we could have agreed on a
policy. Well anyway, not a big deal.



-- Alain

-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners


  parent reply	other threads:[~2004-01-29 18:18 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-28 18:32 Markus Mottl
2004-01-28 22:44 ` Stefano Zacchiroli
2004-01-28 23:21   ` Markus Mottl
2004-01-29  9:38     ` Sven Luther
2004-01-29 18:18     ` Alain.Frisch [this message]
2004-01-29 20:06       ` Richard Jones
2004-01-29 23:36         ` Markus Mottl
2004-01-30  5:50         ` Josh Burdick
2004-01-30  7:37           ` Shawn Wagner
2004-01-30  8:21           ` Vitaly Lugovsky
2004-01-30 10:24             ` Benjamin Geer
2004-01-30 10:47               ` Richard Jones
2004-01-30 14:58                 ` Gerd Stolpmann
2004-01-30 15:46                   ` Richard Jones
2004-01-30 11:14               ` Markus Mottl
2004-01-30 11:25               ` Vitaly Lugovsky
2004-01-30 11:41                 ` Benjamin Geer
2004-01-30 16:44               ` Alex Baretta
2004-01-30 16:49                 ` Benjamin Geer
2004-01-30  8:23           ` Alain.Frisch
2004-02-01 21:03   ` Alain.Frisch
2004-01-30 12:02 Richard Jones
2004-01-30 12:15 ` Benjamin Geer
2004-01-30 12:23   ` Richard Jones
2004-01-30 12:30     ` Richard Jones
2004-01-30 12:43     ` Benjamin Geer
2004-01-30 12:56     ` Benjamin Geer
2004-01-30 13:22       ` Richard Jones

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.SOL.4.44.0401290922110.17012-100000@clipper.ens.fr \
    --to=alain.frisch@ens.fr \
    --cc=caml-list@inria.fr \
    --cc=markus@oefai.at \
    /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 NNTP newsgroup(s).