| Re: [wtp-dev] About parsing and conversion times |
Angelo,
Yes, it's tolerant and it even supports "typed _javascript_" so it parses fine declarations like that:
var x: {p: string, q: string, r: number};
--
Eugene, it's perhaps a stupid question, but closure compiler is too a tolerant parser?
2016-04-07 19:38 GMT+02:00 Gorkem Ercan <gorkem.ercan@xxxxxxxxx>:
On 7 Apr 2016, at 12:44, Eugene Melekhov wrote:
I would not hold my breath on that. Even if we can get the IP work done. We still need a converter from Closure’s IR
to DOM AST so that the current functionality continues to work.
Yes, unfortunately it's not that easy. I'd prefer to use Closure's IR directly in order to avoid conversion at all and
manipulate it directly if necessary, but this require work. I've found at least 341 file importing ASTNode in
org.eclipse.wst.jsdt.ui so you see...
Perhaps it's possible to use class derived from Closure's Node as wrapper or implement some Adaptor in Eclipse's
terminology to minimize conversion, but it depends. It's hard to say in advance.
Possible but I think it is a good idea to keep parser model and DOM model separate so that we still have options.
Also conversion from a strongly typed model to another one may actually be faster than converting from nashorn/esprima.
--
Eugene Melekhov
_______________________________________________
wtp-dev mailing list
wtp-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/wtp-dev
_______________________________________________
wtp-dev mailing list
wtp-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/wtp-dev
Eugene Melekhov
_______________________________________________
wtp-dev mailing list
wtp-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/wtp-dev