From: Alain Frisch <Alain.Frisch@inria.fr>
To: skaller <skaller@users.sourceforge.net>
Cc: Caml Mailing List <caml-list@inria.fr>
Subject: Re: [Caml-list] Parser state variables
Date: Fri, 28 Oct 2005 08:22:03 +0200 [thread overview]
Message-ID: <4361C38B.8090309@inria.fr> (raw)
In-Reply-To: <1130398547.7544.66.camel@rosella>
skaller wrote:
> Are there any plans to extend Ocamlyacc to allow state variables,
> in a manner similar to the recent extensions to Ocamllex to
> allow them?
>
> At present, there are two workarounds:
Another one is to make semantic actions return functions which take the
state as an argument. This is similar to introducing a new data type to
represent pure concrete parse trees and then post-process these trees to
produce abstract syntax.
-- Alain
next prev parent reply other threads:[~2005-10-28 6:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-27 7:35 skaller
2005-10-28 6:22 ` Alain Frisch [this message]
2005-10-28 7:11 ` [Caml-list] " skaller
2005-10-31 22:32 ` Erik de Castro Lopo
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=4361C38B.8090309@inria.fr \
--to=alain.frisch@inria.fr \
--cc=caml-list@inria.fr \
--cc=skaller@users.sourceforge.net \
/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).