Declaring multiple variables in a single declaration could cause confusion about the types of variables and their initial values. In particular, do not declare any of the following in a single declaration:
- variables Variables of different types
- a A mixture of initialized and uninitialized variables
In general, you should declare each variable on its own line with an explanatory comment regarding its role. Although it is While not required for conformance with this guideline, this practice is also recommended in the Code Conventions for the Java Programming Language, Section 6§6.1, "Number Per Line" [Conventions 2009].
When more than one variable is declared in a single declaration, ensure that both the type and the initial value of each variable are self-evident.
This guideline applies to
- local Local variable declaration statements [Java 2005JLS 2013, §14 §14.4]
- field Field declarations [Java 2005JLS 2013, §8 §8.3]
- field Field (constant) declarations [Java 2005JLS 2013, §9 §9.3]
Noncompliant Code Example (Initialization)
This noncompliant code example might lead a programmer or reviewer to mistakenly believe that both i
and j
are initialized to 1. In fact, only j
is initialized; , while i
remains uninitialized.:
Code Block | ||
---|---|---|
| ||
int i, j = 1;
|
Compliant Solution (Initialization)
In this compliant solution, it is readily apparent that both i
and j
are initialized to 1.:
Code Block | ||
---|---|---|
| ||
int i = 1; // purposePurpose of i... int j = 1; // purposePurpose of j... |
Compliant Solution (Initialization)
In this compliant solution, it is readily apparent that both i
and j
are initialized to 1.:
Code Block | ||
---|---|---|
| ||
int i = 1, j = 1;
|
Declaring each variable on a separate line is the prefered preferred method. However, multiple variables on one line are acceptable when they are trivial temporary variables such as array indexesindices.
Noncompliant Code Example (Different Types)
In this noncompliant code example, the programmer declares multiple variables, including an array, on the same line. All instances of the type T
have access to methods of the Object
class. However, it is easy to forget that arrays require special treatment when some of these methods are overridden.
Code Block | ||
---|---|---|
| ||
public class Example<T> {
private T a, b, c[], d;
public Example(T in) {
a = in;
b = in;
c = (T[]) new Object[10];
d = in;
}
}
|
When an Object
method, such as toString()
, is overridden, a programmer could accidentally provide an implementation for type T
that fails to consider that c
is an array of T
, rather than a reference to an object of type T
.
Code Block |
---|
public String toString() { return a.toString() + b.toString() + c.toString() + d.toString(); } |
However, the programmer's actual intent could have been to invoke toString()
on each individual element of the array c
.
Code Block |
---|
// Correct functional implementation public String toString(){ String s = a.toString() + b.toString(); for (int i = 0; i < c.length; i++){ s += c[i].toString(); } s += d.toString(); return s; } |
Compliant Solution (Different Types)
This compliant solution places each declaration on its own line and uses the preferred notation for array declaration.:
Code Block | ||
---|---|---|
| ||
public class ExampleExample<T> { private T a; // purposePurpose of a... private T b; // purposePurpose of b... private T[] c; // purposePurpose of c[]... private T d; // purposePurpose of d... public Example(T in){ a = in; b = in; c = (T[]) new Object[10]; d = in; } } |
Exceptions
Applicability
Declaration of multiple variables per line can reduce code readability and lead to programmer confusion.
When more than one variable is declared in a single declaration, ensure that both the type and the initial value of each variable are self-evident.DCL01-EX0: Note that the declaration of a loop counter in a for
statement is in violation of this guideline because the declaration is not on its own line with an explanatory comment about the variable's role. However, declaration of loop indices in for
statements is not only a common idiom; it also provides the benefit of restricting the scope of the loop index to the for
loop itself. This is a specific reason to relax this guideline.
Declarations of loop indices should be included within a for
statement even when this results in variable declarations that lack a comment about the purpose of the variable:
Code Block | ||
---|---|---|
| ||
public class Example { void function() { int mx = 100; // Some max value for (int i = 0; i < mx; ++i ) { /* ... */ } |
Risk Assessment
Declaration of multiple variables per line can reduce code readability and lead to programmer confusion.
Guideline | Severity | Likelihood | Remediation Cost | Priority | Level |
---|---|---|---|---|---|
DCL01-J | low | unlikely | low | P3 | L3 |
Related Guidelines
C Secure Coding Standard: "DCL04-C. Do not declare more than one variable per declaration"
C++ Secure Coding Standard: "DCL04-CPP. Do not declare more than one variable per declaration"
Bibliography
}
}
|
Such declarations are not required to be in a separate line, and the explanatory comment may be omitted.
Automated Detection
Tool | Version | Checker | Description | ||||||
---|---|---|---|---|---|---|---|---|---|
Parasoft Jtest |
| CERT.DCL52.MVOS | Do not declare multiple variables in one statement | ||||||
SonarQube |
| S1659 |
Bibliography
§6 |
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="c0755042-3223-4087-8a49-2ae07bcfbe49"><ac:plain-text-body><![CDATA[
[[Conventions 2009
AA. Bibliography#Conventions 09]]
.1, "Number Per Line" |
]]></ac:plain-text-body></ac:structured-macro>
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="64178e3c-5333-41d8-a138-90bcabc34253"><ac:plain-text-body><![CDATA[
] | Rule 9 |
, Put Single Variable Definitions in Separate Lines | |
[JLS 2013] |
]]></ac:plain-text-body></ac:structured-macro>
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="f7c6d656-89b5-4387-9445-30b075cf5591"><ac:plain-text-body><![CDATA[
[[JLS 2005
AA. Bibliography#JLS 05]]
http://java.sun.com/docs/books/jls/third_edition/html/classes.html#8.3]
]]></ac:plain-text-body></ac:structured-macro>
...
DCL00-J. Use visually distinct identifiers 01. Declarations and Initialization (DCL) DCL02-J. Use meaningful symbolic constants to represent literal values in program logic