caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: skaller <skaller@users.sourceforge.net>
To: Richard Jones <rich@annexia.org>
Cc: Brian Hurt <bhurt@spnz.org>,
	tmp123@menta.net, ocaml ml <caml-list@inria.fr>
Subject: Re: [Caml-list] Sorted list
Date: Sun, 05 Aug 2007 03:54:47 +1000	[thread overview]
Message-ID: <1186250087.6025.41.camel@rosella.wigram> (raw)
In-Reply-To: <20070804162135.GA7370@furbychan.cocan.org>

On Sat, 2007-08-04 at 17:21 +0100, Richard Jones wrote:

> > Well, I would like to see a community process for selecting,
> > implementing, documenting and maintaining a set of good algorithms
> > which go IN THE STANDARD DISTRIBUTION (under the usual LGPL+X licence,
> > with a disclaimer the code base isn't maintained by Inria, merely
> > distributed on behalf of the community).
> 
> But what's wrong with extlib?  Now I know it's not the "Standard"
> distribution, but that's a mere packaging issue.

A 'mere' packaging issue??? That's the very issue that concerns me.

I think there are other (technical) problems with extlib too:
the iterator design is a bit suspicious, and the implementation
is using Obj.magic without Inria support.

However the packaging issue is the primary problem, for this
and other 3PLs (third party libraries).

My own package requires standard Python, Ocaml, and C++ distros.
That's it. That's already bad enough. The only 3PL's allowed
are provided as source and built by the Felix build system.
On the Ocaml side this includes Dypgen and OCS Scheme.
Extlib couldn't be included this way because it is LGPL.
Felix is FFAU (free for any use modulo propagating copyright
notices).

I carefully avoid 3PL's I can't include as source, and as
many complications -- such as camlp4/5 -- as possible.
[I wish I could use ulex .. but it uses camlp4/5 extensions]
Getting Ocaml to work at all on Windows is hard enough
for clients.

-- 
John Skaller <skaller at users dot sf dot net>
Felix, successor to C++: http://felix.sf.net


  parent reply	other threads:[~2007-08-04 17:54 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-04  9:35 tmp123
2007-08-04 10:00 ` [Caml-list] " Jon Harrop
2007-08-04 10:29 ` Philippe Wang
2007-08-04 11:22   ` skaller
2007-08-04 12:23     ` Philippe Wang
2007-08-04 13:39       ` skaller
2007-08-04 14:01         ` Philippe Wang
2007-08-04 14:45           ` skaller
2007-08-04 14:27       ` tmp123
2007-08-04 20:33       ` Christophe TROESTLER
2007-08-04 14:37     ` tmp123
2007-08-04 15:09       ` Brian Hurt
2007-08-04 15:42         ` skaller
2007-08-04 16:21           ` Richard Jones
2007-08-04 17:17             ` Brian Hurt
2007-08-04 18:24               ` skaller
2007-08-04 17:54             ` skaller [this message]
2007-08-04 19:16               ` Richard Jones
2007-08-05 16:22                 ` David Allsopp
2007-08-05 16:41                   ` Xavier Leroy
2007-08-05 17:01                     ` David Allsopp
2007-08-04 17:35           ` Julien Moutinho
2007-08-04 18:04             ` skaller
2007-08-05  1:47             ` Jon Harrop
2007-08-05 11:44               ` Erik de Castro Lopo
2007-08-05 12:03                 ` Jacques GARRIGUE
2007-08-05 12:31                   ` Erik de Castro Lopo
2007-08-05 13:22                     ` Richard Jones
2007-08-05 20:47                       ` Erik de Castro Lopo
2007-08-05 13:17                 ` Richard Jones
2007-08-05 16:26           ` Xavier Leroy
2007-08-05 23:47             ` skaller
2007-08-04 15:36       ` skaller
2007-08-04 15:17     ` tmp123
2007-08-12 12:05       ` Andrej Bauer
2007-08-04 12:15 ` Brian Hurt
2007-08-04 12:36   ` Brian Hurt
2007-08-04 13:49     ` skaller
2007-08-04 12:16 ` Daniel Bünzli
2007-08-04 12:58 ` Oliver Bandel

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=1186250087.6025.41.camel@rosella.wigram \
    --to=skaller@users.sourceforge.net \
    --cc=bhurt@spnz.org \
    --cc=caml-list@inria.fr \
    --cc=rich@annexia.org \
    --cc=tmp123@menta.net \
    /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).