From: Alain Frisch <alain@frisch.fr>
To: caml-list <caml-list@inria.fr>
Subject: Re: [wg-camlp4] [Caml-list] Working Group: the future of syntax extensions in OCaml, after camlp4
Date: Mon, 28 Jan 2013 13:17:06 +0100 [thread overview]
Message-ID: <51066C42.9040502@frisch.fr> (raw)
In-Reply-To: <51066BCA.1020201@frisch.fr>
(Sorry for the noise, I did not realize that caml-list was still in Cc:.
Please continue the discussion on wg-camlp4 only!)
On 01/28/2013 01:15 PM, Alain Frisch wrote:
> 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
>
> _______________________________________________
> wg-camlp4 mailing list
> wg-camlp4@lists.ocaml.org
> http://lists.ocaml.org/listinfo/wg-camlp4
next prev parent reply other threads:[~2013-01-28 12:17 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
2013-01-28 12:17 ` Alain Frisch [this message]
2013-02-03 14:01 ` 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=51066C42.9040502@frisch.fr \
--to=alain@frisch.fr \
--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;
as well as URLs for NNTP newsgroup(s).