Hi Tilman,
The main reason of the NPE is due to a syntax error in your Optimizer.testsuite
in which you should use "{tree-rule} walks {rule}:" for defining the test
target (tree grammar's rules). Try to modify "expr:" to "expr walks expr:" in
your testsuite, and it should work. You can also re
Hi Tilman,
Thanks for the bug report and the testing grammars. I'll check this issue later
today.
Regards,
Leon
On Thursday, April 02, 2009, at 09:28AM, "Tilman Bender"
wrote:
>Hi folks,
>
>Tried to setup a testsuite for my tree grammar. The testsuite can be
>run (allthough all tests fail)
Hi David,
Are there only 2 lexical rules in your grammar?
If yes, the following gUnit test case must fail because ANTLR can't
tokenize your input string properly.
dbCommand:
".output C:\TEMP\test.csv" OK
Here is a trick to display the error messages from ANTLR as below:
".output C:\TEMP\test.
esponse.
>
> I'll start using gUnit on my project and let you know if I see any
> problems.
>
> On Mon, 10 Nov 2008 at 19:35:24, Leon Su wrote:
>> ...I'll try
>> to add this support into the next release soon :)
>>
>> Leon
>>
>> On Nov 10,
Hi George,
Thanks for the suggestion. There's indeed a need to add the
functionality of testing lexical rules separately in gUnit. I'll try
to add this support into the next release soon :)
Leon
On Nov 10, 2008, at 1:57 PM, George S. Cowan wrote:
> I have experimented with gUnit a little an
Hi Chris,
Thanks for pointing out this issue. I think it's a bug of testing a
tree grammar's template output in gUnit-1.0.2.
I just uploaded an intermediate release to the wiki page of gUnit.
Please download the new version and try to see if it works on your
testsuite.
ps. you may need to p
Hi Todd,
gUnit currently is not able to test lexical rules individually. So if
you would like to test some lexical rules only, you may need to add
some new parser rules which only define corresponding lexical rules
for testing. For example, there're two lexical rules: ID and INT.
then you m
