From: Oliver Bandel <oliver@first.in-berlin.de>
To: Didier Cassirame <didier.cassirame@gmail.com>
Cc: Francois Berenger <berenger@riken.jp>, caml-list <caml-list@inria.fr>
Subject: Re: [Caml-list] Why should I use .mli files?
Date: Wed, 31 Oct 2012 22:30:07 +0100 [thread overview]
Message-ID: <94654D4E-20EE-4690-91EA-9BBD1CF111C5@first.in-berlin.de> (raw)
In-Reply-To: <CA+Lkvyr=e9iXpcUhwPv+G90sq4zqTAKxJPNOAi-N284LYkNtyQ@mail.gmail.com>
Am 30.10.2012 um 16:52 schrieb Didier Cassirame <didier.cassirame@gmail.com>:
>
> Thinking about it, there's at least one case where mli files are not so useful: When you have several modules which must all comply with a certain module type. In that case, all the mli files would be identical, and a modification of the module type would necessitate to change all the .mli.
Sounds like you reformulated an advantagenas being a disadvantage.
If someone changes a type of a module by accident, it,will pop up as
problem.
Also I wonder, if a type that is used by other modules
might not also need to change the mplementation.
I think it depends on the kind of change.
Maybe you can provide an example.
Somehow the discussion looks a bit like
changing the interface often to be a sport
for programmers.
I remember times, when it was a good idea tomchange interfaces
as seldom as possible.
But modern times bring modern behaviour.
Maybe soon there will be a fast-interface-change contest.
One big advantage of mli-files is, to carve the interface in stone.
So even I mostly used OCaml only for my own small projects,
in a big project with many developers, it would make sense
that the team will plan the interface, and when the decisionis done,
the project leader or a certain person who is responsible for
mantaining the nterfaces, will create the file and has
rw-permissions, and the other developers only have group-readability.
So then they have to use the interface as it was agreed upon.
And the one who wants to implement furthe things can omit the mli file for a while,
but if the code does not compile with the official mli-file,
the code will be rejected.
I think this is a valuable tool, the mli can provide clear interfaces,
and this is working well wirh many developers.
And if changing of intefcüace really can't be avoided,
it will need a team meeting on intercace change.
Thats totally different to lets-change-they-interface-as-often-as-possible
contest behaviour.
Best wishes,
Oliver
next prev parent reply other threads:[~2012-10-31 21:29 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-30 0:43 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
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 [this message]
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
[not found] <fa.4zzWyGZIo+GsGOz7cSC34yWTunY@ifi.uio.no>
2012-10-31 14:32 ` Radu Grigore
[not found] ` <fa.pEEaqh4bLDLiRdYkCRHvi9787TQ@ifi.uio.no>
[not found] ` <fa.JtZOlOTbNCp6rOoRnHhKEARwLDQ@ifi.uio.no>
[not found] ` <fa.s4gDOdOTZVbthjceZ5OEMxHiH90@ifi.uio.no>
[not found] ` <fa.rfsHI3X48Zri1S2pu1SEFowmDZg@ifi.uio.no>
[not found] ` <fa.KulHINoVpgjN1uI63QvwcxoNuiY@ifi.uio.no>
2012-11-01 11:38 ` Radu Grigore
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=94654D4E-20EE-4690-91EA-9BBD1CF111C5@first.in-berlin.de \
--to=oliver@first.in-berlin.de \
--cc=berenger@riken.jp \
--cc=caml-list@inria.fr \
--cc=didier.cassirame@gmail.com \
/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