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

Bug 255936

Summary: Parsing / code scope error for inner classes
Product: [Eclipse Project] JDT Reporter: Stephan Fuhrmann <stephan.fuhrmann>
Component: CoreAssignee: Ayushman Jain <amj87.iitr>
Status: CLOSED WONTFIX QA Contact:
Severity: normal    
Priority: P3 CC: frederic_fusier, Olivier_Thomann, srikanth_sankaran
Version: 3.4   
Target Milestone: ---   
Hardware: PC   
OS: Linux   
Whiteboard: stalebug

Description Stephan Fuhrmann CLA 2008-11-20 04:40:14 EST
Members of inner classes are "visible" to the parser AFTER the visible class.

Example:

public class SimpleAggregationNode extends DefaultNode {
...
	private String aloah;

	private class AggregateConfig {
		String fromEvents[];
		String toEvents[];
		String matchProperties[];
		String aggregateProperties[];
	}
	
	/** The aggregate configs extracted from #a */
	private List<AggregateConfig> aggregateConfigs;
...
}

Look at the place with "#a". If you press CTRL+Space here Eclipse will give the members that are in scope as proposals for a {@link #a...}. Unfortunately at this place the editor has still the inner class AggregateConfig in scope.

This means #aggregateProperties gets proposed and not #aloah as it should be. One assign statement later the inner class scope is gone.
Comment 1 Eclipse Genie CLA 2020-02-21 13:59:55 EST
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're closing this bug.

If you have further information on the current state of the bug, please add it and reopen this bug. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.