From: Kenneth Knowles <kknowles@uclink.berkeley.edu>
To: caml-list@inria.fr
Subject: Re: [Caml-list] start conditions in ocamllex
Date: Wed, 25 Feb 2004 11:23:09 -0800 [thread overview]
Message-ID: <20040225192309.GA22138@tallman.kefka.frap.net> (raw)
In-Reply-To: <20040225190056.GE27866@speakeasy.org>
> > Has anyone thought of implementing start conditions for ocamllex?
> Can't you get the same effect with multiple entrypoints? Though this syntax
> is probably cleaner.
>
I disagree; I think different entry points are cleaner. In some recent release
they added the ability to pass your own parameter to the rules, and so I
maintain state by passing a reference to the state. I don't think the below
code is thread safe, but it could easily be made so by keeping the state ref
external to the entire lexer:
{
type state_t = StartCondition1 | StartCondition2
}
rule entrypoint1 state_ref = parse
'a' { state_ref := StartCondition2; A_TOKEN }
and entrypoint2 state_ref = parse
'a' { state_ref := StartCondition1; B_TOKEN }
{
let next_token start_start =
let state_ref = ref start_state in
(fun lexbuf -> match !state_ref with
| StartCondition1 -> entrypoint1 state_ref lexbuf
| StartCondition2 -> entrypoint2 state_ref lexbuf
}
-------------------
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:[~2004-02-25 19:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-25 18:07 Sean Proctor
2004-02-25 19:00 ` Shawn Wagner
2004-02-25 19:23 ` Kenneth Knowles [this message]
2004-02-25 19:31 ` Shawn Wagner
2004-02-26 2:54 ` [Caml-list] Plea for arguments to Ocamlyacc generated parsers 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=20040225192309.GA22138@tallman.kefka.frap.net \
--to=kknowles@uclink.berkeley.edu \
--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