From: Alex Baretta <alex@barettadeit.com>
To: Hendrik Tews <tews@tcs.inf.tu-dresden.de>
Cc: Ocaml <caml-list@inria.fr>
Subject: Re: [Caml-list] Camlp4 with traditional syntax (was: Camlp4 documentation)
Date: Mon, 21 Feb 2005 13:28:25 +0100 [thread overview]
Message-ID: <4219D3E9.80003@barettadeit.com> (raw)
In-Reply-To: <rlll9lmr64.fsf@ithif59.inf.tu-dresden.de>
Hendrik Tews wrote:
> Alex Baretta <alex@barettadeit.com> writes:
>
> There is one more issue with Camlp4: it does not allow for quotations
> to expand to generic syntactic elements. Often, I use quotations which
> expand to module definitions. I had to implement my own quotation
> expander, bypassing the limitations of Camlp4 to achieve this.
>
> I don't quite understand, what's wrong with
>
> let me = <:module_expr< struct $ list of module def's $ end >>
> in
> <:str_item< module $some_name$ = $me$ >>
We use quotation expanders to embed completely different languages, such
as SQL, within Ocaml code. Specifically, the SQL quotation expander
compiles SQL code to an Ocaml module. CamlP4 signals an error because
quotations are only meant to be used as expressions or as patterns,
IIRC. Anyhow, the solution is either to use ocpp rather than camlp4 as a
preprocessor (ocpp is less picky), or to write one's own quotation
preprocessor. We use both techniques depending on the context.
Alex
--
*********************************************************************
http://www.barettadeit.com/
Baretta DE&IT
A division of Baretta SRL
tel. +39 02 370 111 55
fax. +39 02 370 111 54
Our technology:
The Application System/Xcaml (AS/Xcaml)
<http://www.asxcaml.org/>
The FreerP Project
<http://www.freerp.org/>
next prev parent reply other threads:[~2005-02-21 12:28 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-17 15:32 Immediate recursive functions Alex Baretta
2005-02-17 18:20 ` [Caml-list] " Marcin 'Qrczak' Kowalczyk
2005-02-17 19:00 ` Jason Hickey
2005-02-17 20:33 ` Alex Baretta
2005-02-17 19:18 ` Christian Szegedy
2005-02-17 20:36 ` Alex Baretta
2005-02-17 22:39 ` Camlp4 documentation (was: Immediate recursive functions) Martin Jambon
2005-02-17 23:30 ` [Caml-list] " Richard Jones
2005-02-17 23:51 ` Michael Walter
2005-02-18 0:51 ` Micha
2005-02-18 3:37 ` briand
2005-02-18 5:21 ` Oliver Bandel
2005-02-18 6:51 ` Johann Spies
2005-02-18 8:04 ` [Caml-list] Camlp4 documentation Alex Baretta
2005-02-18 8:54 ` Alex Cowie
2005-02-18 16:20 ` Camlp4 with traditional syntax (was: Camlp4 documentation) Hendrik Tews
2005-02-18 16:28 ` [Caml-list] " Alex Baretta
2005-02-18 22:36 ` Hendrik Tews
2005-02-21 12:28 ` Alex Baretta [this message]
2005-02-21 12:55 ` Bardur Arantsson
2005-02-21 15:22 ` [Caml-list] Camlp4 with traditional syntax Olivier Andrieu
2005-02-21 16:57 ` Bardur Arantsson
2005-02-18 18:43 ` [Caml-list] Camlp4 with traditional syntax (was: Camlp4 documentation) Martin Jambon
2005-02-18 22:41 ` Hendrik Tews
2005-02-22 10:29 ` Oliver Bandel
2005-02-22 23:32 ` Richard Jones
2005-02-23 0:01 ` Martin Jambon
2005-02-24 0:47 ` Oliver Bandel
2005-02-24 15:24 ` William D. Neumann
2005-02-18 8:14 ` [Caml-list] Camlp4 documentation (was: Immediate recursive functions) Robert M. Solovay
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=4219D3E9.80003@barettadeit.com \
--to=alex@barettadeit.com \
--cc=caml-list@inria.fr \
--cc=tews@tcs.inf.tu-dresden.de \
/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