|Re: [pdt-dev] Semantic Analysis in PDT|
good to know. Current PEX framework is written (broken :P) mostly by me and based on this experience Iâm designing new version which I planned to propose as PDT plugin. Probably for Mars.2 (performance is critical part for me).
Separate to ârequire / not requireâ index isnât enough, because still will be slow. Even with index. Index usage might be also easy reduced by class loaders (see bug 472758  }:->).
A lot of problem could be collected during standard Type Inference (JDT calls this flow analysis) : class / variable / method not exists or even deprecated calls . DLTK donât allow collecting IGoal results during inference process right now. I plan to propose patch, because I need it to improve syntax highlighters performance, especially deprecation highlighter.
Others need access to type information (implementation / override etcâ) so as you said index (or class loaders helpers).
Others need only content / ast
Others, mostly framework specific, might need three of above or nothing (own index/builders etcâ).
Also validator chain should be introduced. If any validator produce problem, validator participant should be able to mute / extend (ideal use case could be usage validator where doctrine extension could).
but if we talking only about ui (user point), would be nice to have not only categories and validator names with severities, but also ability to introduce some options to validator (for example be case sensitive) like in JDT.
 - https://bugs.eclipse.org/bugs/show_bug.cgi?id=472758
+48 795 996 064
On 13 Aug 2015 at 23:47:09, MichaÅ NiewrzaÅ (michal.n@xxxxxxxx) wrote:
Description: S/MIME cryptographic signature