From: Malcolm Matalka <mmatalka@gmail.com>
To: Francois Berenger <berenger@riken.jp>
Cc: caml-list <caml-list@inria.fr>, oliver <oliver@first.in-berlin.de>
Subject: Re: [Caml-list] automatic extaction of the .mli (and a little more) from the .ml
Date: Mon, 3 Jun 2013 14:01:02 +0200 [thread overview]
Message-ID: <CAKziXDXnQOynH7McNg_p4dvBGxQ7SstpF6TUprXdeK_=9Yc-=g@mail.gmail.com> (raw)
In-Reply-To: <51ABF120.2060002@riken.jp>
[-- Attachment #1: Type: text/plain, Size: 1306 bytes --]
I don't think LEGOs are a good analogy here since they have a very well
defined and consistent interface :)
But I have never found handling mlis by hand to get in the way of program
evolution. If you take time in your interfaces program evolution should be
more about plugging in functionality in unique ways not changing interfaces
willy nilly.
On Jun 3, 2013 1:28 PM, "Francois Berenger" <berenger@riken.jp> wrote:
> On 06/01/2013 08:13 AM, oliver wrote:
> > [...]
>
>> Of course, especially if things are explored rather experimentally,
>> for example if there is a new field of topics, where the interface
>> is NOT clear in advance, starting with the mli-files might be rather
>> a show stopper.
>> if things are rather experimentally, starting with the ml-file might
>> be easier to handle.
>>
>
> This is exactly my case.
>
> Also, I grow programs organically because it is fun and motivating.
> It is like playing with LEGO.
>
>
> --
> Caml-list mailing list. Subscription management and archives:
> https://sympa.inria.fr/sympa/**arc/caml-list<https://sympa.inria.fr/sympa/arc/caml-list>
> Beginner's list: http://groups.yahoo.com/group/**ocaml_beginners<http://groups.yahoo.com/group/ocaml_beginners>
> Bug reports: http://caml.inria.fr/bin/caml-**bugs<http://caml.inria.fr/bin/caml-bugs>
>
[-- Attachment #2: Type: text/html, Size: 1858 bytes --]
next prev parent reply other threads:[~2013-06-03 12:01 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-31 3:43 Francois Berenger
2013-05-31 5:31 ` Malcolm Matalka
2013-05-31 6:26 ` Francois Berenger
2013-05-31 9:10 ` Romain Bardou
2013-06-03 1:33 ` Francois Berenger
2013-06-04 7:53 ` David Allsopp
2013-06-04 8:22 ` Alain Frisch
2013-06-04 8:54 ` David Allsopp
2013-06-04 8:22 ` Romain Bardou
2013-06-04 9:05 ` David Allsopp
2013-05-31 23:13 ` oliver
2013-06-03 1:28 ` Francois Berenger
2013-06-03 12:01 ` Malcolm Matalka [this message]
2013-05-31 15:21 ` [Caml-list] " Hongbo Zhang
2013-05-31 15:42 ` Yaron Minsky
2013-05-31 23:20 ` Jacques Le Normand
2013-06-01 9:12 ` Florent Monnier
2013-06-03 17:12 ` [Caml-list] " Alain Frisch
2013-06-04 0:30 ` Francois Berenger
2013-06-04 8:36 ` 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='CAKziXDXnQOynH7McNg_p4dvBGxQ7SstpF6TUprXdeK_=9Yc-=g@mail.gmail.com' \
--to=mmatalka@gmail.com \
--cc=berenger@riken.jp \
--cc=caml-list@inria.fr \
--cc=oliver@first.in-berlin.de \
/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