The JCGLClearSpecification value
can be re-used indefinitely. The API also provides optional strict
checking which can, for example, raise an exception if the programmer
attempts to clear the depth or stencil buffer without the current
framebuffer actually having one
[4].
This is usually the result of the programmer forgetting to
attach a depth/stencil attachment on framebuffer creation, and
can lead to difficult-to-trace bugs.