This week's book giveaway is in the OCMJEA forum. We're giving away four copies of OCM Java EE 6 Enterprise Architect Exam Guide and have Paul Allen & Joseph Bambara on-line! See this thread for details.
byte b = 10;
results in a compile time error.
byte b = 10;
integer i = 128;
System.out.println(b == i);
runs fine and produces a result of false.
Why byte can't be compared to int in (1), whereas byte can be compared to int in (2) ?
Alternatively, why code in (1) cannot compare byte and int values (but will result in loss of precision), whereas code in (2) could compare a byte and int fine ?
I see. So it is the Java language specification that tells this. But it seems unnatural to force the switch statement to this behavior whereas it isn't the case while using == operator. One of those weird, strange quirks one has to remember
If you think about it, it is logical. The == operator allows comparison between byte and int because you might compare two variables i.e. something like this
So the compiler cannot tell whether i's value will be in the range of byte or not. But in the case of a switch statement, you cannot use variables as case values, so at the compile time you already know whether the case value is assignable to the switch expression or not. What is the whole point of allowing a case which can never be true?? In the example you showed, the case 128 can never be true, so what is the point of allowing it?? By flagging this as an error, the compiler helps you avoid such circumstances as its definitely a logical error...