From: skaller <skaller@users.sourceforge.net>
To: Alain Frisch <Alain.Frisch@inria.fr>
Cc: Caml Mailing List <caml-list@inria.fr>
Subject: Re: [Caml-list] Parser state variables
Date: Fri, 28 Oct 2005 17:11:56 +1000 [thread overview]
Message-ID: <1130483516.28547.26.camel@rosella> (raw)
In-Reply-To: <4361C38B.8090309@inria.fr>
On Fri, 2005-10-28 at 08:22 +0200, Alain Frisch wrote:
> 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.
Aha! Another win for higher order functions! Thanks for this
insight. Dang -- so obvious when you see it :)
--
John Skaller <skaller at users dot sf dot net>
Felix, successor to C++: http://felix.sf.net
next prev parent reply other threads:[~2005-10-28 7:12 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 ` [Caml-list] " Alain Frisch
2005-10-28 7:11 ` skaller [this message]
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=1130483516.28547.26.camel@rosella \
--to=skaller@users.sourceforge.net \
--cc=Alain.Frisch@inria.fr \
--cc=caml-list@inria.fr \
/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