Re: [jdt-ui-dev] Question concerning the reconciler

[Martin Aeschlimann <martin_aeschlimann@xxxxxxxxxx>]

I can speak for quick fixes that work
on the reconciled AST and are accessing AST nodes and bindings very locally;
around a problem or at the cursor position and bindings of the context
(surrounding method, type...) and some bindings reachable through these
bindings (super type, parameter types, etc). My guess is that the average
quick fix accesses 3 - 4 bindings.
The highest binding consumer on the
reconciled AST is probably 'mark occurrence' using the binding directly
at nodes, but then no bindings reachable from that binding (e.g. declared
methods, super type..)

A lazy approach to create (and even
evaluate) bindings seems to be most suited for these use cases.

Hope that helps
Martin

Olivier Thomann <Olivier_Thomann@xxxxxxxxxx>
Sent by: jdt-ui-dev-bounces@xxxxxxxxxxx

08.04.2005 18:04

Please respond to
"Eclipse JDT UI developers list." <jdt-ui-dev@xxxxxxxxxxx>

To	jdt-ui-dev@xxxxxxxxxxx
cc
Subject	[jdt-ui-dev] Question concerning the reconciler

Hi, 

In order to know how I can fix https://bugs.eclipse.org/bugs/show_bug.cgi?id=89281,
I'd like to know what operations are done on the DOM/AST tree once it is
returned by the reconciler. I didn't see a performance test that is specific
to the reconciling of a compilation unit. 

The attached patch might end up with slower performance if the bindings
like fields and methods are never requested for the requested units, but
if these bindings are retrieved frequently, the patch won't impact the
speed and it will save memory. 

Olivier_______________________________________________
jdt-ui-dev mailing list
jdt-ui-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/jdt-ui-dev