From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <berenger@riken.jp>
Received: from mail2-relais-roc.national.inria.fr (mail2-relais-roc.national.inria.fr [192.134.164.83])
	by sympa.inria.fr (Postfix) with ESMTPS id 6D2DD7EE6B
	for <caml-list@sympa.inria.fr>; Fri, 29 Nov 2013 01:43:24 +0100 (CET)
Received-SPF: None (mail2-smtp-roc.national.inria.fr: no sender
  authenticity information available from domain of
  berenger@riken.jp) identity=pra; client-ip=134.160.33.175;
  receiver=mail2-smtp-roc.national.inria.fr;
  envelope-from="berenger@riken.jp";
  x-sender="berenger@riken.jp"; x-conformance=sidf_compatible
Received-SPF: Pass (mail2-smtp-roc.national.inria.fr: domain of
  berenger@riken.jp designates 134.160.33.175 as permitted
  sender) identity=mailfrom; client-ip=134.160.33.175;
  receiver=mail2-smtp-roc.national.inria.fr;
  envelope-from="berenger@riken.jp";
  x-sender="berenger@riken.jp"; x-conformance=sidf_compatible;
  x-record-type="v=spf1"
Received-SPF: Pass (mail2-smtp-roc.national.inria.fr: domain of
  postmaster@postman.riken.jp designates 134.160.33.175 as
  permitted sender) identity=helo; client-ip=134.160.33.175;
  receiver=mail2-smtp-roc.national.inria.fr;
  envelope-from="berenger@riken.jp";
  x-sender="postmaster@postman.riken.jp";
  x-conformance=sidf_compatible; x-record-type="v=spf1"
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ah0EAG3il1KGoCGvh2dsb2JhbABZuWOCegqBMQ4BAQEKCwkHFiiCJQEBBAE4QAYLCxgJFg8JAwIBAgFFEwgBAYd3BsBOF44gbxaEHQOJQI5UhkWPBg
X-IPAS-Result: Ah0EAG3il1KGoCGvh2dsb2JhbABZuWOCegqBMQ4BAQEKCwkHFiiCJQEBBAE4QAYLCxgJFg8JAwIBAgFFEwgBAYd3BsBOF44gbxaEHQOJQI5UhkWPBg
X-IronPort-AV: E=Sophos;i="4.93,794,1378850400"; 
   d="scan'208";a="45988248"
Received: from postman3.riken.jp (HELO postman.riken.jp) ([134.160.33.175])
  by mail2-smtp-roc.national.inria.fr with ESMTP; 29 Nov 2013 01:43:22 +0100
Received: from postman.riken.jp (postman3.riken.jp [127.0.0.1])
	by postman.riken.jp (Postfix) with SMTP id CE92D38380E8
	for <caml-list@inria.fr>; Fri, 29 Nov 2013 09:43:18 +0900 (JST)
Received: from [172.27.98.103] (rikad98.riken.jp [134.160.214.98])
	by postman.riken.jp (Postfix) with ESMTPA id B92C138201EC
	for <caml-list@inria.fr>; Fri, 29 Nov 2013 09:43:18 +0900 (JST)
Message-ID: <5297E326.4090402@riken.jp>
Date: Fri, 29 Nov 2013 09:43:18 +0900
From: Francois Berenger <berenger@riken.jp>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.1.1
MIME-Version: 1.0
To: caml-list@inria.fr
References: <20131125031021.384845a8@kiwi.local.tld> <20131125191546.08a22f18@kiwi.local.tld> <529347C2.3000202@riken.jp> <20131128195702.GA24153@annexia.org>
In-Reply-To: <20131128195702.GA24153@annexia.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-PMX-Version: 6.0.0.2142326, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2013.11.29.3615
Subject: Re: [Caml-list] extlib 1.6.0 released

On 11/29/2013 04:57 AM, Richard W.M. Jones wrote:
> On Mon, Nov 25, 2013 at 09:51:14PM +0900, Francois Berenger wrote:
>> I even wonder why extlib is still out there.
>> I was thinking it was superseded by batteries.
>
> Extlib has its niche, and several programs exist that are using it.
> There's sometimes no need for a huge library like Batteries to do a
> few things that extlib does.

I was wondering if it doesn't hide some kind of user request, like
batteries should be split in a core part and some other parts.
Other big libraries did that (Core some time ago, for example).

> Also .. if people want to hack on extlib, good luck to them.
>
> Rich.