Thanks for the info. I have been browsing over the master branch and noticed that in some plugins use is made of DLTK's 'internal' classes...
I sort of have a love/hate relationship with PDT - I have found nothing better, but there are some things I don't like (or would like it to do)... so I decided to have a look and see what effort was needed to do some modifications. Anyhow, thanks for the work all of you do on PDT! On Sun, Jun 7, 2020 at 12:10 PM Dawid Pakuła <[email protected]> wrote: > Hi, > > Maybe in future. > > For now we have to untick form DLTK IModel/IType/IField/ISourceModule. > It's too limited: > 1. Problems with class alias > 2. Not available traits in hierarchy > 3. Problems with imports > 4. Not possible to keep reference to PHPDoc/Interface infos in member > 5. No annotation support (PHP 8) > > On 7 June 2020 at 08:39:41, Marc Veary ([email protected]) wrote: > > Hi, > I was looking over GItHub and wondered if the project to abandon the DLTK > model means: completely remove the use of DLTK from PDT? > > Regards > _______________________________________________ > pdt-dev mailing list > [email protected] > To unsubscribe from this list, visit > https://www.eclipse.org/mailman/listinfo/pdt-dev > > _______________________________________________ > pdt-dev mailing list > [email protected] > To unsubscribe from this list, visit > https://www.eclipse.org/mailman/listinfo/pdt-dev >
_______________________________________________ pdt-dev mailing list [email protected] To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/pdt-dev
