Attachment #236601 for bug #389787

Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Lines 11-16 Link Here

(-)dom/org/eclipse/jdt/core/dom/Expression.java (-1 / +9 lines)
11	*	11	*
12	* Contributors:	12	* Contributors:
13	* IBM Corporation - initial API and implementation	13	* IBM Corporation - initial API and implementation
		14	* Jesper Steen Moller - minor JavaDoc for bug 389787
14	*******************************************************************************/	15	*******************************************************************************/
15		16
16	package org.eclipse.jdt.core.dom;	17	package org.eclipse.jdt.core.dom;
Lines 110-116 Link Here
110	* Note that bindings are generally unavailable unless requested when the	111	* Note that bindings are generally unavailable unless requested when the
111	* AST is being built.	112	* AST is being built.
112	* </p>	113	* </p>
113	*	114	* <p>
		115	* Note that the binding returned is based on how the construct is is resolved,
		116	* in context. For instance, if the expression <code>obj.field</code> is a field reference
		117	* to <code>field</code> inside the class A, the type binding returned for <code>obj</code> would
		118	* return a binding for A', even if the declared type of obj was a subclass of A, satisfying
		119	* <code>fieldAccess.getExpression().resolveTypeBinding()
		120	* == fieldAccess.resolveFieldBinding().getDeclaringClass()</code>
		121	* </p>
114	* @return the binding for the type of this expression, or	122	* @return the binding for the type of this expression, or
115	* <code>null</code> if the type cannot be resolved	123	* <code>null</code> if the type cannot be resolved
116	*/	124	*/

Return to bug 389787