From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <rich@annexia.org>
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 5E70E7F249
	for <caml-list@sympa.inria.fr>; Tue, 30 Oct 2012 12:03:07 +0100 (CET)
Received-SPF: None (mail4-smtp-sop.national.inria.fr: no sender
  authenticity information available from domain of
  rich@annexia.org) identity=pra; client-ip=80.68.91.176;
  receiver=mail4-smtp-sop.national.inria.fr;
  envelope-from="rich@annexia.org";
  x-sender="rich@annexia.org"; x-conformance=sidf_compatible
Received-SPF: Pass (mail4-smtp-sop.national.inria.fr: domain of
  rich@annexia.org designates 80.68.91.176 as permitted sender)
  identity=mailfrom; client-ip=80.68.91.176;
  receiver=mail4-smtp-sop.national.inria.fr;
  envelope-from="rich@annexia.org";
  x-sender="rich@annexia.org"; 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@furbychan.cocan.org) identity=helo;
  client-ip=80.68.91.176;
  receiver=mail4-smtp-sop.national.inria.fr;
  envelope-from="rich@annexia.org";
  x-sender="postmaster@furbychan.cocan.org";
  x-conformance=sidf_compatible
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AkYQAM2yj1BQRFuw/2dsb2JhbABEhS8jhhq2RQSBAIEIgh4BAQU6PxALGBwSFCghiB2sQZAthU9QhVY2hUZhA5VzkEOCbw
X-IronPort-AV: E=Sophos;i="4.80,679,1344204000"; 
   d="scan'208";a="160870294"
Received: from furbychan.cocan.org ([80.68.91.176])
  by mail4-smtp-sop.national.inria.fr with ESMTP/TLS/AES256-SHA; 30 Oct 2012 12:03:06 +0100
Received: from rich by furbychan.cocan.org with local (Exim 4.72)
	(envelope-from <rich@annexia.org>)
	id 1TT9b5-0003MH-MC; Tue, 30 Oct 2012 11:03:03 +0000
Date: Tue, 30 Oct 2012 11:03:03 +0000
From: "Richard W.M. Jones" <rich@annexia.org>
To: Francois Berenger <berenger@riken.jp>
Cc: Anton Lavrik <alavrik@piqi.org>, caml-list <caml-list@inria.fr>
Message-ID: <20121030110303.GB12862@annexia.org>
References: <508F22BD.7010103@riken.jp>
 <CACX4useWCnu4tg2jAkSx=K=38BaHimgZWRFPF1Jyj5gw+YHAbg@mail.gmail.com>
 <508F9B56.8090806@riken.jp>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <508F9B56.8090806@riken.jp>
User-Agent: Mutt/1.5.20 (2009-06-14)
Subject: Re: [Caml-list] Why should I use .mli files?

On Tue, Oct 30, 2012 at 06:18:14PM +0900, Francois Berenger wrote:
> In C, I used a tool call cproto to extract header files out of my .c
> implementation code. Then, I just snipped out some parts of the header
> I didn't want to make public, if I remember well.
> That was not perfect, but at least I did not have to maintain two
> files at the same time.

ocamlc -i can do the same thing.

Maintaining two files can occasionally be annoying, but the benefits
of having a well-defined, well-documented interface between your
modules should not be minimized.

However it doesn't sound as if your project involves large amounts of
people working on the code base over a long period of time, so perhaps
maintainability is not so important for you.

Rich.

-- 
Richard Jones
Red Hat