From: Martin Jambon <martin.jambon@ens-lyon.org>
To: tmp123 <tmp123@menta.net>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Which camlp variant?
Date: Wed, 7 Nov 2007 19:20:55 +0100 (CET) [thread overview]
Message-ID: <Pine.LNX.4.64.0711071919540.13988@martin.ec.wink.com> (raw)
In-Reply-To: <47320337.3030102@menta.net>
On Wed, 7 Nov 2007, tmp123 wrote:
> Hello,
>
> The module "pa_log" proposed by Mr. Conway seems very near to the objective
> of my previuos post.
>
> The objective now is expand a line like: DEBUG 3 "%d\n" 14
> to: if debug.val then logint 3 ( fun () -> Printf.printf "%d\" 14 ) else ();
>
> However, it is necessary to migrate the module to new camlpx .
>
> Please, could someone give any advice about the current options: camlp4 or
> camlp5? PreCast? Functorial?
sed?
:-)
Martin
--
http://wink.com/profile/mjambon
http://martin.jambon.free.fr
next prev parent reply other threads:[~2007-11-07 18:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-07 18:25 tmp123
2007-11-07 18:20 ` Martin Jambon [this message]
2007-11-08 0:24 ` [Caml-list] " Nicolas Pouillard
2007-11-08 0:48 ` Christopher L Conway
[not found] ` <4a051d930711071716n7c88dde9t7dfe4c190ea3a90d@mail.gmail.com>
2007-11-09 11:34 ` tmp123
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=Pine.LNX.4.64.0711071919540.13988@martin.ec.wink.com \
--to=martin.jambon@ens-lyon.org \
--cc=caml-list@inria.fr \
--cc=tmp123@menta.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