[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[news.eclipse.tools.jdt] Re: Incremental parsing in JDT

David Audel wrote:
Orly Goren wrote:
Is the code assist completions based upon the parsing alone, or also on some Indexer (like it is for CDT)? If it is based also on the Indexer, what is the indexer results for? i.e. what are they different from the parser results), and what is the information kept in the indexer..


The Search indexes are used to find types proposals when a simple name is completed. Code assist can also use the eclipse Java Model. So code assist doesn't use caching for the completed compilation unit but benefit from the Search caching (indexes) and Java Model caching for all other compilation units.

Is the Java Model the result of the AST build (from the parsing)? If not, then what does it stand for? When is the index& Java Model build? What do you mean by types proposals (only when ASTNode is a type?)


Is there any connection between the parsing done for code assist and the parsing done for syntax error highlighting? (I assume not since the parser done for code assist doesn't enter function declarations...)

There is no connection between these parsing. However the both parser classes inherit from the same class: Parser. Code assist parser is CompletionParser and the syntax error highlighting parser is SourceElementPaser.

Is the parser applied for the Error highlighting working in some incremental way, or does it do full parsing?


Thanks!!!
Orly