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 9024F7EE51 for ; Wed, 3 Apr 2013 14:58:12 +0200 (CEST) Received-SPF: None (mail3-smtp-sop.national.inria.fr: no sender authenticity information available from domain of bobzhang1988@gmail.com) identity=pra; client-ip=209.85.128.41; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="bobzhang1988@gmail.com"; x-sender="bobzhang1988@gmail.com"; x-conformance=sidf_compatible Received-SPF: Pass (mail3-smtp-sop.national.inria.fr: domain of bobzhang1988@gmail.com designates 209.85.128.41 as permitted sender) identity=mailfrom; client-ip=209.85.128.41; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="bobzhang1988@gmail.com"; x-sender="bobzhang1988@gmail.com"; x-conformance=sidf_compatible; x-record-type="v=spf1" Received-SPF: None (mail3-smtp-sop.national.inria.fr: no sender authenticity information available from domain of postmaster@mail-qe0-f41.google.com) identity=helo; client-ip=209.85.128.41; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="bobzhang1988@gmail.com"; x-sender="postmaster@mail-qe0-f41.google.com"; x-conformance=sidf_compatible X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AmEBAO4mXFHRVYApnGdsb2JhbABDhhq9YoEMFg4BAQEBAQYNCQkUKIIfAQEFMgEFCAEbDw8DDAYFCw0JJQ8CEhEBBQEcBgEMCAEBh30BAw+iX4wvgnuEUQoZJw1ZiHwBBQyPFINAA45PiByPKT+ESg X-IPAS-Result: AmEBAO4mXFHRVYApnGdsb2JhbABDhhq9YoEMFg4BAQEBAQYNCQkUKIIfAQEFMgEFCAEbDw8DDAYFCw0JJQ8CEhEBBQEcBgEMCAEBh30BAw+iX4wvgnuEUQoZJw1ZiHwBBQyPFINAA45PiByPKT+ESg X-IronPort-AV: E=Sophos;i="4.87,401,1363129200"; d="scan'208";a="9633471" Received: from mail-qe0-f41.google.com ([209.85.128.41]) by mail3-smtp-sop.national.inria.fr with ESMTP/TLS/RC4-SHA; 03 Apr 2013 14:58:11 +0200 Received: by mail-qe0-f41.google.com with SMTP id 7so839634qeb.0 for ; Wed, 03 Apr 2013 05:58:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=chjfI12/wEQoHcf8hF/ppofF3hMqv10UGEJZAN2V928=; b=MXqp6YIA3/yxDSvPz6WjyYUkThd701dkl2Ev0n6DQJCo09LQ8m8gUPB12nTJPMZUhW n7CvffooxcKUI3zuycVnPyXR1OQUG7daToS5aAVZksl5YExEn9G68azzo1Bayz6SSNfG O4sh8HvhLbW2IafBv30akOL6IY3kIs9cC9roUoY5SU76ghfmmQU4rHReIazgJ8DbO/0v EW2d9JKVG8rM6ICM/Hvu8of/iZZqe6cws2ooQntSHOLEkp0sTxWFzSza+6NA13SUuqo4 XO2Y68vTDfv4B1QjBVUEx+KuYsLjDEvZQhLniSC8PGe+Km25I4nFoYxpHyJSyNi+Fg6Z F4KA== X-Received: by 10.224.104.145 with SMTP id p17mr1497116qao.50.1364993890419; Wed, 03 Apr 2013 05:58:10 -0700 (PDT) Received: from bobzhangs-iMac.local ([66.250.143.158]) by mx.google.com with ESMTPS id t3sm6289053qen.5.2013.04.03.05.58.09 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 03 Apr 2013 05:58:09 -0700 (PDT) Message-ID: <515C2760.50201@gmail.com> Date: Wed, 03 Apr 2013 08:58:08 -0400 From: bobzhang User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130307 Thunderbird/17.0.4 MIME-Version: 1.0 To: Pierre-Etienne Meunier , Caml List References: <515C26BD.1070308@gmail.com> In-Reply-To: <515C26BD.1070308@gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Subject: [Caml-list] Re: Is there any open-sourced yacc style parser generator written in OCaml? On 4/3/13 8:55 AM, Pierre-Etienne Meunier wrote: > El 03/04/13 14:48, bob zhang escribió: >> >> Dear list, >> I want to embed a yacc-style parser generator in OCaml, ocamlyacc is >> written in C. menhir has a QPL license so that I can not patch it. So >> is there any other existing yacc-style parser generator(in OCaml) >> available? >> Thanks in advance! >> -- >> Regards >> -- Bob > > Have a look at dypgen, but it's not yacc-style (the lexer are embedded > in the parsers, and the kind of grammar is GLR, not LR1). Thanks! The reason for a yacc style is that it's simple, everyone who take a compiler course knows its underlying theory. Dypgen seems too complex for non-parser expert to understand. > > Regards, > Pierre >