IBM
Software Group | Rational software
© 2004 IBM
Corporation
22
DOM as a Service
§We need to take some
effort to minimize parsing within Eclipse
4C and C++ are mature
languages : hence, larger source code bases
•Multiple clients
parsing on resource-change events can cripple the system
4A complex web of
#include’s throughout the code base is difficult to optimize
per-parse without having knowledge of previous parses
•Same with templates …
4The Indexer is already
parsing continually, we should be able to leverage that
information for all other clients that require saved-file parse trees
4Since parsing can be a
processor and memory-intensive operation, it is difficult for the
indexer to co-ordinate its priority vs. other parser clients for system
resources
•users requests an Open
Declaration which competes against a running indexer for memory
& CPU
4Eventual Goal
•AST Service w/Index
•Incremental Parse