I normally test the lexer and the parser separately.

The lexer is easy to test using a function like:

  let lexbuf = Lexing.from_channel file_channel in
  let result = ref [] in
  try
    while true do
      let next_token = Dtd_lexer.token lexbuf in
      result := next_token :: !result;
      if debug_lexer then Dtd_types.print next_token;
      if next_token = Dtd_types.EOF then raise Not_found
    done;
    List.rev (!result)
  with Not_found -> List.rev (!result)

For debugging the parser I set the -v flag to ocamlyacc and look at the
.parser file

/mattias

> -----Original Message-----
> From: owner-caml-list@pauillac.inria.fr
> [mailto:owner-caml-list@pauillac.inria.fr]On Behalf Of Rafael 'Dido'
> Sevilla
> Sent: Tuesday, October 23, 2001 4:15 AM
> To: Caml List
> Subject: [Caml-list] debugging an ocamlyacc parser
>
>
> Well, while my current ocamlyacc parser seems to be working pretty well,
> I'm just wondering if there's a debug mode available for
> ocamlyacc-generated parsers, like the debugging mode that Bison uses
> when you do a #define YYDEBUG, printing out all the states the parser
> goes through as it receives tokens from the lexer, so along with the
> generated y.output file I can see how it's working (or not working as
> the case may be).
>
> --
> Rafael R. Sevilla <sevillar@team.ph.inter.net>   +63(2)   8177746
> ext. 8311
> Programmer, Inter.Net Philippines                +63(917) 4458925
> http://dido.engr.internet.org.ph/                OpenPGP Key ID:
> 0x5CDA17D8
> -------------------
> Bug reports: http://caml.inria.fr/bin/caml-bugs  FAQ:
http://caml.inria.fr/FAQ/
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/
To unsubscribe, mail caml-list-request@inria.fr  Archives: http://caml.inria.fr