From: skaller <skaller@users.sourceforge.net>
To: Christoph Bauer <Christoph.Bauer@lmsintl.com>
Cc: Erik de Castro Lopo <mle+ocaml@mega-nerd.com>, caml-list@yquem.inria.fr
Subject: RE: [SPAM?][Caml-list] Handling include files using ocamllex
Date: Thu, 02 Aug 2007 23:19:30 +1000 [thread overview]
Message-ID: <1186060770.23889.39.camel@rosella.wigram> (raw)
In-Reply-To: <BB046CA812535C45BD0029AA9D04BA79012BFA38@KL-SRV57.lmsintl.com>
On Thu, 2007-08-02 at 12:29 +0200, Christoph Bauer wrote:
> > Hi all,
> >
> > I doing some simple parsing with ocamllex and ocamlyacc and I
> > need to be able to handle C style include files.
> >
> > I know how to do this in C with flex and bison, but I can't
> > figure out how to do it with ocamllex and ocamlyacc.
> >
> > Anyone know how to do this?
>
> A solution could be to create an lexbuf from a function with
> Lexing.from_function.
> This function has to manage a stack of open channels and positions. It
> has to
> scan for "#include"-statements and copies instead of these statements
> the contents
> of the corresponding files into the buffer.
>
> Just an idea, I haven't done it yet.
I recommend abandoning the idea of passing a
lexbuf to a parser: make a dummy lexbuf and pass that to
keep Ocamlyacc happy, but make sure you never use it.
Instead, create an Ocaml class with a get_token method,
and use the closure of that method over the class PLUS
a dummy lexbuf.
The class then manages the lexer state. A stack
of Ocamllex lexers and lexbufs can be used. If you want
to do conditional compilation, you also need a stack
of booleans -- one stack per include file (to ensure
conditions don't span file boundaries).
--
John Skaller <skaller at users dot sf dot net>
Felix, successor to C++: http://felix.sf.net
next prev parent reply other threads:[~2007-08-02 13:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-02 10:09 Erik de Castro Lopo
2007-08-02 10:29 ` [SPAM?][Caml-list] " Christoph Bauer
2007-08-02 10:42 ` [Caml-list] " Erik de Castro Lopo
2007-08-02 13:19 ` skaller [this message]
2007-08-05 4:52 ` Erik de Castro Lopo
2007-08-05 5:35 ` Erik de Castro Lopo
2007-08-05 10:16 ` skaller
2007-08-05 10:33 ` Erik de Castro Lopo
2007-08-05 11:55 ` Jacques GARRIGUE
2007-08-05 12:17 ` 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=1186060770.23889.39.camel@rosella.wigram \
--to=skaller@users.sourceforge.net \
--cc=Christoph.Bauer@lmsintl.com \
--cc=caml-list@yquem.inria.fr \
--cc=mle+ocaml@mega-nerd.com \
/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