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

["Oberhuber, Martin" <Martin.Oberhuber@xxxxxxxxxxxxx>]

With tern claiming support for Eclipse/Java , I'm wondering how much of a parser JSDT even needs ?
Perhaps syntax highlighting would be sufficient, with the rest offloaded to tern ?
http://ternjs.net/doc/manual.html#tern_java


Thanks,
Martin
--
Martin Oberhuber, SMTS / Product Owner - Development Tools, Wind River
direct +43.662.457915.85  fax +43.662.457915.6


-----Original Message-----
From: eclipse.org-architecture-council-bounces@xxxxxxxxxxx [mailto:eclipse.org-architecture-council-bounces@xxxxxxxxxxx] On Behalf Of Michael Scharf
Sent: Wednesday, July 01, 2015 3:01 PM
To: Max Rydahl Andersen; eclipse.org-architecture-council
Subject: Re: [eclipse.org-architecture-council] Javascript: a bug that makes me really sad....

 > Thus you at least don't get these bogus warnings/error markers.

+1 excellent. Not having some warnings is way better than
polluting the workspace with wrong error messages...

Does the parser work in that case correctly. I think the change in JavaScript that causes lots of problems is that keywords can be used as keys of objects and when there is a `.` before the word.

Classical lexer/parsers handle language keywords special.
I guess the PR solves this problem....

Michael

On 2015-07-01 13:45, Max Rydahl Andersen wrote:
>
> wtp-dev is where you should raise this.
>
> We have a PR for SR1 that will go in an disable this 1998 crappy validation.
>
> Thus you at least don't get these bogus warnings/error markers.
>
> /max
>
>>
>> I am excited about mars being out. But there is a bug, that makes me 
>> really really sad. The most popular eclipse package is JavaEE and it 
>> contains JavaScript. But eclipse supports only JavaScript 1998.
>>
>> https://bugs.eclipse.org/bugs/show_bug.cgi?id=223131
>>
>> The most annoying problem is that modern versions of javascript allow 
>> keywords if they are part of a data structure:
>>
>> promise.catch(function(){...});
>> var foo {
>>    default: 42
>> }
>>
>>
>>
>>
>> Many libraries use `throw` and `catch` as methods on objects and this 
>> causes a lot of errors and the rest of the file cannot be parsed.
>>
>> I know there are a lot of different javascript solutions out there 
>> that work better than this. But, the out of box experience with 
>> eclipse is, well suboptimal.
>>
>> Is there anything the architecture council can do about this?
>>
>>
>> Michael
>>
>>
>> _______________________________________________
>> eclipse.org-architecture-council mailing list 
>> eclipse.org-architecture-council@xxxxxxxxxxx
>> https://dev.eclipse.org/mailman/listinfo/eclipse.org-architecture-cou
>> ncil
>>
>> IMPORTANT: Membership in this list is generated by processes internal to the Eclipse Foundation.  To be permanently removed from this list, you must contact emo@xxxxxxxxxxx to request removal.
>
>
> /max
> http://about.me/maxandersen
>

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

IMPORTANT: Membership in this list is generated by processes internal to the Eclipse Foundation.  To be permanently removed from this list, you must contact emo@xxxxxxxxxxx to request removal.