Thread: Finding where variable is defined and where referenced

In Eclipse:

To find declaration:

right click on the variable/method/class/etc. and choose "Open Declaration" (shortcut key is F3).

To find usage:

right click on the variable/method/class/etc and choose "References" and then in what context you want to find it's usage (in the current project, hierarchy, or workspace, or a specific working set).

You can also do a "Java search" (click the little arrow next to the search icon and choose "Java search") to search for a variety of different fields, methods, classes, etc. in whatever context you want and even how Eclipse thinks you're using it at that time.

To enable Eclipse's JDT to determine what to do about name shadowing in various contexts (ignore, warn, or throw a compiler error):

Windows > Preferences > Java > Compiler > Error/Warnings > Name Shadowing and Conflicts

The available items are:
Field declaration hides another field or variable (this is probably one you want to change)
Local variable declaration hides another field or variable (this is probably one you want to change)
Type parameter hides another type
Method does not override package visible method
Interface method conflicts with protected 'Object' method

Note that these settings can be changed on a project-by-project basis, too.

Right click on the project in the Package Explorer, then choose:

Properties > Java Compiler > Errors/Warnings > Enable project specific settings

I tend to use shadowing in constructors and setters. Mostly it's because often times I use Eclipse's automated generate getter/setter and generate constructor using fields functionality, but also because then I can quickly identify which method argument should match up with which field in my class.

Originally Posted by Norm

Which IDE(s) does that work in?

Does it tell you which ones are shadowed?

Hi, I'm talking about Eclipse. I didn't mean it shows shadowed variables, just easily find occurrences (including variables and shadowed ones).

java memory

Originally Posted by Norm

The problem is the shadowed variables NEED to be marked with a warning. If you know to search for a variable to see if its shadowed then you won't need the warning.

Okay guy, I was missing the point.

java memory