When a cycle exists between classes during their ``++static++`` initialization, the results can be unpredictable because they depend on which class was initialized first.


== Noncompliant Code Example

[source,java]
----
public class A {
  public static int a = B.b + 1;  // Noncompliant; sometimes a = 1, others a = 2
}

public class B {
  public static int b = A.a + 1;  // Noncompliant; sometimes b = 1, others b = 2
}
----


== See

* https://www.securecoding.cert.org/confluence/display/java/DCL00-J.+Prevent+class+initialization+cycles[CERT, DCL00-J.] - Prevent class initialization cycles


ifdef::env-github,rspecator-view[]

'''
== Implementation Specification
(visible only on this page)

include::message.adoc[]

'''
== Comments And Links
(visible only on this page)

include::comments-and-links.adoc[]
endif::env-github,rspecator-view[]