From: Francois Berenger <berenger@riken.jp>
To: caml-list@inria.fr
Cc: romain.bardou@inria.fr
Subject: Re: [Caml-list] Re: Why should I use .mli files?
Date: Wed, 31 Oct 2012 10:03:22 +0900 [thread overview]
Message-ID: <509078DA.6010300@riken.jp> (raw)
In-Reply-To: <508FD6B3.9080407@inria.fr>
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.
next prev parent reply other threads:[~2012-10-31 1:03 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-30 0:43 [Caml-list] " Francois Berenger
2012-10-30 1:04 ` Peter Groves
2012-10-30 2:21 ` Francois Berenger
2012-10-30 1:15 ` malc
2012-10-30 2:24 ` Francois Berenger
2012-10-30 10:23 ` malc
2012-10-30 1:19 ` Daniel Bünzli
2012-10-30 2:36 ` Francois Berenger
2012-10-30 3:26 ` Anthony Tavener
2012-10-30 12:28 ` Daniel Bünzli
2012-10-31 0:53 ` Francois Berenger
2012-10-30 2:21 ` gallais @ ensl.org
2012-10-30 6:12 ` Anton Lavrik
2012-10-30 9:18 ` Francois Berenger
2012-10-30 10:01 ` Malcolm Matalka
2012-10-30 11:03 ` Richard W.M. Jones
2012-10-30 11:41 ` [Caml-list] " Hongbo Zhang
2012-10-30 13:31 ` Romain Bardou
2012-10-31 1:03 ` Francois Berenger [this message]
2012-10-31 1:44 ` Daniel Bünzli
2012-10-31 9:51 ` Oliver Bandel
2012-10-30 14:32 ` [Caml-list] " Oliver Bandel
2012-10-30 14:45 ` Anton Lavrik
2012-10-30 14:49 ` Oliver Bandel
2012-10-30 14:51 ` Didier Cassirame
2012-10-30 14:47 ` Romain Bardou
2012-10-30 16:06 ` Edgar Friendly
2012-10-30 16:21 ` Romain Bardou
2012-10-30 16:46 ` Edgar Friendly
2012-10-30 21:25 ` Gabriel Scherer
2012-10-30 22:18 ` Oliver Bandel
2012-10-31 9:25 ` Gabriel Scherer
2012-10-31 9:59 ` Daniel Bünzli
2012-10-31 13:22 ` Edgar Friendly
2012-10-31 13:38 ` Daniel Bünzli
2012-10-31 13:55 ` Edgar Friendly
2012-10-31 13:43 ` Gabriel Scherer
2012-11-01 0:38 ` Francois Berenger
2012-11-01 0:42 ` Edgar Friendly
2012-11-01 0:52 ` Francois Berenger
2012-11-01 2:06 ` Edgar Friendly
2012-11-01 2:37 ` Francois Berenger
2012-11-01 2:44 ` Jacques Garrigue
2012-11-01 7:45 ` Andreas Rossberg
2012-10-31 10:20 ` Alain Frisch
2012-10-31 13:50 ` Edgar Friendly
2012-10-31 15:12 ` Gabriel Scherer
2012-10-31 16:48 ` Edgar Friendly
2012-10-31 17:15 ` Gabriel Scherer
2012-10-31 19:05 ` Tiphaine Turpin
2012-10-30 7:43 ` Mike Lin
2012-10-30 15:52 ` Didier Cassirame
2012-10-30 15:56 ` Romain Bardou
2012-10-30 16:14 ` Didier Cassirame
2012-10-31 21:30 ` Oliver Bandel
2012-11-01 15:26 ` Didier Cassirame
2012-10-31 15:32 ` Alain Frisch
2012-10-31 17:32 ` Tiphaine Turpin
2012-10-31 21:40 ` Oliver Bandel
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=509078DA.6010300@riken.jp \
--to=berenger@riken.jp \
--cc=caml-list@inria.fr \
--cc=romain.bardou@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).