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