From: Yoann Padioleau <padator@wanadoo.fr>
To: Romain Beauxis <toots@rastageeks.org>
Cc: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] [ANN] ocamltarzan 0.1
Date: Thu, 16 Apr 2009 14:27:48 -0500 [thread overview]
Message-ID: <87eivstn4b.fsf@aryx.cs.uiuc.edu> (raw)
In-Reply-To: <200904161515.21327.toots@rastageeks.org> (Romain Beauxis's message of "Thu\, 16 Apr 2009 15\:15\:21 -0400")
Romain Beauxis <toots@rastageeks.org> writes:
> Hi !
>
> Le Thursday 16 April 2009 14:15:40 Yoann Padioleau, vous avez écrit :
>> Sexplib and binprot by Jane Street are attractive, but they rely on
>> camlp4. I don't like camlp4. I like the metaprogramming facility it
>> offers but it has many disadvantages. So I've found a in-the-middle
>> solution where I use camlp4 to generate code (via the small script
>> ocamltarzan.ml), save the generated code in a file (e.g
>> test/foo_sexp.ml), which allows then to completely remove the
>> dependency to camlp4. Once the code has been generated, all
>> dependencies to camlp4 can be removed. If tomorrow an incompatible new
>> version of camlp4 arrives (e.g. camlp6 ...), your code will still
>> work, because it does not rely on the new behavior of this camlp4.
>> It's just regular plain good ocaml code.
>
> Shouldn't this just be a software/script independant from sexplib ?
It should, but the goal is to make it easier to use sexplib, and I've
found sexplib as it is right now a little bit complex to compile
(it requires ocamlfind, it requires type-conv, etc) by
default and too much tied to camlp4, hence the fork.
>
> On the one hand, such a technique could be useful for other code using other
> camlp4 extensions,
It's useful only for boilerplate related camlp4 extensions, and
except sexplib/binprot I don't know other such extensions.
> and on the other hand, this would avoid yet another fork...
sexplib has already been forked ?
>
>
> Romain
>
> _______________________________________________
> Caml-list mailing list. Subscription management:
> http://yquem.inria.fr/cgi-bin/mailman/listinfo/caml-list
> Archives: http://caml.inria.fr
> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
> Bug reports: http://caml.inria.fr/bin/caml-bugs
prev parent reply other threads:[~2009-04-16 19:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-16 18:15 Yoann Padioleau
2009-04-16 19:15 ` [Caml-list] " Romain Beauxis
2009-04-16 19:27 ` Yoann Padioleau [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=87eivstn4b.fsf@aryx.cs.uiuc.edu \
--to=padator@wanadoo.fr \
--cc=caml-list@yquem.inria.fr \
--cc=toots@rastageeks.org \
/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