The answer is A, B, E and F (correct me if you disagree!)
A: b2 refers to a 2d array, which b is. B: b refers to a byte value, which b3 is. E: b2 refers to a single byte value, as does b F: b2 refers to a 2d array, which 'big' is.
C: b2 refers to a 1d array, whereas b refers to a single byte D: b2 refers to a 1d array, whereas b is a 2d array
If you can't just see the number of dimensions when looking at the code you could look at an array like this:
byte b2  = new byte ; //a 4d array
If you put: b2 you're referring to a single value b2 you're referring to a 1d array b2 you're referring to a 2d array b2 you're referring to a 3d array b2 you're referring to a 4d array
Notice the pattern - so you could apply this to other arrays:
e.g byte  b = new byte ; //a 2d array
b single value b 1d array b 2d array
There might be easier ways of working this out but I think once you're familiar with working with arrays (through practise) it's like doing timestables and the answer is obvious. [ November 27, 2006: Message edited by: Andy Morris ]
Greg L Tonn
Joined: Nov 27, 2006
So it doesn't matter what the size of the array is only the demensions?
Joined: May 30, 2004
For compilation only the dimensions matter. For runtime the size does matter (you'll get ArrayIndexOutOfBoundsExceptions if you reference an index that is not valid).