Which statements about constants in Java are true?

The statement that a named constant makes computations that use it clearer is true because named constants help improve code readability and maintainability. By using descriptive names for constants, programmers can convey the purpose of a specific value without requiring readers to remember what a raw numeric value represents. This means that instead of just seeing a number in the code, such as 3.14, a programmer might see a constant like PI, which clearly indicates that the value represents the mathematical constant Pi. This practice reduces the likelihood of errors and makes the code easier to understand for both the original programmer and anyone else who might read it later.

In contrast to this, other statements suggest misunderstandings about how constants should be used in Java. For instance, constants are not limited to only integer values, as they can also represent floating-point numbers, characters, strings, and more. Additionally, while variables can be initialized with a specific value and may not change if they are declared as constants, the distinction lies in that constants must use the final keyword to prevent any reassignment. Lastly, constants are typically named using uppercase letters with underscores separating words, which is a widely accepted naming convention in Java rather than being referred to by lowercase letters.