From: Joel Reymont <joelr1@gmail.com>
To: caml-list@inria.fr
Subject: Testing lexers and parsers
Date: Tue, 27 Feb 2007 15:29:24 +0000 [thread overview]
Message-ID: <7175FEA6-5CA0-4379-9BBC-CF43504CE733@gmail.com> (raw)
Folks,
I'm trying to incrementally develop a translator using a test-driven
approach. I figure I can write a bunch of tests for small chunks of
functionality to structurally test expected AST against produced.
Once I get to testing the parsing of whole files I think I can print
the AST I produce into a file and test this against a target file
with the correct printed AST. I can probably run 'cmp' to make sure
my files match. This would not be a structural comparison, though,
and would be highly dependent on white space which does not strike me
as ideal.
Is there a better way to accomplish this while still using structural
comparison of ASTs?
Should I try to read my target AST into OCaml, for example? Should I
create a bunch of "target AST" modules with functions that return my
target AST?
How does everyone else approach testing of lexers and parsers?
Thanks, Joel
--
http://wagerlabs.com/
next reply other threads:[~2007-02-27 15:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-27 15:29 Joel Reymont [this message]
2007-02-27 15:42 ` [Caml-list] " Denis Bueno
2007-02-27 15:46 ` Joel Reymont
[not found] ` <6dbd4d000702270810h16ea3308k49dfcf7e5a479ecb@mail.gmail.com>
2007-02-27 16:11 ` Denis Bueno
2007-02-27 16:20 ` konrad
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=7175FEA6-5CA0-4379-9BBC-CF43504CE733@gmail.com \
--to=joelr1@gmail.com \
--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).