caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: "Nicolas Pouillard" <nicolas.pouillard@gmail.com>
To: "Joel Reymont" <joelr1@gmail.com>
Cc: "Caml List" <caml-list@inria.fr>
Subject: Re: [Caml-list] Re: camlp4: Curried constructor error
Date: Mon, 2 Apr 2007 19:08:58 +0200	[thread overview]
Message-ID: <cd67f63a0704021008k707b7206s3384200621e67b5c@mail.gmail.com> (raw)
In-Reply-To: <60774EF5-3FB9-4D76-A349-5F86DEF00068@gmail.com>

On 4/2/07, Joel Reymont <joelr1@gmail.com> wrote:
> Foot in mouth. camlp4 in this case is doing compile-time expansion
> and cannot take runtime variables. Oh, well...

camlp4 always do compile-time expansion but you can insert code using
antiquotations.

<:expr< Some >> x      ==> WRONG
<:expr< Some $x$ >> ==> RIGHT

-- 
Nicolas Pouillard


      reply	other threads:[~2007-04-02 17:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-02 13:20 Joel Reymont
2007-04-02 13:26 ` Joel Reymont
2007-04-02 17:08   ` Nicolas Pouillard [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=cd67f63a0704021008k707b7206s3384200621e67b5c@mail.gmail.com \
    --to=nicolas.pouillard@gmail.com \
    --cc=caml-list@inria.fr \
    --cc=joelr1@gmail.com \
    /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;
as well as URLs for NNTP newsgroup(s).