Mailing list for all users of the OCaml language and system.
 help / color / mirror / Atom feed
From: Francois Berenger <berenger@riken.jp>
To: caml-list@inria.fr
Subject: Re: [Caml-list] extlib 1.6.0 released
Date: Mon, 25 Nov 2013 21:51:14 +0900	[thread overview]
Message-ID: <529347C2.3000202@riken.jp> (raw)
In-Reply-To: <20131125191546.08a22f18@kiwi.local.tld>

On 11/25/13, 8:15 PM, ygrek wrote:
> On Mon, 25 Nov 2013 03:10:21 +0800
> ygrek <ygrek@autistici.org> wrote:
>
>>   * Install additionally `extlib_min` with reduced set of modules (to mitigate linking conflicts)
>
> After some more thought I don't really like this approach.
> See the reasoning in http://code.google.com/p/ocaml-extlib/issues/detail?id=23#c6
> The new approach (implemented in svn) is to include offending modules conditionally during extlib build
> time, so that extlib without UChar module can be easily integrated into codebases that don't depend on UChar,
> while others may take some time to amend the code. Basically the decision is being retargeted
> from code developer to the end-user/admin. Cursory research suggests that in opam there is one package
> using UTF8 module from extlib - namely javalib. So practically it means creating
> two opam packages extlib and extlib_full and promoting the first. This sounds better than having
> two ocamlfind packages, anyway.
> What do you think?

I even wonder why extlib is still out there.
I was thinking it was superseded by batteries.


  reply	other threads:[~2013-11-25 12:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-24 19:10 ygrek
2013-11-25 11:15 ` ygrek
2013-11-25 12:51   ` Francois Berenger [this message]
2013-11-28 19:57     ` Richard W.M. Jones
2013-11-29  0:43       ` Francois Berenger
2013-11-29  8:22         ` Sergei Lebedev
2013-11-26  9:36   ` ygrek

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=529347C2.3000202@riken.jp \
    --to=berenger@riken.jp \
    --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