From: Francois Pottier <Francois.Pottier@inria.fr>
To: skaller <skaller@users.sourceforge.net>
Cc: Joel Reymont <joelr1@gmail.com>,
menhir-list@yquem.inria.fr, Caml List <caml-list@inria.fr>
Subject: Re: [Caml-list] Re: [Menhir-list] There's an elephant in the room: Solution to sharing a symbol table
Date: Wed, 2 May 2007 13:56:35 +0200 [thread overview]
Message-ID: <20070502115635.GA21560@yquem.inria.fr> (raw)
In-Reply-To: <1178096690.13660.80.camel@rosella.wigram>
Hello,
On Wed, May 02, 2007 at 07:04:50PM +1000, skaller wrote:
> You can't. Don't be confused by functor interface in Menhir.
> It is useless for maintaining state.
I don't think so...
> What you need is a feature I asked for .. the possibility of
> passing a state argument to the parser the same way you can
> now do for ocamllex: you just write
>
> rule fred state = parse ...
I remember our discussion. What you need primarily, if I recall
correctly, is the ability for a semantic action to recursively
invoke the parser itself. This happens to work if the parser is
defined as a recursive function, and does not (currently) work
when the parser is defined as a functor, because the functor is
not declared as recursive. We could, in principle, make it a
recursive functor, which would allow recursive invocations.
--
François Pottier
Francois.Pottier@inria.fr
http://cristal.inria.fr/~fpottier/
next prev parent reply other threads:[~2007-05-02 11:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-01 21:39 Joel Reymont
2007-05-02 5:44 ` [Menhir-list] " Francois Pottier
2007-05-02 5:58 ` Joel Reymont
[not found] ` <20070502070345.GA5242@yquem.inria.fr>
2007-05-02 7:35 ` Joel Reymont
2007-05-02 9:04 ` [Caml-list] " skaller
2007-05-02 11:56 ` Francois Pottier [this message]
2007-05-02 16:07 ` skaller
2007-05-02 18:30 ` Francois Pottier
2007-05-03 1:17 ` skaller
2007-05-03 8:48 ` 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=20070502115635.GA21560@yquem.inria.fr \
--to=francois.pottier@inria.fr \
--cc=caml-list@inria.fr \
--cc=joelr1@gmail.com \
--cc=menhir-list@yquem.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).