One of JDT AST models contains also logic for FlowAnalysis.
At first look PDT ASTs works like in JDT, but… Older (JDT like) AST contains binding resolver, which using compiler AST and sometimes whole DLTK TI framework. Older AST (JDT like) is mostly used directly in UI with many utils, functions and widget ported from JDT (many of them still contains java/jdt keyword in comments and strings). And as I see, it is always created while using editor. He has ability to record his changes. Second AST (compiler subnamespace) its created for DLTK integration, but it also used in outline, syntax coloring etc… This AST is cashed by DLTK
In summary, it looks like an unfinished migration to DLTK. I do not see the terms of use of these models.
Maybe will be possible to transform from one to another (by special visitor), instead of duplicating parsers.
Dawid
Actually, JDT also uses 2 ASTs :)
One is used in indexing/search/model building etc - the so
called compiler AST. It uses less resources, so can be created
faster.
The other one supports rewrite, so it uses more resources
because of that and is used mostly for refactorings.
Regards,
Alex
_______________________________________________
pdt-dev mailing list
pdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/pdt-dev
|