From: Hendrik Tews <tews@tcs.inf.tu-dresden.de>
To: caml-list@inria.fr
Subject: Re: [Caml-list] Calling ocamlyacc from ocamlyacc
Date: Wed, 3 Sep 2003 12:28:10 +0200 [thread overview]
Message-ID: <16213.49722.962405.471006@ithif51.inf.tu-dresden.de> (raw)
In-Reply-To: <20030902152340.GA32745@henchmonkey.org>
katre writes:
Right, but is there a way, in a ocamlyacc action, to switch which lexer
rule you're using? That seems to be the main part I am missing. Or if
I could access the lexbuf directly, I could also use that.
In the lexer you can do
rule lexer =
parse
| "" { match !global_var with
| Xlex -> xlex lexbuf
| Ylex -> ylex lexbuf
}
and xlex =
parse
....
and ylex =
parse
....
You can set the global_var from the actions in the grammar.
However, there is probably a better solution: First note that
ocamlyacc generated functions expect a (Lexing.lexbuf -> token)
function. So you can write your own master lexer:
let lexer lexbuf = match !global_var with
| Xlex -> Lexer.xlex lexbuf
| Ylex -> ....
with a bit of hacking you can also combine ocamllex lexers with
other lexers.
In both approaches the problem is the lookahead token: In some
cases yacc fetches the next token and decides on that token
whether to shift or reduce. If the action taken on reduce changes
the lexer then have used the wrong lexer for the next token.
You can examine the grammar.output file and the OCAMLRUNPARAM=p
trace to find out if ocamlyacc needs the lookahead token for a
given rule. (I can give examples on that if you are interested.)
Bye,
Hendrik
-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
next prev parent reply other threads:[~2003-09-03 10:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-01 17:28 katre
2003-09-02 15:19 ` Michal Moskal
2003-09-02 15:23 ` katre
2003-09-02 15:40 ` Michal Moskal
2003-09-03 10:28 ` Hendrik Tews [this message]
2003-09-06 3:36 ` skaller
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=16213.49722.962405.471006@ithif51.inf.tu-dresden.de \
--to=tews@tcs.inf.tu-dresden.de \
--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