caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Paolo Donadeo <p.donadeo@gmail.com>
To: OCaml mailing list <caml-list@inria.fr>
Subject: Re: [Caml-list] module alias in a .mli file
Date: Mon, 19 Nov 2012 13:44:23 +0100	[thread overview]
Message-ID: <CAPzAKVBW9ZPS2gnkTCD9zPyf_Hf+-8p07m4bopJv8hJcibs4+g@mail.gmail.com> (raw)
In-Reply-To: <CAK=fH+jVxh_6fuTXB==TYOYovfb+sdFpYsjL8DWuTErRwnyKug@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2051 bytes --]

Actually this is not true, Martin explained how. :-)


-- 
Paolo
Sent by Gmail from Android
Il giorno 19/nov/2012 11:35, "David House" <dhouse@janestreet.com> ha
scritto:

> Annoyingly though, there is no way to create a module alias in an mli.
>
> If, in an ml file, you have to refer often to
> Some_very_long_module_name, it can quite convenient to define an alias
> by doing "module Mod = Some_very_long_module_name" (or, locally, "let
> module Mod = Some_very_long_module_name in"). But there is no way of
> doing this in an mli: you have to use the long name every time.
>
> This is especially annoying if you have some big type that you want to
> expose in the mli. You really just want to copy-paste out of the ml
> file and stick it into the mli, but then you have to expand all the
> module aliases. (It's just a couple of goes with M-%, but still...)
>
> On Mon, Nov 19, 2012 at 6:36 AM, Francois Berenger <berenger@riken.jp>
> wrote:
> > 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. :)
> >
> >
> >
> >
> > --
> > Caml-list mailing list.  Subscription management and archives:
> > https://sympa.inria.fr/sympa/arc/caml-list
> > Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
> > Bug reports: http://caml.inria.fr/bin/caml-bugs
>
> --
> Caml-list mailing list.  Subscription management and archives:
> https://sympa.inria.fr/sympa/arc/caml-list
> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
> Bug reports: http://caml.inria.fr/bin/caml-bugs
>

[-- Attachment #2: Type: text/html, Size: 3164 bytes --]

  reply	other threads:[~2012-11-19 12:44 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-19  5:29 Francois Berenger
2012-11-19  6:02 ` Martin Jambon
2012-11-19  6:36   ` Francois Berenger
2012-11-19 10:35     ` David House
2012-11-19 12:44       ` Paolo Donadeo [this message]
2012-11-19 15:46         ` Tiphaine Turpin
2012-11-19 14:51           ` David House
2012-11-20  1:38           ` Francois Berenger
2012-11-20  1:57             ` Francois Berenger
2012-11-19  6:03 ` Wojciech Meyer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAPzAKVBW9ZPS2gnkTCD9zPyf_Hf+-8p07m4bopJv8hJcibs4+g@mail.gmail.com \
    --to=p.donadeo@gmail.com \
    --cc=caml-list@inria.fr \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).