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 mail4-relais-sop.national.inria.fr (mail4-relais-sop.national.inria.fr [192.134.164.105]) by sympa.inria.fr (Postfix) with ESMTPS id 780007F249 for ; Thu, 1 Nov 2012 01:42:39 +0100 (CET) Received-SPF: None (mail4-smtp-sop.national.inria.fr: no sender authenticity information available from domain of thelema314@gmail.com) identity=pra; client-ip=209.85.223.182; receiver=mail4-smtp-sop.national.inria.fr; envelope-from="thelema314@gmail.com"; x-sender="thelema314@gmail.com"; x-conformance=sidf_compatible Received-SPF: Pass (mail4-smtp-sop.national.inria.fr: domain of thelema314@gmail.com designates 209.85.223.182 as permitted sender) identity=mailfrom; client-ip=209.85.223.182; receiver=mail4-smtp-sop.national.inria.fr; envelope-from="thelema314@gmail.com"; x-sender="thelema314@gmail.com"; x-conformance=sidf_compatible; x-record-type="v=spf1" Received-SPF: None (mail4-smtp-sop.national.inria.fr: no sender authenticity information available from domain of postmaster@mail-ie0-f182.google.com) identity=helo; client-ip=209.85.223.182; receiver=mail4-smtp-sop.national.inria.fr; envelope-from="thelema314@gmail.com"; x-sender="postmaster@mail-ie0-f182.google.com"; x-conformance=sidf_compatible X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AsABAIXEkVDRVd+2m2dsb2JhbABEhVC+CggjAQEBAQEICQsJFCeCHgEBBTgIARscAgMMBgULDQkWDwkDAgECARERAQUBHBMIAQGHbwEDD5xijDKCdoUTChknDVmIdQEFDItsgxeDJAOVdoVpiHg/hC0 X-IronPort-AV: E=Sophos;i="4.80,688,1344204000"; d="scan'208";a="161066942" Received: from mail-ie0-f182.google.com ([209.85.223.182]) by mail4-smtp-sop.national.inria.fr with ESMTP/TLS/RC4-SHA; 01 Nov 2012 01:42:38 +0100 Received: by mail-ie0-f182.google.com with SMTP id k10so5178515iea.27 for ; Wed, 31 Oct 2012 17:42:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=wv4TAHMWwnPyiQ2+YAUJ0gw5Buj9c/phn9nWPvqoHqg=; b=XhMGgKXpfVkjTV0dwSfKwi1VTO136QHzzP+IlRFZMDz55NLWsoMLxqje9OtTtRDNPM iX7NJV+8BsFJIju/cV6Eb6gyxCBQHh1OpnU57Thh+lufh/n1/wNreGDmNGW+ixT6WsUc rsGDdYl6bEdhm8gXpeZg2HgJxZEc3NrROlflW8UoBK/yT1TA3titN8uwOhOW0XiN5DYy hSigJxO3PQ5UrEV4/40x4iTsBnGvnYzAZxPuiw3XwuLCgT4R22q0WXhKLAZuIkZHmLIy da7QCSVaoJg1FOAyq9wUQiun9I+LgbiRctcneIEvI2J5F//ebz7fD9+/0n3hZBiAYpkc JfEQ== Received: by 10.42.175.5 with SMTP id ay5mr20879612icb.10.1351730557497; Wed, 31 Oct 2012 17:42:37 -0700 (PDT) Received: from [192.168.1.73] (99-121-78-10.lightspeed.lnngmi.sbcglobal.net. [99.121.78.10]) by mx.google.com with ESMTPS id gz10sm4554557igc.9.2012.10.31.17.42.36 (version=SSLv3 cipher=OTHER); Wed, 31 Oct 2012 17:42:36 -0700 (PDT) Message-ID: <5091C584.1010607@gmail.com> Date: Wed, 31 Oct 2012 20:42:44 -0400 From: Edgar Friendly User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121010 Thunderbird/16.0.1 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> In-Reply-To: <5091C47D.4070501@riken.jp> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Caml-list] Why should I use .mli files? 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. E.