From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <berenger@riken.jp>
X-Original-To: caml-list@sympa.inria.fr
Delivered-To: caml-list@sympa.inria.fr
Received: from mail2-relais-roc.national.inria.fr (mail2-relais-roc.national.inria.fr [192.134.164.83])
	by sympa.inria.fr (Postfix) with ESMTPS id 4F3E37FE50
	for <caml-list@sympa.inria.fr>; Mon,  3 Jun 2013 12:46:59 +0200 (CEST)
Received-SPF: None (mail2-smtp-roc.national.inria.fr: no sender
  authenticity information available from domain of
  berenger@riken.jp) identity=pra; client-ip=134.160.33.162;
  receiver=mail2-smtp-roc.national.inria.fr;
  envelope-from="berenger@riken.jp";
  x-sender="berenger@riken.jp"; x-conformance=sidf_compatible
Received-SPF: Pass (mail2-smtp-roc.national.inria.fr: domain of
  berenger@riken.jp designates 134.160.33.162 as permitted
  sender) identity=mailfrom; client-ip=134.160.33.162;
  receiver=mail2-smtp-roc.national.inria.fr;
  envelope-from="berenger@riken.jp";
  x-sender="berenger@riken.jp"; x-conformance=sidf_compatible;
  x-record-type="v=spf1"
Received-SPF: Pass (mail2-smtp-roc.national.inria.fr: domain of
  postmaster@postman.riken.jp designates 134.160.33.162 as
  permitted sender) identity=helo; client-ip=134.160.33.162;
  receiver=mail2-smtp-roc.national.inria.fr;
  envelope-from="berenger@riken.jp";
  x-sender="postmaster@postman.riken.jp";
  x-conformance=sidf_compatible; x-record-type="v=spf1"
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AqMFAMLwq1GGoCGigGdsb2JhbABahnWJFgGkPIsFgm2BFQ4BAQkWBz6CGwgBAQUjFUABEAsYAgIFFgsCAgkDAgECAUUGDQEHAQGFcoIXqWiRCoEmjgEHgkQOgQYDiR6OIIYejHqBRg
X-IPAS-Result: AqMFAMLwq1GGoCGigGdsb2JhbABahnWJFgGkPIsFgm2BFQ4BAQkWBz6CGwgBAQUjFUABEAsYAgIFFgsCAgkDAgECAUUGDQEHAQGFcoIXqWiRCoEmjgEHgkQOgQYDiR6OIIYejHqBRg
X-IronPort-AV: E=Sophos;i="4.87,790,1363129200"; 
   d="scan'208";a="19977408"
Received: from postman2.riken.jp (HELO postman.riken.jp) ([134.160.33.162])
  by mail2-smtp-roc.national.inria.fr with ESMTP; 03 Jun 2013 03:28:03 +0200
Received: from postman.riken.jp (postman2.riken.jp [127.0.0.1])
	by postman.riken.jp (Postfix) with SMTP id C9C8B1260636;
	Mon,  3 Jun 2013 10:28:00 +0900 (JST)
Received: from [172.27.98.103] (rikad98.riken.jp [134.160.214.98])
	by postman.riken.jp (Postfix) with ESMTPA id 3C48D127005B;
	Mon,  3 Jun 2013 10:28:00 +0900 (JST)
Message-ID: <51ABF120.2060002@riken.jp>
Date: Mon, 03 Jun 2013 10:28:00 +0900
From: Francois Berenger <berenger@riken.jp>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130510 Thunderbird/17.0.6
MIME-Version: 1.0
To: oliver <oliver@first.in-berlin.de>
CC: caml-list@inria.fr
References: <51A81C67.50902@riken.jp> <87bo7rogub.fsf@gmail.com> <51A84283.80309@riken.jp> <20130531231308.GC6483@siouxsie>
In-Reply-To: <20130531231308.GC6483@siouxsie>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-PMX-Version: 6.0.0.2142326, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2013.6.3.11518
Subject: Re: [Caml-list] automatic extaction of the .mli (and a little more)
 from the .ml

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.