This week's book giveaway is in the Agile/Processes forum.
We're giving away four copies of Building Green Software: A Sustainable Approach to Software Development and Operations and have Anne Currie, Sarah Hsu , Sara Bergman on-line!
See this thread for details.
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Tim Cooke
  • Campbell Ritchie
  • paul wheaton
  • Jeanne Boyarsky
  • Ron McLeod
Sheriffs:
  • Paul Clapham
  • Devaka Cooray
Saloon Keepers:
  • Tim Holloway
  • Carey Brown
  • Piet Souris
Bartenders:

Reference variable casting doubt

 
Ranch Hand
Posts: 583
Firefox Browser Notepad Windows
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator


If above program can compile and run successfully then what's problem in given below thanks

 
Bartender
Posts: 4568
9
  • Likes 1
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
In your second case, you're casting an Animal reference to a Dog reference. Now, that might work, so it will compile OK. But at run-time the JVM will look at the actual type of the object, which is Animal, and will try and cast that to a Dog. That's not possible, because an Animal is-not-a Dog, so you get a ClassCastException.

In the first example you're preceding the cast with an instanceof check. Which means that for those cases where you would get a ClassCastException (the first and last elements in the array), it doesn't try and cast. It only tries it for the case where the cast is safe - when the object actually is a Dog.

You should always check instanceof before casting an object like that unless you know you can guarantee (from your understanding of the rest of the code) that it is safe.
 
saloni jhanwar
Ranch Hand
Posts: 583
Firefox Browser Notepad Windows
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Matthew Brown wrote:In your second case, you're casting an Animal reference to a Dog reference. Now, that might work, so it will compile OK. But at run-time the JVM will look at the actual type of the object, which is Animal, and will try and cast that to a Dog. That's not possible, because an Animal is-not-a Dog, so you get a ClassCastException.

In the first example you're preceding the cast with an instanceof check. Which means that for those cases where you would get a ClassCastException (the first and last elements in the array), it doesn't try and cast. It only tries it for the case where the cast is safe - when the object actually is a Dog.

You should always check instanceof before casting an object like that unless you know you can guarantee (from your understanding of the rest of the code) that it is safe.



Thanks Matthew:)
 
reply
    Bookmark Topic Watch Topic
  • New Topic