caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: "Jocelyn Sérot" <jocelyn.serot@uca.fr>
To: OCaML Mailing List <caml-list@inria.fr>
Subject: Re: [Caml-list] Implementing include "file" statement in menhir
Date: Tue, 21 Jan 2020 14:03:28 +0100	[thread overview]
Message-ID: <D324C400-AE96-45D8-B9AF-D025FD73B9C7@uca.fr> (raw)
In-Reply-To: <20200121064845.GM27889@rich.annexia.org>

[-- Attachment #1: Type: text/plain, Size: 2591 bytes --]

Hi,

I had implemented a include mechanisms at the lexer level using ocamllex for the Caph programming language.
This is here (undocumented unfortunately) (related stuff starts at line 128):

https://github.com/jserot/caph/blob/master/compiler/lexer.mll <https://github.com/jserot/caph/blob/master/compiler/lexer.mll>

Just in case it can help.


Jocelyn

> Le 21 janv. 2020 à 07:48, Richard W.M. Jones <rich@annexia.org> a écrit :
> 
> [Resend, apologies if you get this twice, but I sent it
> earlier and that seems to have disappeared.]
> 
> I'm writing a parser which needs to have a C-like include directive.
> There's an old thread on this describing a rather complicated way to
> do this for ocamllex:
> https://groups.google.com/forum/#!topic/fa.caml/_v_k4WTQV_Q
> 
> I thought I'd have a go at writing an include statement in menhir, and
> I did come up with something which works but it's quite a large hack.
> What I did is documented below, but I wonder if someone can think of a
> simpler way to do this?  Also two related questions:
> 
> How do you pass extra parameters to menhir's generated parser
> functions?
> 
> Is there a nice way to export values into menhir's generated
> parser.mli file?
> 
> ----
> 
> The concept behind my include statement uses the following grammar:
> 
>  %token INCLUDE
>  %token <string> STRING
>  %start file
>  %%
>  file: list(stmt) ;
> 
>  stmt:
>      | INCLUDE STRING
>      {
>        let filename = $2 in
>        let fp = open_in filename in
>        let lexbuf = Lexing.from_channel fp in
>        lexbuf.lex_curr_p <- { lexbuf.lex_curr_p with pos_fname = filename };
> 	(* Recursively call Parser.file: *)
>        file Lexer.read lexbuf;
>        close_in fp;
>      }
>      | ... other statements ...
>      ;
> 
> 
> Unfortunately as written the above code cannot work because it
> introduces a circular dependency between the Parser and the Lexer
> modules (normally the Lexer module depends on the Parser, and so the
> Parser cannot use any functions from the Lexer module).
> 
> To break the cycle we have to add:
> 
>  %{
>  let lexer_read = ref None
>  %}
> 
> and replace Lexer.read with:
> 
>  let reader =
>     match !lexer_read with None -> assert false | Some r -> r in
>  file reader lexbuf;
> 
> Then to initialize lexer_read, we have to export it by doing this
> hack:
> 
>  menhir parser.mly
>  echo 'val lexer_read : (Lexing.lexbuf -> token) option ref' >> parser.mli
> 
> and we can set it from the main program.
> 
> Rich.


[-- Attachment #2: Type: text/html, Size: 4539 bytes --]

      parent reply	other threads:[~2020-01-21 13:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-21  6:48 Richard W.M. Jones
2020-01-21  7:15 ` Yann Régis-Gianas
2020-01-21  8:55 ` François Pottier
2020-01-21 13:03 ` Jocelyn Sérot [this message]

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=D324C400-AE96-45D8-B9AF-D025FD73B9C7@uca.fr \
    --to=jocelyn.serot@uca.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;
as well as URLs for NNTP newsgroup(s).