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=1.1 required=5.0 tests=AWL,HTML_MESSAGE,SPF_NEUTRAL autolearn=disabled version=3.1.3 Received: from mail4-relais-sop.national.inria.fr (mail4-relais-sop.national.inria.fr [192.134.164.105]) by yquem.inria.fr (Postfix) with ESMTP id C13C3BC6C for ; Fri, 1 Feb 2008 19:27:49 +0100 (CET) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AgAAAH/zokdIDtbheGdsb2JhbACCPDSNPQEKBAQJCBOXU4ZI X-IronPort-AV: E=Sophos;i="4.25,291,1199660400"; d="scan'208";a="22066327" Received: from hu-out-0506.google.com ([72.14.214.225]) by mail4-smtp-sop.national.inria.fr with ESMTP; 01 Feb 2008 19:27:49 +0100 Received: by hu-out-0506.google.com with SMTP id 40so1083826hub.13 for ; Fri, 01 Feb 2008 10:27:48 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; bh=57SxkSPi5dQNRmIz7HFX9u8cLDQRdMOBQ9E+gJynCMQ=; b=sa3dhpLgIUil52ylv068o5HjAynVJlZHsc2ZjeOd4k4KJy+gg/+fYG7/QU9mt4JyWzjwWSH3lMqcmR8edOTTDW3AAs0Y9vaPJa34YLdhyf3GXMeeFZI+8WxdhtKf15RgtgjbbFAFAzCVd2t+tOEYwvPnC7xuKIGrXtiXH7pBnys= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=CwaBm3vzzhojt5AkdDUhztQvR3A9qPLYaMXH/i4tS7+fxUZLFNiqCLJiPVIpblsSZ1+XaXO8+SWcqFX9wv+4v/ln36aN1avSDAPMGnbeB1wgydxy21gclTrCu27asnT4qzlO2pKUcyYLpybyk6jAzL1TMZrjLHQmOxAXllQd1vc= Received: by 10.86.87.5 with SMTP id k5mr3435158fgb.51.1201890468599; Fri, 01 Feb 2008 10:27:48 -0800 (PST) Received: by 10.86.52.20 with HTTP; Fri, 1 Feb 2008 10:27:48 -0800 (PST) Message-ID: Date: Fri, 1 Feb 2008 13:27:48 -0500 From: "Jonathan Bryant" To: "David Allsopp" Subject: Re: [Caml-list] [OSR] Caml Community Code Cc: caml-list@yquem.inria.fr In-Reply-To: <003d01c864f7$9e3c97d0$6c7ba8c0@countertenor> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_7978_31151788.1201890468603" References: <003d01c864f7$9e3c97d0$6c7ba8c0@countertenor> X-Spam: no; 0.00; camlp:01 syntax:01 syntax:01 camlp:01 parser:01 parsers:01 parsers:01 trivial:01 beginner's:01 ocaml:01 bug:01 parser:01 trivial:01 beginner's:01 ocaml:01 ------=_Part_7978_31151788.1201890468603 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline On Fri, Feb 1, 2008 at 12:26 PM, David Allsopp wrote: > > I also think we should have one CamlP4 grammar with all the community's > > agreed upon "standard" syntax extensions (sort of a "new revised" > > syntax?) > > Am I correct in thinking that you can only use one camlp4 parser per > source > file - i.e. that parsers cannot be automatically composed, even if that is > logically (grammatically) possible? I believe multiple CamlP4 parsers can be specified on the command line and are used in the order given. But there are a few (relatively trivial) syntax extensions people are commonly asking for (try ... finally is probably the most common), so I was suggesting that we group the most requested ones into a single camlp4 rather than users having to keep up with and constantly specify multiple camlp4s. --Jonathan > > > David > > _______________________________________________ > Caml-list mailing list. Subscription management: > http://yquem.inria.fr/cgi-bin/mailman/listinfo/caml-list > Archives: http://caml.inria.fr > Beginner's list: http://groups.yahoo.com/group/ocaml_beginners > Bug reports: http://caml.inria.fr/bin/caml-bugs > ------=_Part_7978_31151788.1201890468603 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline

On Fri, Feb 1, 2008 at 12:26 PM, David Allsopp <dra-news@metastack.com> wrote:
> I also think we should have one CamlP4 grammar with all the community's
> agreed upon "standard" syntax extensions (sort of a "new revised"
> syntax?)

Am I correct in thinking that you can only use one camlp4 parser per source
file - i.e. that parsers cannot be automatically composed, even if that is
logically (grammatically) possible?

I believe multiple CamlP4 parsers can be specified on the command line and are used in the order given.  But there are a few (relatively trivial) syntax extensions people are commonly asking for (try ... finally is probably the most common), so I was suggesting that we group the most requested ones into a single camlp4 rather than users having to keep up with and constantly specify multiple camlp4s.

--Jonathan




David

_______________________________________________
Caml-list mailing list. Subscription management:
http://yquem.inria.fr/cgi-bin/mailman/listinfo/caml-list
Archives: http://caml.inria.fr
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
Bug reports: http://caml.inria.fr/bin/caml-bugs

------=_Part_7978_31151788.1201890468603--