From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <berenger@riken.jp>
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 A35327F249
	for <caml-list@sympa.inria.fr>; Wed, 31 Oct 2012 02:03:26 +0100 (CET)
Received-SPF: None (mail4-smtp-sop.national.inria.fr: no sender
  authenticity information available from domain of
  berenger@riken.jp) identity=pra; client-ip=134.160.33.161;
  receiver=mail4-smtp-sop.national.inria.fr;
  envelope-from="berenger@riken.jp";
  x-sender="berenger@riken.jp"; x-conformance=sidf_compatible
Received-SPF: Pass (mail4-smtp-sop.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=mail4-smtp-sop.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 (mail4-smtp-sop.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=mail4-smtp-sop.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: ArECAEl4kFCGoCGhhWdsb2JhbABEwCOCTgQEgScBAQEKCwsFFieCHgEBBThAARALGAkWDwkDAgECAUUTAQcBAYgCvFiLd4MXgyQDiFeNHoVpjVc
X-IronPort-AV: E=Sophos;i="4.80,683,1344204000"; 
   d="scan'208";a="160945509"
Received: from postman1.riken.jp (HELO postman.riken.jp) ([134.160.33.161])
  by mail4-smtp-sop.national.inria.fr with ESMTP; 31 Oct 2012 02:03:24 +0100
Received: from postman.riken.jp (postman1.riken.jp [127.0.0.1])
	by postman.riken.jp (Postfix) with SMTP id B387F2588001;
	Wed, 31 Oct 2012 10:03:22 +0900 (JST)
Received: from [172.27.98.103] (rikad98.riken.jp [134.160.214.98])
	by postman.riken.jp (Postfix) with ESMTPA id 8673D32A0043;
	Wed, 31 Oct 2012 10:03:22 +0900 (JST)
Message-ID: <509078DA.6010300@riken.jp>
Date: Wed, 31 Oct 2012 10:03:22 +0900
From: Francois Berenger <berenger@riken.jp>
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
CC: romain.bardou@inria.fr
References: <508F22BD.7010103@riken.jp> <CACX4useWCnu4tg2jAkSx=K=38BaHimgZWRFPF1Jyj5gw+YHAbg@mail.gmail.com> <508F9B56.8090806@riken.jp> <508FBCDC.5000104@gmail.com> <508FD6B3.9080407@inria.fr>
In-Reply-To: <508FD6B3.9080407@inria.fr>
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.10.31.5125
Subject: Re: [Caml-list] Re: Why should I use .mli files?

On 10/30/2012 10:31 PM, Romain Bardou wrote:
> Usually the code you have to duplicate is type definitions which are not
> private. If you don't want to copy-paste them, you can put them in a
> separate file, which you open in the .mli and the .ml.

In the first place, I don't want to write those .mli files as the 
compiler can infer them for me automatically (I'm lazy).

And I understand that some people need to cast these type signatures
in stone and constrain them in a different way than the default
inferred by the compiler, for large projects.

Regards,
F.