Howdy --
In this new 1.4 version of the exam, we tried to modify the language to change the use of "inner class" to "nested class" in all cases, static or not. But I'm not certain we were 100% successful on changing everything.
But here's the breakdown of terminology you *might* see, and what it means on the exam:
* Nested class
-this could be either static or non-static
* Inner class
- this could *also* mean either static or non-static
* Top-level nested class
Definitely means STATIC nested/inner class
* Non-static inner class or non-static nested class
-speaks for itself
* Static inner class or static nested class
Definitenly means STATIC nested/inner class
So....
STATIC inner/nested class could be called any of the following:
* Top-level nested class
* static inner class
* static nested class
a NON-static inner/nested class could be called any of the following:
* nested class
* inner class
* method-local inner class
* anonymous inner class
The only issue you might have is that you *might* see a question similar to the following:
Which of these modifiers may be used on with an inner class?
static
transient
synchronized
strictfp
and so on...
In this case, it would be appropriate to choose "static" as a correct answer. Some people have found this disturbing because they assume that the term "inner class" automatically means DEFINITELY NOT STATIC, but we're using the term "inner" in a broader sense -- in the old, original sense of the
word.
But as I said, I'm pretty sure we got rid of all of those anyway. Just know that you will NEVER be expected to recognize the difference between "inner" and "nested".
Yes, you can count on me to make things even more confusing
cheers,
Kathy