caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: "Daniel Bünzli" <daniel.buenzli@erratique.ch>
To: Benjamin Canou <benjamin.canou@gmail.com>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] OCamlPro Highlights: Dec 2013 & Jan 2014
Date: Thu, 6 Feb 2014 14:06:22 +0100	[thread overview]
Message-ID: <4EE76A0DCE894248BA68BF2D57EBE595@erratique.ch> (raw)
In-Reply-To: <52F3728A.1010408@gmail.com>

Le jeudi, 6 février 2014 à 12:31, Benjamin Canou a écrit :
> Thanks for your reactive input. OCamlRes is still in design stage (cf.
> the version number) and I published it for gathering potential usages  
> and users so it is very welcome. About the lack of mli, the  
> implementation is actually ocamldoc'ed, so a `make doc` and a good  
> browser should make for a reasonable substitute until the interface is  
> well frozen in an mli.

The problem of figuring out which functions in the ml are part of the interface and which are not is still solved by this approach (not to mention that you may expose representations you'd like to hide later). Besides you don't get any feel on how the interface is organized type-wise which is one of the quickest way to evaluate the brokenness or beauty of an api.  

As soon as I see a lack of mli files in a published package, I disregard. I equate it with lack of design.  

Best,

Daniel



  reply	other threads:[~2014-02-06 13:06 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-05 17:31 Fabrice Le Fessant
2014-02-06  9:43 ` Romain Bardou
2014-02-06 10:25   ` Malcolm Matalka
2014-02-06 10:57     ` Anil Madhavapeddy
2014-02-06 11:31   ` Benjamin Canou
2014-02-06 13:06     ` Daniel Bünzli [this message]
2014-02-06 16:07       ` Benjamin Canou
2014-02-07  1:36         ` Benjamin Canou
2014-02-07 10:48           ` Daniel Bünzli
2014-02-06 10:53 ` Pierre-Étienne Meunier
2014-02-07  9:15   ` Alain Frisch

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=4EE76A0DCE894248BA68BF2D57EBE595@erratique.ch \
    --to=daniel.buenzli@erratique.ch \
    --cc=benjamin.canou@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).