Here we do not required to cast byte to integer.
But in switch case we are passing byte and which will consider max limit upto 127 and that's why we need to set it upto limit 127.
And if it's more then 127, as shown here we need to cast it.
As well at the time of initializing the variable, if require to set more then 127, it also required to case and give us answer "hello2".
Hi ket bhav, Thanks a bunch for your generous effort to clarify the point . My 2nd question is solved, But i still do need bug you for the 1st question, please point me out where exactly, byte is implicitly cast to int my example(this code is taken from scjp ref. material)
Adri Jamis wrote: please point me out where exactly, byte is implicitly cast to int my example(this code is taken from scjp ref. material)
byte is never implicitly casted to int...It is int which is implicitly casted to byte. See by default the all whole numbers like 23,55,1000,2055 etc all are of int data type by default (i.e. integer literals are of type int by default). So when you are writing 50 is of type int but since it is stored in byte it is implicitly casted to byte and now the question arises why implicit cast happened??? It happened because the value which i was storing (i.e. 50 in above example) was well within the range of byte which is -128 to 127.So the summary is whenever you are storing a number between -128 to 127(which are int by default) in a byte variable there will be an implicit cast. So when you are storing an number greater than 127 in byte you need to do an explicit cast. Example
I hope this answers your question number 1.