org.sonar.l10n.java.rules.squid.S1444.html Maven / Gradle / Ivy

Go to download

There is no good reason to declare a field "public" and "static" without also declaring it "final". Most of the time this is a kludge to share a state among several objects. But with this approach, any object can do whatever it wants with the shared state, such as setting it to null.

Noncompliant Code Example
public class Greeter {
public static var foo:Foo = new Foo(...);
...
}


Compliant Solution
public class Greeter {
public static const FOO:Foo = new Foo(...);
...
}