From: Hendrik Tews <tews@cs.ru.nl>
To: caml-list@inria.fr
Subject: Camlp4: example/parse_files.ml
Date: Thu, 3 Apr 2008 01:13:41 +0200 [thread overview]
Message-ID: <18420.4901.506029.744640@tandem.cs.ru.nl> (raw)
Hi,
I have a few questions to the parse_files example.
The example starts with building the parser and printer via the
following functor application
module Caml =
Camlp4.Printers.OCaml.Make
(Camlp4OCamlParser.Make
(Camlp4OCamlRevisedParser.Make
(Camlp4.OCamlInitSyntax.Make(Ast)(Gram)(Quotation))));;
1. Can I omit the printer functor if I am only interested in
parsing files (and not printing) and simplify to
module Caml =
Camlp4OCamlParser.Make
(Camlp4OCamlRevisedParser.Make
(Camlp4.OCamlInitSyntax.Make(Ast)(Gram)(Quotation)))
2. Ast, Gram, Quotation come from Camlp4.PreCast. Do I miss
something if I simplify further to
module Caml =
Camlp4OCamlParser.Make
(Camlp4OCamlRevisedParser.Make(Camlp4.PreCast.Syntax))
3. I looked into the registration of syntax extentions (Register
functors) and how the syntax extention callbacks are called
in Register.iter_and_take_callbacks. I have the impression
that in camlp4 not the above nested functor application is
performed but the Make functors are sequentially applied to
the same Syntax functor. Therefore, can I further simplify to
module Caml = Camlp4.PreCast.Syntax
let () =
let module M1 = Camlp4OCamlRevisedParser.Make(Caml) in
let module M2 = Camlp4OCamlParser.Make(Caml)
in
()
?
Bye,
Hendrik
next reply other threads:[~2008-04-02 23:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-02 23:13 Hendrik Tews [this message]
2008-04-03 15:32 ` [Caml-list] " Nicolas Pouillard
2008-04-03 21:24 ` Hendrik Tews
2008-04-04 13:40 ` Nicolas Pouillard
2008-04-04 14:01 ` Hendrik Tews
2008-04-04 14:19 ` Nicolas Pouillard
2008-04-04 21:30 ` Hendrik Tews
2008-04-05 10:00 ` Nicolas Pouillard
2008-04-07 7:31 ` Hendrik Tews
2008-04-07 8:10 ` Nicolas Pouillard
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=18420.4901.506029.744640@tandem.cs.ru.nl \
--to=tews@cs.ru.nl \
--cc=caml-list@inria.fr \
/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