From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: 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 F17057EEB4 for ; Sun, 3 Feb 2013 15:01:32 +0100 (CET) Received-SPF: None (mail3-smtp-sop.national.inria.fr: no sender authenticity information available from domain of jon@ffconsultancy.com) identity=pra; client-ip=84.93.230.235; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="jon@ffconsultancy.com"; x-sender="jon@ffconsultancy.com"; x-conformance=sidf_compatible Received-SPF: None (mail3-smtp-sop.national.inria.fr: no sender authenticity information available from domain of jon@ffconsultancy.com) identity=mailfrom; client-ip=84.93.230.235; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="jon@ffconsultancy.com"; x-sender="jon@ffconsultancy.com"; x-conformance=sidf_compatible Received-SPF: None (mail3-smtp-sop.national.inria.fr: no sender authenticity information available from domain of postmaster@avasout07.plus.net) identity=helo; client-ip=84.93.230.235; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="jon@ffconsultancy.com"; x-sender="postmaster@avasout07.plus.net"; x-conformance=sidf_compatible X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Ao0CALNsDlFUXebrlWdsb2JhbABErEuSaBYOAQEBAQkLCQkSKYIfAQEBBAECBQJiAgYRAQMCCREEAQEBDRoHGQ8dAQkIAgQTCwUCCYdkAxMItRIDiWCND4RDA4gwhVeFZoNPkjA X-IPAS-Result: Ao0CALNsDlFUXebrlWdsb2JhbABErEuSaBYOAQEBAQkLCQkSKYIfAQEBBAECBQJiAgYRAQMCCREEAQEBDRoHGQ8dAQkIAgQTCwUCCYdkAxMItRIDiWCND4RDA4gwhVeFZoNPkjA X-IronPort-AV: E=Sophos;i="4.84,593,1355094000"; d="scan'208";a="905258" Received: from avasout07.plus.net ([84.93.230.235]) by mail3-smtp-sop.national.inria.fr with ESMTP; 03 Feb 2013 14:57:41 +0100 Received: from WinEight ([84.93.180.99]) by avasout07 with smtp id vq1V1k002294Gsc01q1Wyu; Sun, 03 Feb 2013 14:01:31 +0000 X-CM-Score: 0.00 X-CNFS-Analysis: v=2.0 cv=H5sFNZki c=1 sm=1 a=PAy2fcRYZjOZrvRM8fVqmg==:17 a=TmaWPSqPtk0A:10 a=Xub9RBUEA-sA:10 a=8nJEP1OIZ-IA:10 a=r2vSxAw-AAAA:8 a=2J5L55nvrsoA:10 a=YG86fJyiAAAA:8 a=ZOzjf2MOAAAA:8 a=CjxXgO3LAAAA:8 a=piz1FjBUBe3yP-EYy2sA:9 a=wPNLvfGTeEIA:10 a=PAy2fcRYZjOZrvRM8fVqmg==:117 From: "Jon Harrop" To: "'caml-list'" References: <510145A5.6030807@frisch.fr> <90C5BC201F264C4C902B4E7897660042@erratique.ch> <1359044659.30715.4@samsung> <51066BCA.1020201@frisch.fr> In-Reply-To: <51066BCA.1020201@frisch.fr> Date: Sun, 3 Feb 2013 14:01:20 -0000 Message-ID: <017801ce0216$f2b2c020$d8184060$@ffconsultancy.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQJomy5hy1yIgUBIWibbqg7CvboJgQGn+hFaApVIDxcCCd0ro5cAqUsA Content-Language: en-gb Subject: RE: AW: [Caml-list] Working Group: the future of syntax extensions in OCaml, after camlp4 I worked on a commercial project written in OCaml in Q4 2012 that used stream parsing. However, my project was to translate the whole thing into F#... I never used stream parsing in any commercial code I wrote myself. I did use camlp4 quite a bit though and, I must say, the only problem I had was that it was never finished (the docs end in "..."!). Moreover, my main practical application of camlp4 was in using it to write parsers. Parsers written using Camlp4 are nicer than with any other tool I have ever used. Would be a shame if OCaml lost this or, if it did, gained the ability to write lex/yacc in-line without having to battle with multi-stage compilation and a wide selection of incomplete/broken build tools. Cheers, Jon. > -----Original Message----- > From: caml-list-request@inria.fr [mailto:caml-list-request@inria.fr] On Behalf > Of Alain Frisch > Sent: 28 January 2013 12:15 > To: Gerd Stolpmann > Cc: Daniel B=FCnzli; caml-list; wg-camlp4@lists.ocaml.org; Leo P White; A= nil > Madhavapeddy > Subject: Re: AW: [Caml-list] Working Group: the future of syntax extensions in > OCaml, after camlp4 >=20 > 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. >=20 > I've no idea how widely stream parsing is used. Has anyone some intuition > about this? >=20 > 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. >=20 > 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? >=20 >=20 > Alain >=20 >=20 > -- > Caml-list mailing list. Subscription management and archives: > https://sympa.inria.fr/sympa/arc/caml-list > Beginner's list: http://groups.yahoo.com/group/ocaml_beginners > Bug reports: http://caml.inria.fr/bin/caml-bugs