caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Markus Mottl <markus@oefai.at>
To: Inria Ocaml Mailing List <caml-list@inria.fr>
Subject: Re: [Caml-list] PostgreSQL-OCaml 1.0.1
Date: Thu, 29 Jan 2004 00:21:31 +0100	[thread overview]
Message-ID: <20040128232131.GA22126@fichte.ai.univie.ac.at> (raw)
In-Reply-To: <20040128224410.GC16830@fistandantilus.takhisis.org>

On Wed, 28 Jan 2004, Stefano Zacchiroli wrote:
> On Wed, Jan 28, 2004 at 07:32:18PM +0100, Markus Mottl wrote:
> > complete library for accessing the PostgreSQL-database. This library
> > builds on Alain Frisch's previous interface (postgres-20010808).
> 
> This sentence doesn't clarify an issue: is this library supposed to
> supersede Alain's bindings or to be a fork?

I actually haven't asked Alain yet what he thinks about it :-)

Since I currently need PostgreSQL-bindings, I just took his version and
adapted it to my taste. The interface was hardly documented (its most
serious shortcoming), which usually prevents libraries from widespread
use so I also did that.

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

There is hardly anything left to add to this library so there are no
foreseeable major changes. The new additions and cleanups also do not
make such a big difference. If Alain wants to add or change anything,
he will still recognize the code and can do so easily. I'd say it's safe
to use the new version...

Regards,
Markus

-- 
Markus Mottl          http://www.oefai.at/~markus          markus@oefai.at

-------------------
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


  reply	other threads:[~2004-01-28 23:21 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 [this message]
2004-01-29  9:38     ` Sven Luther
2004-01-29 18:18     ` Alain.Frisch
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=20040128232131.GA22126@fichte.ai.univie.ac.at \
    --to=markus@oefai.at \
    --cc=caml-list@inria.fr \
    /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).