[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [pdt-dev] Two AST models and parsers

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


On Sat, Nov 16, 2013 at 1:01 AM, Seva Lapsha <seva.lapsha@xxxxxxxxx> wrote:
I have a good idea why. Because it it's a time consuming project to migrate everything. So it was decided to postpone it until there is necessary time frame. But as always happens the time never came. Now none of the people who took that decision is longer in the team :)

So: "why" - is not really a helpful question IMO. The good questions are: "what" priority should the migration take and "when" should it happen.

Hope this helps.


On Fri, Nov 15, 2013 at 6:32 AM, Kaloyan Raev <kaloyan.r@xxxxxxxx> wrote:
Good catch! I am currently working on improving performance in Zend Studio and noticed the same. Yet no idea why they both co-exist.

Hopefully there is someone who still remember the early days of PDT.


On Fri, Nov 15, 2013 at 1:17 PM, Dawid PakuÅa <zulus@xxxxxxxxx> wrote:
Hi PDT-team,

while working on php 5.5 support for PDT I understood that this project have two very similar AST models and parsers for each one.

Is this necessary?
First model is older and is very similar to JDT/JSDT AST
Second is extended DLTK generic model. (compiler AST)

First model is used in ASTRewrite, Formatter etcâ
Second in DLTK TI framework, error reporting, etc...

Each one contains own visitors, utils etc...

Maybe is this possible to link them? This should improve performance andÂsimplify the further development.

Thanks,
Dawid

_______________________________________________
pdt-dev mailing list
pdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/pdt-dev



_______________________________________________
pdt-dev mailing list
pdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/pdt-dev



_______________________________________________
pdt-dev mailing list
pdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/pdt-dev