From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Original-To: caml-list@sympa.inria.fr Delivered-To: caml-list@sympa.inria.fr Received: from mail1-relais-roc.national.inria.fr (mail1-relais-roc.national.inria.fr [192.134.164.82]) by sympa.inria.fr (Postfix) with ESMTPS id 1EE6C7F249 for ; Thu, 1 Nov 2012 01:53:01 +0100 (CET) Received-SPF: None (mail1-smtp-roc.national.inria.fr: no sender authenticity information available from domain of berenger@riken.jp) identity=pra; client-ip=134.160.33.161; receiver=mail1-smtp-roc.national.inria.fr; envelope-from="berenger@riken.jp"; x-sender="berenger@riken.jp"; x-conformance=sidf_compatible Received-SPF: Pass (mail1-smtp-roc.national.inria.fr: domain of berenger@riken.jp designates 134.160.33.161 as permitted sender) identity=mailfrom; client-ip=134.160.33.161; receiver=mail1-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 (mail1-smtp-roc.national.inria.fr: domain of postmaster@postman.riken.jp designates 134.160.33.161 as permitted sender) identity=helo; client-ip=134.160.33.161; receiver=mail1-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: ArkAABjHkVCGoCGhmWdsb2JhbABEwByDaQEBAQEBCAsLBxQngh4BAQU4QBELGAkWDwkDAgECAUUTCAEBiAK7SIt4gxeDJAOIWI0ehWmNVw X-IronPort-AV: E=Sophos;i="4.80,688,1344204000"; d="scan'208";a="179763294" Received: from postman1.riken.jp (HELO postman.riken.jp) ([134.160.33.161]) by mail1-smtp-roc.national.inria.fr with ESMTP; 01 Nov 2012 01:52:59 +0100 Received: from postman.riken.jp (postman1.riken.jp [127.0.0.1]) by postman.riken.jp (Postfix) with SMTP id BE4212588001 for ; Thu, 1 Nov 2012 09:52:56 +0900 (JST) Received: from [172.27.98.103] (rikad98.riken.jp [134.160.214.98]) by postman.riken.jp (Postfix) with ESMTPA id 948CD32A0043 for ; Thu, 1 Nov 2012 09:52:56 +0900 (JST) Message-ID: <5091C7E8.7090007@riken.jp> Date: Thu, 01 Nov 2012 09:52:56 +0900 From: Francois Berenger User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:16.0) Gecko/20121028 Thunderbird/16.0.2 MIME-Version: 1.0 To: caml-list@inria.fr References: <508F22BD.7010103@riken.jp> <026F32A8-2790-4CDD-A839-58655A8074CA@first.in-berlin.de> <508FE869.3070603@inria.fr> <508FFB12.9030307@gmail.com> <508FFE82.2050409@inria.fr> <50900466.2050000@gmail.com> <5090F66F.60803@erratique.ch> <50912619.9090004@gmail.com> <5091C47D.4070501@riken.jp> <5091C584.1010607@gmail.com> In-Reply-To: <5091C584.1010607@gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-PMX-Version: 5.6.0.2009776, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2012.11.1.4221 Subject: Re: [Caml-list] Why should I use .mli files? On 11/01/2012 09:42 AM, Edgar Friendly wrote: > On 10/31/2012 8:38 PM, Francois Berenger wrote: >> It gives me the impression that with such a tool >> people would no more need to maintain both a .ml >> and a .mli file. I like the "centralization" of it. > It's exactly the opposite that drives people to use .mli files; by > having a separation between interface and implementation, it's easier > for people to dig through interfaces to find what's available, instead > of having to dig through the much lengthier implementation. If the .mli is generated automatically from the .ml, including documentation, people can still read their dear .mli file (once it has been generated). Maybe the tool should also be able to detect in an efficient manner that a .mli file is up to date. And people can still write interface files by writing .ml files where all implementation is left to 'failwith "not implemented yet"'. Regards, F.