Re: [eclipse.org-architecture-council] Javascript: a bug that makes me r

[Doug Schaefer <dschaefer@xxxxxxx>]

For what it¹s worth, I think Michael was talking about *DT not *DK. JDT,
not JDK.

A common AST, at least partial to model symbol references and definitions,
is indeed necessary for inter-language features. We have had that in CDT
to handle things between C++ and C (and, yes, they are two different
languages). We all have lots of experience building IDEs and editors and
probably different philosophies on how to do it. It¹ll be interesting to
see if we can find common ground.

Doug.

On 2015-07-06, 1:28 PM,
"eclipse.org-architecture-council-bounces@xxxxxxxxxxx on behalf of Sven
Efftinge" <eclipse.org-architecture-council-bounces@xxxxxxxxxxx on behalf
of sven.efftinge@xxxxxxxxx> wrote:

>
>> On 06 Jul 2015, at 18:45, Michael Scharf <eclipse@xxxxxxxxx> wrote:
>> - Xtext https://eclipse.org/Xtext/ (which is extreme, because it
>>generates a *DK for
>>  each language)
>
>Allow me to comment on this :-)
>Xtext doesn¹t generate an SDK or similar but it generates a parser and an
>AST.
>Having a common notion of what ASTs look like is key to let languages
>integrate with each other and is also the basis
>for many services that are offered by Xtext and which are important for
>advanced language-specific tool support.
>If you just want lexical coloring, and maybe run an external linter than
>you don¹t need anything like that. But if you expect content assist,
>incremental
> builds and refactoring (even cross-language) than this is not going to
>happen without something like that.
>Note that IntellIj has its common notion of ASTs (called PSI) as well, so
>in that regard it is similar to Xtext.
>
>Sven