Menu
▾
▴
ocaml-lib-devel
|
From: Nicolas C. <war...@fr...> - 2004-04-24 09:44:01
|
Hi list, Here's a todo list proposal before releasing 1.1 : - writing documentation of newest modules : IO , Base64 and PMap - adding Ocaml DBI (only the common abstract interfaces, no driver) : I'm waiting for OCaml DBI 's author Richard Johns answer. Everybody is of course welcome in contributing documentation, comments, or code before next release. Best Regards, Nicolas Cannasse |
|
From: Nicolas C. <war...@fr...> - 2004-04-25 09:21:51
|
> Hi list, > > Here's a todo list proposal before releasing 1.1 : > - writing documentation of newest modules : IO , Base64 and PMap > - adding Ocaml DBI (only the common abstract interfaces, no driver) : I'm > waiting for OCaml DBI 's author Richard Johns answer. > Everybody is of course welcome in contributing documentation, comments, or > code before next release. Today : - added Base64 IO support (for mapping an IO with a Base64 encoding) and documentation - committed dbi.ml and dbi.ml , common DB interfaces for OCamlDBI. Regards, Nicolas Cannasse |
|
From: John G. <jgo...@co...> - 2004-04-26 00:39:20
|
On Sun, Apr 25, 2004 at 11:14:43AM +0200, Nicolas Cannasse wrote: > > waiting for OCaml DBI 's author Richard Johns answer. > > Everybody is of course welcome in contributing documentation, comments, or > > code before next release. > > Today : > - added Base64 IO support (for mapping an IO with a Base64 encoding) and > documentation > - committed dbi.ml and dbi.ml , common DB interfaces for OCamlDBI. Have you added OcamlDBI itself, or simply some sort of interface to it? If the latter, what is the point, given than OcamlDBI is itself a generic interface? If the former, what is the point, given that OcamlDBI already exists? :-) -- John |
|
From: Nicolas C. <war...@fr...> - 2004-04-26 07:02:04
|
> On Sun, Apr 25, 2004 at 11:14:43AM +0200, Nicolas Cannasse wrote: > > > waiting for OCaml DBI 's author Richard Johns answer. > > > Everybody is of course welcome in contributing documentation, comments, or > > > code before next release. > > > > Today : > > - added Base64 IO support (for mapping an IO with a Base64 encoding) and > > documentation > > - committed dbi.ml and dbi.ml , common DB interfaces for OCamlDBI. > > Have you added OcamlDBI itself, or simply some sort of interface to it? > If the latter, what is the point, given than OcamlDBI is itself a > generic interface? If the former, what is the point, given that > OcamlDBI already exists? :-) It's OcamlDBI itself, but only the "common headers" since the drivers needs C code. It was included in ExtLib with the agreement of Richard Jones, for the sake of widespread of both librairies. Later, OcamlDBI might be only maintained into the ExtLib CVS tree, but nothing has been decided yet. Best Regards, Nicolas Cannasse |
|
From: Richard J. <ri...@an...> - 2004-05-03 12:02:08
|
On Mon, Apr 26, 2004 at 09:01:10AM +0200, Nicolas Cannasse wrote: > It's OcamlDBI itself, but only the "common headers" since the > drivers needs C code. It was included in ExtLib with the agreement > of Richard Jones, for the sake of widespread of both > librairies. Later, OcamlDBI might be only maintained into the ExtLib > CVS tree, but nothing has been decided yet. Actually OcamlDBI doesn't itself contain any C code. It depends on external drivers (eg. the Postgres module) which contain C code. Is the policy that ExtLib itself only depends on base OCaml functionality? Rich. -- Richard Jones. http://www.annexia.org/ http://www.j-london.com/ Merjis Ltd. http://www.merjis.com/ - improving website return on investment 'There is a joke about American engineers and French engineers. The American team brings a prototype to the French team. The French team's response is: "Well, it works fine in practice; but how will it hold up in theory?"' |
|
From: Nicolas C. <war...@fr...> - 2004-05-03 14:46:16
|
> On Mon, Apr 26, 2004 at 09:01:10AM +0200, Nicolas Cannasse wrote: > > It's OcamlDBI itself, but only the "common headers" since the > > drivers needs C code. It was included in ExtLib with the agreement > > of Richard Jones, for the sake of widespread of both > > librairies. Later, OcamlDBI might be only maintained into the ExtLib > > CVS tree, but nothing has been decided yet. > > Actually OcamlDBI doesn't itself contain any C code. It depends on > external drivers (eg. the Postgres module) which contain C code. Is > the policy that ExtLib itself only depends on base OCaml > functionality? > > Rich. I was meaning OCamlDBI = dbi.ml + .mli , so I there is two ways of working : 1) for each OcamlDBI release, copy dbi.ml + .mli from OcamlDBI CVS to ExtLib CVS 2) maintain dbi.ml + dbi.mli directly into ExtLib CVS (but then the users need to install ExtLib in order to get the last version of OcamlDBI, not sure that's what you want :). Of course, no driver will be added to ExtLib CVS (since they require C). Regards, Nicolas Cannasse |
|
From: Richard J. <ri...@an...> - 2004-05-03 14:51:04
|
On Mon, May 03, 2004 at 04:45:18PM +0200, Nicolas Cannasse wrote:
> > On Mon, Apr 26, 2004 at 09:01:10AM +0200, Nicolas Cannasse wrote:
> > > It's OcamlDBI itself, but only the "common headers" since the
> > > drivers needs C code. It was included in ExtLib with the agreement
> > > of Richard Jones, for the sake of widespread of both
> > > librairies. Later, OcamlDBI might be only maintained into the ExtLib
> > > CVS tree, but nothing has been decided yet.
> >
> > Actually OcamlDBI doesn't itself contain any C code. It depends on
> > external drivers (eg. the Postgres module) which contain C code. Is
> > the policy that ExtLib itself only depends on base OCaml
> > functionality?
> >
> > Rich.
>
> I was meaning OCamlDBI = dbi.ml + .mli , so I there is two ways of working :
> 1) for each OcamlDBI release, copy dbi.ml + .mli from OcamlDBI CVS to ExtLib
> CVS
> 2) maintain dbi.ml + dbi.mli directly into ExtLib CVS (but then the users
> need to install ExtLib in order to get the last version of OcamlDBI, not
> sure that's what you want :).
> Of course, no driver will be added to ExtLib CVS (since they require C).
Actually you missed my point there. OCamlDBI *itself* (including
things like dbi_postgres.{ml,mli}) doesn't contain any C code. But it
depends on external modules like Alaine Frische's Postgres which are,
of course, written in C. So if you pulled the whole of OCamlDBI into
ExtLib then you still wouldn't have any C code. But my question is:
Is the policy that ExtLib itself only depends on base OCaml
functionality, or may it depend on external modules (eg. Alaine
Frische's Postgres module)?
Rich.
--
Richard Jones. http://www.annexia.org/ http://www.j-london.com/
Merjis Ltd. http://www.merjis.com/ - improving website return on investment
PTHRLIB is a library for writing small, efficient and fast servers in C.
HTTP, CGI, DBI, lightweight threads: http://www.annexia.org/freeware/pthrlib/
|
|
From: Nicolas C. <war...@fr...> - 2004-05-03 15:11:03
|
> On Mon, May 03, 2004 at 04:45:18PM +0200, Nicolas Cannasse wrote:
> > > On Mon, Apr 26, 2004 at 09:01:10AM +0200, Nicolas Cannasse wrote:
> > > > It's OcamlDBI itself, but only the "common headers" since the
> > > > drivers needs C code. It was included in ExtLib with the agreement
> > > > of Richard Jones, for the sake of widespread of both
> > > > librairies. Later, OcamlDBI might be only maintained into the ExtLib
> > > > CVS tree, but nothing has been decided yet.
> > >
> > > Actually OcamlDBI doesn't itself contain any C code. It depends on
> > > external drivers (eg. the Postgres module) which contain C code. Is
> > > the policy that ExtLib itself only depends on base OCaml
> > > functionality?
> > >
> > > Rich.
> >
> > I was meaning OCamlDBI = dbi.ml + .mli , so I there is two ways of
working :
> > 1) for each OcamlDBI release, copy dbi.ml + .mli from OcamlDBI CVS to
ExtLib
> > CVS
> > 2) maintain dbi.ml + dbi.mli directly into ExtLib CVS (but then the
users
> > need to install ExtLib in order to get the last version of OcamlDBI, not
> > sure that's what you want :).
> > Of course, no driver will be added to ExtLib CVS (since they require C).
>
> Actually you missed my point there. OCamlDBI *itself* (including
> things like dbi_postgres.{ml,mli}) doesn't contain any C code. But it
> depends on external modules like Alaine Frische's Postgres which are,
> of course, written in C. So if you pulled the whole of OCamlDBI into
> ExtLib then you still wouldn't have any C code. But my question is:
> Is the policy that ExtLib itself only depends on base OCaml
> functionality, or may it depend on external modules (eg. Alaine
> Frische's Postgres module)?
>
> Rich.
Sorry I misunderstood :)
Yes, ExtLib is also monolithic and does not require extra libraries to
install.
One solution is to keep the - pure-ocaml - drivers outside of ExtLib, the
other is to have a directory /contrib or /tools that is distributed but not
compiled nor installed by default.
Regards,
Nicolas Cannasse
|
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X