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 5ED7B7EE20
	for <caml-list@sympa.inria.fr>; Mon, 19 Nov 2012 07:36:44 +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.175;
  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.175 as permitted
  sender) identity=mailfrom; client-ip=134.160.33.175;
  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.175 as
  permitted sender) identity=helo; client-ip=134.160.33.175;
  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: AqgBALDSqVCGoCGvmWdsb2JhbABFhiC5OoJzgRQBAQEBAQgLCwcUJ4IeAQEFIxVAARALGAICBRYLAgIJAwIBAgFFEwEHAQGICa09kgWBIosSg3qBEwOIWI0khWuNVg
X-IronPort-AV: E=Sophos;i="4.83,276,1352070000"; 
   d="scan'208";a="162936732"
Received: from postman3.riken.jp (HELO postman.riken.jp) ([134.160.33.175])
  by mail4-smtp-sop.national.inria.fr with ESMTP; 19 Nov 2012 07:36:43 +0100
Received: from postman.riken.jp (postman3.riken.jp [127.0.0.1])
	by postman.riken.jp (Postfix) with SMTP id A1AA038380BB;
	Mon, 19 Nov 2012 15:36:40 +0900 (JST)
Received: from [172.27.98.103] (rikad98.riken.jp [134.160.214.98])
	by postman.riken.jp (Postfix) with ESMTPA id 3683D3820233;
	Mon, 19 Nov 2012 15:36:40 +0900 (JST)
Message-ID: <50A9D378.4020403@riken.jp>
Date: Mon, 19 Nov 2012 15:36:40 +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
CC: caml-list@inria.fr
References: <50A9C3BB.2050900@riken.jp> <50A9CB66.1020207@ens-lyon.org>
In-Reply-To: <50A9CB66.1020207@ens-lyon.org>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-PMX-Version: 5.6.0.2009776, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2012.11.19.62115
Subject: Re: [Caml-list] module alias in a .mli file

On 11/19/2012 03:02 PM, Martin Jambon wrote:
> On Sun 18 Nov 2012 09:29:31 PM PST, Francois Berenger wrote:
>> Hello,
>>
>> Here is my stupid question of the day:
>> can't I declare the following in a .mli file?
>>
>> module V3 = Vector3
>
> No, because "= Vector3" specifies an implementation.
> An mli file is a module interface, and module interfaces never contain
> implementations.
>
> However, you may want to do this, which does what it says:
>
>   module V3 : module type of Vector3

Thanks a lot! That's exactly what I needed. :)