Java Casting issue

[Bhaskar Jakkaraddi]

3. public class Redwood extends Tree {
4. public static void main(String[] args) {
5. new Redwood().go();
6. }
7. void go() {
8. go2(new Tree(), new Redwood());
9. go2((Redwood) new Tree(), new Redwood());
10. }
11. void go2(Tree t1, Redwood r1) {
12. Redwood r2 = (Redwood)t1;
13. Tree t2 = (Tree)r1;
14. }
15. }
16. class Tree { }

Would some one explain easy way to figure out casting run time error in the above type of code?

[Stephan van Hulst]

Because at line 9 you're making a new Tree, and casting it to a Redwood. Redwoods may be Trees, but Trees are not Redwoods.

[Campbell Ritchie]

Please use the code button and indent your code correctly; your posting is difficult to read otherwise.

[Mohamed Sanaulla]

In real implementations- Its always better to use instance of before casting, so that you can avoid the class cast exception.

In your first go2() call at line 8- You are creating an Instance of Tree. And then in the go2() method you are trying to cast it to Redwood which Is not possible.

You can try passing in an Instance of Redwood as the first argument to go2() in which case it doesnt throw the exception. At run time JVM checks what object actually it is- a Tree or a Redwood and checks if it can do the cast. If its a Tree object it throws an Exception as already mentioned by Stephan.

[Wouter Oet]

And it would be nice to quote the source.

[Campbell Ritchie]

mohammed sanaullah wrote:In real implementations- Its always better to use instance of before casting, . . .

Wouldn't it be better to design your application to avoid casting at all?

[Mohamed Sanaulla]

Campbell Ritchie wrote:Wouldn't it be better to design your application to avoid casting at all?

Agree. Casting at times will lead to problems.

[Campbell Ritchie]

mohammed sanaullah wrote: . . . Agree. . . .