From: Jeremy Yallop <jeremy.yallop@ed.ac.uk>
To: "forum@x9c.fr" <forum@x9c.fr>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] [ANN] Kaputt 1.0 alpha
Date: Tue, 25 Nov 2008 09:55:59 +0000 [thread overview]
Message-ID: <492BCBAF.6080607@ed.ac.uk> (raw)
In-Reply-To: <7DDCBA63-92C1-4575-A326-DEED2BD33CE9@x9c.fr>
forum@x9c.fr wrote:
> Le 24 nov. 08 à 22:49, Christophe Raffalli a écrit :
>> Or a camlp4 extension to build the intended function(s) by induction on
>> the type definition.
>> you could include that as part of deriving
>> (http://code.google.com/p/deriving/)
>
> Good idea.
> I would regard a deriving-based "class" for generation
> of test cases as a very useful enhancement.
>
> However, I do not know the policy of the "deriving"
> developers. Would they accept a "class" relying on
> a library besides the standard library ?
Yes: such contributions would be welcome. It wouldn't be necessary for
users of "deriving" to link in your library unless they were actually
using it.
It would also be possible to distribute your "class" separately from
deriving. The design of deriving (based on the underlying camlp4
facility for loading object files dynamically) allows classes (i.e. code
generators) to be loaded at runtime, so there's no need to modify the
whole program just to add a new class.
Jeremy.
--
The University of Edinburgh is a charitable body, registered in
Scotland, with registration number SC005336.
prev parent reply other threads:[~2008-11-25 9:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-23 20:57 barista
2008-11-23 21:30 ` [Caml-list] " Stefano Zacchiroli
2008-11-23 23:14 ` forum
2008-11-23 23:22 ` forum
2008-11-24 16:52 ` Yoann Padioleau
2008-11-24 17:08 ` Sylvain Le Gall
2008-11-24 19:13 ` [Caml-list] " forum
2008-11-24 21:49 ` Christophe Raffalli
2008-11-24 22:05 ` Yoann Padioleau
2008-11-24 22:52 ` forum
2008-11-25 9:55 ` Jeremy Yallop [this message]
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=492BCBAF.6080607@ed.ac.uk \
--to=jeremy.yallop@ed.ac.uk \
--cc=caml-list@inria.fr \
--cc=forum@x9c.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