The Java Language Specification, Third Edition

NAMES Method Names 6.8.4
DISCUSSION
If a generic method appears inside a generic class, it’s a good idea to avoid using the same
names for the type parameters of the method and class, to avoid confusion. The same
applies to nested generic classes.
DISCUSSION
These conventions are illustrated in the code snippets below:
public class HashSet extends AbstractSet { ... }
public class HashMap extends AbstractMap { ... }
public class ThreadLocal { ... }
public interface Functor {
T eval() throws X;
}
When type parameters do not fall conveniently into one of the categories mentioned,
names should be chosen to be as meaningful as possible within the confines
of a single letter. The names mentioned above (E , K, T, V, X) should not
be used for type parameters that do not fall into the designated categories.
6.8.4 Method Names
Method names should be verbs or verb phrases, in mixed case, with the first letter
lowercase and the first letter of any subsequent words capitalized. Here are some
additional specific conventions for method names:
• Methods to get and set an attribute that might be thought of as a variable V
should be named getV and setV. An example is the methods getPriority
and setPriority of class Thread.
• A method that returns the length of something should be named length,asin
class String.
DRAFT
• A method that tests a boolean condition V about an object should be named
isV. An example is the method isInterrupted of class Thread.
149