Hi
Great. That should be a really easy fix then. All these files are
being opened by EMF, so EMF can cache the result of a first lazy
System property read for the lifetime of the EMF plugin. Maybe it
is an idiom that should be applied more universally, until Oracle
fixes the bug.
(It might have an accidental further benefit to Xtext that can
create huge numbers of EMF resources, one per Java type, hopefully
without preparing a parser for each. I looked at https://bugs.eclipse.org/bugs/show_bug.cgi?id=543742
and it looks like a many resources not parser issue.)
Regards
Ed Willink
On 24/01/2019 16:06, Mickael Istria
wrote:
[...]a faster parser[...]
According to the tweet, it's not about a faster parser.
Also, the suggested value for the parser is actually the
default one in most JVMs.
it's about explicitly defining the property seems to save
time in resolving the abstract parser to a concrete one, as
it "just" reads the system property and load the class
instead of checking possible extensions/service providing
this.
_______________________________________________
ide-dev mailing list
ide-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/ide-dev
