TICS Coding Standard Viewer 
TIOBE Software Quality Framework
Print-friendly version
©TIOBE Software www.tiobe.com
 
TIOBE - Java Coding Standard
Search

Category: Naming

Synopsis:The Naming Ruleset contains a collection of rules about names - too long, too short, and so forth.


Description:
The Naming Ruleset contains a collection of rules about names - too long, too short, and so forth.

Coding Rules

NameCheckedSynopsis
Naming1 Checked automatically with code checker Avoid variables with short names
Naming2 Checked automatically with code checker Avoid excessively long variable names
Naming3 Checked automatically with code checker Avoid using short method names
Naming4 Checked automatically with code checker Use naming conventions for variables
Naming5 Checked automatically with code checker Method name does not begin with a lower case character
Naming6 Checked automatically with code checker Class names should begin with an uppercase character
Naming7 Checked automatically with code checker Abstract classes should be named 'AbstractXXX'
Naming8 Checked automatically with code checker Avoid using dollar signs in variable/method/class/interface names
Naming9 Checked automatically with code checker Classes should not have non-constructor methods with the same name as the class
Naming10 Checked automatically with code checker The method name and return type are suspiciously close to hashCode()
Naming11 Checked automatically with code checker The field name indicates a constant but its modifiers do not
Naming12 Checked automatically with code checker The method name and parameter number are suspiciously close to equals(Object)
Naming13 Checked automatically with code checker It is somewhat confusing to have a field name matching the declaring class name
Naming14 Checked automatically with code checker It is somewhat confusing to have a field name with the same name as a method
Naming15 Checked automatically with code checker Don't define methods with the same name as the class name
Naming16 Checked automatically with code checker All classes and interfaces must belong to a named package
Naming17 Checked automatically with code checker Package name contains upper case characters
Naming18 Checked automatically with code checker Avoid naming non-fields with a member-like prefix
Naming101 Checked automatically with code checker Treat acronyms as words