From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <alain@frisch.fr>
X-Original-To: caml-list@sympa.inria.fr
Delivered-To: caml-list@sympa.inria.fr
Received: from mail3-relais-sop.national.inria.fr (mail3-relais-sop.national.inria.fr [192.134.164.104])
	by sympa.inria.fr (Postfix) with ESMTPS id 5D1EB7EEAF
	for <caml-list@sympa.inria.fr>; Mon, 28 Jan 2013 13:15:09 +0100 (CET)
Received-SPF: None (mail3-smtp-sop.national.inria.fr: no sender
  authenticity information available from domain of
  alain@frisch.fr) identity=pra; client-ip=193.252.23.215;
  receiver=mail3-smtp-sop.national.inria.fr;
  envelope-from="alain@frisch.fr"; x-sender="alain@frisch.fr";
  x-conformance=sidf_compatible
Received-SPF: None (mail3-smtp-sop.national.inria.fr: no sender
  authenticity information available from domain of
  alain@frisch.fr) identity=mailfrom; client-ip=193.252.23.215;
  receiver=mail3-smtp-sop.national.inria.fr;
  envelope-from="alain@frisch.fr"; x-sender="alain@frisch.fr";
  x-conformance=sidf_compatible
Received-SPF: None (mail3-smtp-sop.national.inria.fr: no sender
  authenticity information available from domain of
  postmaster@msa.smtpout.orange.fr) identity=helo;
  client-ip=193.252.23.215;
  receiver=mail3-smtp-sop.national.inria.fr;
  envelope-from="alain@frisch.fr";
  x-sender="postmaster@msa.smtpout.orange.fr";
  x-conformance=sidf_compatible
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ao4AAHJrBlHB/BfXkWdsb2JhbABFgzi3TINsDgEBAQEJCwsHFAMkgh4BAQU4QAEQCw4KCRYPCQMCAQIBRQYNAQcBAReHer8skSUDlg2Fa41V
X-IPAS-Result: Ao4AAHJrBlHB/BfXkWdsb2JhbABFgzi3TINsDgEBAQEJCwsHFAMkgh4BAQU4QAEQCw4KCRYPCQMCAQIBRQYNAQcBAReHer8skSUDlg2Fa41V
X-IronPort-AV: E=Sophos;i="4.84,551,1355094000"; 
   d="scan'208";a="228295"
Received: from msa06.smtpout.orange.fr (HELO msa.smtpout.orange.fr) ([193.252.23.215])
  by mail3-smtp-sop.national.inria.fr with ESMTP; 28 Jan 2013 13:17:01 +0100
Received: from [192.168.1.105] ([90.2.82.74])
	by mwinf5d35 with ME
	id tQF61k0101cCdve03QF79W; Mon, 28 Jan 2013 13:15:08 +0100
Message-ID: <51066BCA.1020201@frisch.fr>
Date: Mon, 28 Jan 2013 13:15:06 +0100
From: Alain Frisch <alain@frisch.fr>
User-Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
To: Gerd Stolpmann <info@gerd-stolpmann.de>
CC: =?ISO-8859-15?Q?Daniel_B=FCnzli?= <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>
References: <510145A5.6030807@frisch.fr> <90C5BC201F264C4C902B4E7897660042@erratique.ch> <1359044659.30715.4@samsung>
In-Reply-To: <1359044659.30715.4@samsung>
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: AW: [Caml-list] Working Group: the future of syntax extensions
 in OCaml, after camlp4

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