From: "forum@x9c.fr" <forum@x9c.fr>
To: Marek Kubica <marek@xivilization.net>
Cc: "forum@x9c.fr" <forum@x9c.fr>, caml-list@inria.fr
Subject: Re: [Caml-list] Preferred layout for new packages
Date: Wed, 14 Nov 2012 19:00:45 +0100 [thread overview]
Message-ID: <6973F6F3-317F-46A6-A53D-8796FB33E679@x9c.fr> (raw)
In-Reply-To: <20121114180012.68bf06df@xivilization.net>
Le 14 nov. 2012 à 18:00, Marek Kubica a écrit :
> On Wed, 14 Nov 2012 09:42:09 -0500
> Edgar Friendly <thelema314@gmail.com> wrote:
>
>> (…)
>
> I actually like test extraction frameworks, tools like nose and py.test
> have made writing tests with Python much nicer, that's why I'm somehow
> unimpressed how verbose OUnit is. But having the test code in a comment
> seems ugly to me. Maybe there could be some CamlP4 hack to exclude it
> on normal compilation?
Being not found of extraction myself, I made another proposal in the
latest revision of Kaputt: instead of using mli/ml file couples, I tend to
now use mli/ml/mlt file triples. In this setting, the mlt file simply contains
the code related to tests. Then, at compilation a small camlp4 preprocessor
concatenates the contents of ml and mlt files before actual compilation.
My understanding is that it reconciles two antagonistic goals:
- separate application code from test code;
- allow test code to access unexported elements.
I would be glad to hear what people think of this scheme, independently
of the Kaputt library itself (which I am not advertising here). One can read
more in section 3.3 of the manual available at:
http://kaputt.x9c.fr/downloads.html
Regards,
Xavier Clerc
next prev parent reply other threads:[~2012-11-14 18:00 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-14 11:43 Marek Kubica
2012-11-14 14:41 ` Török Edwin
2012-11-14 16:36 ` Marek Kubica
2012-11-15 1:20 ` Francois Berenger
2012-11-14 14:42 ` Edgar Friendly
2012-11-14 17:00 ` Marek Kubica
2012-11-14 18:00 ` forum [this message]
2012-11-15 9:00 ` Philippe Veber
2012-11-14 18:17 ` Martin Jambon
2012-11-14 18:48 ` Markus Mottl
2012-11-14 19:35 ` Martin Jambon
2012-11-15 6:36 ` Cedric Cellier
2012-11-15 7:24 ` Marek Kubica
2012-11-15 9:17 ` rixed
[not found] <fa.38rAsBvHd+quECbtcbTH9HW+J6U@ifi.uio.no>
[not found] ` <fa.YCrkHurCi6yY5s0Qg1r6uLWNQdY@ifi.uio.no>
[not found] ` <fa.oeqp0ymFFL+o76ut/LjBeQhUcjQ@ifi.uio.no>
[not found] ` <fa.pEDV80ILnW8x1YQyKuF3NBsK3Kw@ifi.uio.no>
[not found] ` <fa.LQofvqHUt8xj1kM1rvmQZF+Z7rw@ifi.uio.no>
2012-11-15 8:13 ` vincent.hugot
2012-11-15 8:31 ` Francois Berenger
2012-11-15 9:20 ` rixed
2012-11-15 17:22 ` Aleksey Nogin
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=6973F6F3-317F-46A6-A53D-8796FB33E679@x9c.fr \
--to=forum@x9c.fr \
--cc=caml-list@inria.fr \
--cc=marek@xivilization.net \
/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