From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on yquem.inria.fr X-Spam-Level: ** X-Spam-Status: No, score=2.5 required=5.0 tests=AWL,DNS_FROM_RFC_POST, SPF_NEUTRAL autolearn=disabled version=3.1.3 X-Original-To: caml-list@yquem.inria.fr Delivered-To: caml-list@yquem.inria.fr Received: from mail2-relais-roc.national.inria.fr (mail2-relais-roc.national.inria.fr [192.134.164.83]) by yquem.inria.fr (Postfix) with ESMTP id 81EA7BBC4 for ; Sun, 8 Mar 2009 01:30:19 +0100 (CET) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Ak8CAFagsknRVduukWdsb2JhbACUYz8BAQEBCQkMBw+tWIEHjwkBAwEDhAIGgxQ X-IronPort-AV: E=Sophos;i="4.38,321,1233529200"; d="scan'208";a="22204502" Received: from mail-ew0-f174.google.com ([209.85.219.174]) by mail2-smtp-roc.national.inria.fr with ESMTP; 08 Mar 2009 01:30:19 +0100 Received: by ewy22 with SMTP id 22so617802ewy.27 for ; Sat, 07 Mar 2009 16:30:18 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:references:message-id:from:to :in-reply-to:content-type:content-transfer-encoding:mime-version :subject:date:cc:x-mailer; bh=+gUEq7DyuGdRKR1ZXqdUPX8kQZF3cXH8ypVORJYbRDw=; b=gznnbi5itZ2dDTSWUc96qwc8G2P6mR925M8MMAm7sxsOO1jcXgEygAQTHGa4arXECT fM/CQPwrE3q1sx1rXEstxEJyP6Gv+7/gY6DQ2z0715tFvhi8yCUzKMOSbwNB4YnNOUGc P0vpCTWvAA4fyOLM0skqiHsDGuwQ4E9voXjlM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=references:message-id:from:to:in-reply-to:content-type :content-transfer-encoding:mime-version:subject:date:cc:x-mailer; b=LIo5xJ7v7zpHlMR5t3ucbEhcOSp4JF87ihEFLN8Bt0t7x/rAnppAt2fsVNs1YPJpWS H3FEsig7UbR25sE4aKDoLt+GoMLOsnJPNNeZ3S3eDtg7ZTiwSMWoEH1HdkXDjE5owcqI WV/+37wed8TxEZw+4Xn6OzV2zf4w9fItIJzs8= Received: by 10.210.125.13 with SMTP id x13mr2305520ebc.33.1236472218763; Sat, 07 Mar 2009 16:30:18 -0800 (PST) Received: from ?10.10.30.5? (94.Red-88-6-143.staticIP.rima-tde.net [88.6.143.94]) by mx.google.com with ESMTPS id i7sm4756661nfh.66.2009.03.07.16.30.17 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sat, 07 Mar 2009 16:30:18 -0800 (PST) References: <200903072352.18127.jon@ffconsultancy.com> <200903080012.10433.jon@ffconsultancy.com> <597512.92153.qm@web27007.mail.ukl.yahoo.com> Message-Id: From: Joel Reymont To: Matthieu Wipliez In-Reply-To: <597512.92153.qm@web27007.mail.ukl.yahoo.com> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v930.3) Subject: Re: Re : [Caml-list] camlp4 stream parser syntax Date: Sun, 8 Mar 2009 00:30:15 +0000 Cc: caml-list@yquem.inria.fr X-Mailer: Apple Mail (2.930.3) X-Spam: no; 0.00; camlp:01 parser:01 syntax:01 matthieu:01 parser:01 camlp:01 ocaml:01 invoke:01 wrote:01 caml-list:01 functions:01 stream:04 stream:04 full-blown:08 maybe:10 On Mar 8, 2009, at 12:20 AM, Matthieu Wipliez wrote: > Joel asked me the parser so I gave it to him, but maybe it can be of > use for others, so here it is. While we are on this subject... How do you troubleshoot camlp4 rules? With a stream parser you can invoke individual functions since each is a full-blown parser. Can the same be done with camlp4, e.g. individual rules invoked? Can rules be traced to see which ones are being taken? Thanks, Joel --- http://tinyco.de Mac, C++, OCaml