From: "Nicolas Pouillard" <nicolas.pouillard@gmail.com>
To: "Caml List" <caml-list@inria.fr>, "Aleksey Nogin" <nogin@metaprl.org>
Subject: Re: [Caml-list] Camlp4 3.10 - antiquotations in keyword position?
Date: Tue, 24 Apr 2007 02:12:53 +0200 [thread overview]
Message-ID: <cd67f63a0704231712i3864bce3hf210c9b8ac041b1c@mail.gmail.com> (raw)
In-Reply-To: <462D4A54.6010700@metaprl.org>
On 4/24/07, Aleksey Nogin <nogin@metaprl.org> wrote:
> In 3.09 we used to allow defining "infix" keywords by using
> antiquotations in inside the "EXTEND" and "DELETE_RULE" directives as
> follows:
>
[...]
> This does not seem to be supported in 3.10. Is there some other way to
> achieve a similar effect in 3.10? Thanks!
You can try something like
.... op = KEYWORD $x$ ...
Regards,
--
Nicolas Pouillard
next prev parent reply other threads:[~2007-04-24 0:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-24 0:07 Aleksey Nogin
2007-04-24 0:12 ` Nicolas Pouillard [this message]
2007-04-26 16:25 ` [Caml-list] " 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=cd67f63a0704231712i3864bce3hf210c9b8ac041b1c@mail.gmail.com \
--to=nicolas.pouillard@gmail.com \
--cc=caml-list@inria.fr \
--cc=nogin@metaprl.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;
as well as URLs for NNTP newsgroup(s).