From: Joel Reymont <joelr1@gmail.com>
To: Jake Donham <jake@donham.org>
Cc: "O'Caml Mailing List" <caml-list@yquem.inria.fr>
Subject: Re: [Caml-list] camlp4 grammar and LIST1
Date: Tue, 10 Mar 2009 22:07:45 +0000 [thread overview]
Message-ID: <C682AD11-2C6D-4356-AFB5-1E34D1FA3239@gmail.com> (raw)
In-Reply-To: <c7e4e9f0903101448u550ea4b2q6bc82c7dc303d693@mail.gmail.com>
On Mar 10, 2009, at 9:48 PM, Jake Donham wrote:
>> statement: [ [ s = openStatement -> s | s = closedStatement -> s ] ];
>
> Syntactically it is fine but I don't think this is going to do what
> you want. Camlp4 parsers aren't backtracking; you have to distinguish
> openStatement from closedStatement by parsing a token.
I have it like this at the moment. Are you saying it won't work?
What does it mean to parse a token then?
Does that token have to be in the same rule?
Thanks, Joel
---
statement: [ [ openStatement | closedStatement ] ];
openStatement: [ [ openIfStatement ] ];
openIfStatement:
[
[ "If"; e = expr; "Then"; s1 = closedStatement; "Else"; s2 =
openStatement -> If (e, s1, s2)
| "If"; e = expr; "Then"; s = statement -> If (e, s, Skip)
]
];
closedIfStatement:
[
[ "If"; e = expr; "Then"; s1 = closedStatement; "Else"; s2 =
closedStatement -> If (e, s1, s2) ]
];
closedStatement:
[
[ inputDeclarations
| varDeclarations
| arrayDeclarations
| compoundStatement
| assignment
| closedIfStatement
| whileStatement
| forStatement
| tradeStatement
| preprocessorStatement
| procCall
]
];
inputDeclarations:
[
[ "Input"; ":";
l = LIST1 [ x = inputDeclaration -> x ] SEP "," -> InputDecls l
]
];
...
---
http://tinyco.de
--- Mac & iPhone
next prev parent reply other threads:[~2009-03-10 22:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-10 18:41 Joel Reymont
2009-03-10 21:48 ` [Caml-list] " Jake Donham
2009-03-10 22:07 ` Joel Reymont [this message]
2009-03-10 23:01 ` Jake Donham
2009-03-10 23:36 ` Joel Reymont
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=C682AD11-2C6D-4356-AFB5-1E34D1FA3239@gmail.com \
--to=joelr1@gmail.com \
--cc=caml-list@yquem.inria.fr \
--cc=jake@donham.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).