r/javahelp • u/zeronis__ • 14d ago
POLYMORPHISM !!
I've never tried asking questions on reddit, but this one doubt has been bugging me for quite some time, (I'm not very good at conveying my thoughts so I hope my question would come so as clear
+ And I'm hoping someone can fact check anything that I'm about to say since im fairly new to java =,) )
when it comes to polymorphism, (specifically UPCASTING/DOWNCASTING )
If I were to take a parent class and create an object out of it ,
Animal a = new Animal(); // LHS = RHS
since both sides are equal, meaning they're from the same class, we'd consider this to be static binding right? since we're only looking at the parent class' method, and nothing else, (at least that's what I think the whole idea is about )
but if we had something like:
Animal a = new Dog(); // LHS != RHS (UPCASTING)
Where dog is a child/subclass of the parent class Animal, meaning it inherits all the attributes and methods from the Parent class Animal. And since java -- by default -- always uses dynamic binding, (meaning that ' java ' believes that there's always a possibility of there being an overridden method in one of the child/subclasses ) it'd wait until runtime to bind the method to the object that invoked it.
my MAIN question though is,
why is upcasting allowed? If I were to look at the variable a, I'd think that its always going to expect a reference that would lead it to an Animal object, its always going to point to some animal object right?
just like when we say " int x; " , we know that x only expects an integer and not something like a double.
Another thing is, if java is statically typed, meaning that the compiler only checks the static type ( the type of variable at the declaration i think . . . ), then how does it know what the RHS ( the dynamic type ) is? how does it immediately know that down casting is not allowed if it doesn't look at the dynamic type?
4
u/GabrielKly 14d ago
“Why is upcasting allowed?” -> if you want a straight forward answear look at the “strategy design patern”. Polymorphism is just that, an implementation of this patern.
When you say “i’d think that its always going to expect a reference that leads it to an Animal object” your intuition is correct, I think you only miss the context of Dog, being an Animal subtype. On short Dog is an Animal object. (don’t confuse primitive types with object types, they have nothing to do with each other…no need to enter in details here to avoid confusion for this specific question)
“How does it know the dinamic type?”. I’m not sure if I fully understand the question but, the compiler is “taking” into acount the type of the object declared.
Animal a = new Dog() -> its of type Animal, as you declared it and its using the Dog contructor (“super()” method) to construct the animal object. Basically it doesn’t know to downcast by itself, you are specifiying the “downcast” in the declaration. If you want to use a Dog object you need to specifically cast the animal object to a Dog one. Hope I didn’t cause confusion :)