Synopsis - Issue Tracker

I'v checked in (rev:1392) some code extracted from 
the ISO C++ standard, which should provide an 
extensive set of cases to test against.
We need to define how to implement the tests, i.e. 
how to trace what the parser is doing.
Alternatively, we could introspect the symbol 
table after the parsing and validate that the 
symbol references are set up correctly (possibly
using the Visitor idea involving comments you
mentioned earlier).

Since symbol declaration is now in place
(roughly), I'm ready to work out a test
that will help us measure the progress in
the development of the actual symbol lookup.

I think the applet should parse an input file,
generating both a ptree as well as a symbol
table. Then a specialized visitor should run
over the ptree and look up each occurence of
an identifier that is not itself a declarator.

The generated output should show the qualified
name of all matched symbols, as well as failures
encountered during the parsing as well as the
lookup. The parser already stores syntax and
symbol lookup errors, so it should be possible
to generate output that allows us to unambiguously
determine whether the program does the right 
thing.

Does this make sense to you ?

While far from complete, it is already working 
nicely and helping in the development as more tests
are added / enabled.