From: "Rafael 'Dido' Sevilla" <sevillar@team.ph.inter.net>
To: Caml List <caml-list@pauillac.inria.fr>
Subject: [Caml-list] debugging an ocamlyacc parser
Date: Tue, 23 Oct 2001 10:14:42 +0800 [thread overview]
Message-ID: <20011023101442.B17138@team.ph.inter.net> (raw)
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
next reply other threads:[~2001-10-23 2:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-23 2:14 Rafael 'Dido' Sevilla [this message]
2001-10-23 5:42 ` Mattias Waldau
2001-10-23 7:51 ` Hendrik Tews
2001-10-24 14:53 ` Xavier Leroy
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=20011023101442.B17138@team.ph.inter.net \
--to=sevillar@team.ph.inter.net \
--cc=caml-list@pauillac.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).