Enthuware

Similarly, literals such as the numbers 1, 2, and 3, or the characters written in code within single quotes such as ’a’, or boolean values true and false, are all compile time constants because the compiler knows that these values will never change.

will be removed tomorrow

Username987654 wrote: ↑

Sun Nov 25, 2018 2:32 am

1.9.11

Similarly, literals such as the numbers 1, 2, and 3, or the characters written in code within single quotes such as ’a’, or boolean values true and false, are all compile time constants because the compiler knows that these values will never change.

(In my Review Copy) The text preceding this statement and 3.3 Declare and Initialize variables' examples appear to contradict the above (when not specified as final)? This does not currently appear to be found on the Errata page? Is the quote an error and/or possible opportunity for clarification?

For example, if you define an int variable as final int x = 10; then x is a compile time constant because the compiler knows that x will
always have a value of 10 at run time

will be removed tomorrow

Was the whole section removed in a later edit?

Similarly (***when defined as final?***[would better? clarify this quote?]), literals such as the numbers 1, 2, and 3, or the characters written in code within single quotes such as ’a’, or boolean values true and false, are all compile time constants because the compiler knows that these values will never change.

Username987654 wrote: ↑

Sun Nov 25, 2018 10:48 am

Similarly (***when defined as final?***[would better? clarify this quote?]), literals such as the numbers 1, 2, and 3, or the characters written in code within single quotes such as ’a’, or boolean values true and false, are all compile time constants because the compiler knows that these values will never change.