Hello,
I have been trying to figure out a way to test a parser for the Oz
language in Eclipse in order to implement an editor. At this point, I care
to ask (having reviewed the ErrorListener documentation in Appendix B of the
compiler section) if there is a way to get a number or identifier for an
error or warning instead? Also, can I have a list of all Mozart errors and
warnings and some guidance about which are relevant to testing a parser (i.e.
compile time as opposed to run time, for example)?
As for my earlier posting about a constraint based search for a
production grammar that would generate input that could be compiled
successfully by Mozart, I realize that was quite grand. At this point, I
think that I will have to settle for a production grammar generator that
creates a far reaching, but not totally exhaustive set of combinations of
program input. Remember, a production grammar is the set of all sentences
(terminology?) that satisfy a grammar. The main problem I see generating a
production grammar for the Oz language, and any language in general, is
"combinatorial explosion". It is currently beyond my capabilities to deal
with this issue in a less than naive manner (i.e. a subset of all the
combinations of terminals and nonterminal "paths" in the grammar). I have
looked as thoroughly as possible on the Internet for production grammar
generators that are free to use or publicly available, and I have not found
any.
Sincerely,
Craig
_________________________________________________________________________________
mozart-users mailing list
[email protected]
http://www.mozart-oz.org/mailman/listinfo/mozart-users
