From: Alain Frisch <alain@frisch.fr>
To: Gerd Stolpmann <info@gerd-stolpmann.de>
Cc: "Daniel Bünzli" <daniel.buenzli@erratique.ch>,
caml-list <caml-list@inria.fr>,
wg-camlp4@lists.ocaml.org, "Leo P White" <lpw25@cam.ac.uk>,
"Anil Madhavapeddy" <avsm2@cl.cam.ac.uk>
Subject: Re: AW: [Caml-list] Working Group: the future of syntax extensions in OCaml, after camlp4
Date: Mon, 28 Jan 2013 13:15:06 +0100 [thread overview]
Message-ID: <51066BCA.1020201@frisch.fr> (raw)
In-Reply-To: <1359044659.30715.4@samsung>
On 01/24/2013 05:24 PM, Gerd Stolpmann wrote:
> It's used in the tool, but only for stream parsing. I could also
> distribute the already-preprocessed file (and maybe I'll do so in the
> next release).
>
> Stream parsing is certainly one of the topics to discuss.
I've no idea how widely stream parsing is used. Has anyone some
intuition about this?
Stream parsers probably fall in the same category as bitstring or sedlex
(custom notions of pattern matching). It seems that stream parsers
(which I'm not familiar with) require to be able to write expressions
within "left-hand sides", which might require special support. Or maybe
the whole left-hand sides should just be quotations.
Anyway, for a basic infrastructure tool such as ocamlfind, I'd probably
advocate for a "manual" solution which works out of the box with a basic
OCaml installation (ocamlyacc or manual top-down parser). Gerd: does
that sound reasonable to you?
Alain
next prev parent reply other threads:[~2013-01-28 12:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-24 14:31 Alain Frisch
2013-01-24 15:52 ` Török Edwin
2013-01-24 15:56 ` Ashish Agarwal
2013-01-24 16:03 ` Esther Baruk
2013-01-24 15:57 ` Daniel Bünzli
2013-01-24 16:24 ` AW: " Gerd Stolpmann
2013-01-28 12:15 ` Alain Frisch [this message]
2013-01-28 12:17 ` [wg-camlp4] " Alain Frisch
2013-02-03 14:01 ` AW: " Jon Harrop
2013-02-03 14:38 ` Simon Cruanes
2013-01-24 16:16 ` rixed
2013-01-24 17:08 ` Alain Frisch
2013-01-24 18:06 ` Jacques Carette
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=51066BCA.1020201@frisch.fr \
--to=alain@frisch.fr \
--cc=avsm2@cl.cam.ac.uk \
--cc=caml-list@inria.fr \
--cc=daniel.buenzli@erratique.ch \
--cc=info@gerd-stolpmann.de \
--cc=lpw25@cam.ac.uk \
--cc=wg-camlp4@lists.ocaml.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).