As I stated previously, we will be using Acorn for QML. We’ve had good success with it. I don’t understand the urge to use something else but have to trust Gorkem has done a pretty good analysis and that at least JSX will be supported in the new system. If not, we could do a JSX editor that uses Acorn and leave esprima to the others.
Doug From: <[email protected]<mailto:[email protected]>> on behalf of Angelo zerr <[email protected]<mailto:[email protected]>> Reply-To: "General discussion of project-wide or architectural issues." <[email protected]<mailto:[email protected]>> Date: Friday, November 20, 2015 at 5:14 AM To: "General discussion of project-wide or architectural issues." <[email protected]<mailto:[email protected]>> Subject: Re: [wtp-dev] WTP JSDT meeting 20151117 Gorkem for esprima use parser, the only thing that I find it's shame is that acorn (as you know) provides the capability to extends it to support QML, JSX, etc I'm not sure that esprima can do that. Regard's Angelo 2015-11-18 0:05 GMT+01:00 Gorkem Ercan <[email protected]<mailto:[email protected]>>: Agenda is updated with the minutes, and the performance comparison blog entry is online now. -- Gorkem On 17 Nov 2015, at 12:02, Gorkem Ercan wrote: The agenda for today's call is at https://wiki.eclipse.org/JSDT/Confcalls/Minutes_20151117 as usual _______________________________________________ wtp-dev mailing list [email protected]<mailto:[email protected]> 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 [email protected] To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/wtp-dev
