c(h)ore stuff to do

Word of warning...

When I say "chore", I mean it. Some tasks listed here are not necessarily hard, but very time consuming and very not rewarding. Still, all of them need to be done.

Javadoc

OK, I was lying. Documenting can be very rewarding. As Nicolas Boileau puts it:

Ce qui se conçoit bien s'énonce clairement, Et les mots pour le dire viennent aisément.

In other (rather more crude) words: what you don't understand you can't explain.

So there, good documentation is planned and will be done, however much time it takes.

Tests

There are a great many components which are not really tested the way they should.

For instance, testing MatcherVisitors interactions with Matchers, RuleMethodProcessor transformations, parsing errors, etc etc.

But the hardest part will be...

Remove all String based testing!

And there is a LOT of it:

• parse tree dumps;
• bytecode dumps (!!!);
• positional error messages...

It was the same story with parser statistics, but since them I have fixed that! All this other stuff needs to be done nevertheless.

80% done. What is left is no fun at all though: bytecode dumps :/ (also parse errors but this will be easier to deal with)