[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
[cdt-core-dev] retirement of the non-public DOM
|
In my checked-out view I have currently removed all references to
IParserCallback; however, converting the DOM from an IParserCallback to an
ISourceElementRequestor is proving to be very painful. I could probably
work at it for another week or so before getting everything hooked up
proper again so that the Outline View, Structure Comparator & our JUnit
tests run as expected.
Why is this so complex? Since IParserCallback's granularity was
determined by the ANSI C++ grammar (declarations with multiple
declarators, etc.), and ISourceElementRequestor's granularity is by more
logical constructs (fields, methods) it is tough to shoe-horn these
complex AST structures back into primitive lists.
Since the DOM was originally intended to be for testing the Parser (and
has had few if any real restrictions placed upon beyond my whims :-) ) I
plan to disactivate this code and do the following :
1. convert all of our DOMTests & DOMFailedTests into ASTTests
(since that is their intention) so that our AutomationSuite still passes
all green
2. look into converting CModelBuilder & ComparatorModelBuilder
Concerns or comments?
Anyone willing to help w/Task 2? (Hint-hint to the owners of these
fantastic components)
JohnC