In Programming, if we assign a value to a local variable, but the value is not read by any subsequent instruction, then it's called a Dead Store. Generally, tools like FindBugs can report these kind of programming mistakes as warnings.
| Property | Value |
| p:abstract
| - In Programming, if we assign a value to a local variable, but the value is not read by any subsequent instruction, then it's called a Dead Store. Generally, tools like FindBugs can report these kind of programming mistakes as warnings.
Java example of a Dead Store:
// DeadStoreExample.java
import java.util.ArrayList;
import java.util.List;
public class DeadStoreExample {
public static void main(String args) {
List list = new ArrayList; // Dead Store here.
list = getList;
System.out.println(list);
}
private static List getList {
// Some intense operation and finally we return a java.util.List
return new ArrayList;
}
}
In the above code a List object was created but was never used. Instead, in the next line the reference variable is pointing to some other object in the heap. The object created on line number 6 is never used and hence it's a dead store. (en)
|
| p:hasPhotoCollection
| |
| rdfs:comment
| - In Programming, if we assign a value to a local variable, but the value is not read by any subsequent instruction, then it's called a Dead Store. Generally, tools like FindBugs can report these kind of programming mistakes as warnings. (en)
|
| rdfs:label
| |
| skos:subject
| |
| foaf:page
| |