• 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 ...
  • Campbell Ritchie
  • Devaka Cooray
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
  • paul wheaton
  • Jeanne Boyarsky
  • Tim Cooke
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Tim Moores
  • Mikalai Zaikin
  • Carey Brown

Java Study Guide OCP I can't get the clue of hiding/polymorphism?

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

I thought I understand but now I have question Java OCP guide 17 Q22.
The two lines marked with //*,  is my question, especially the first one. The second is more to check if my clue is right?
(I have put the comments so that you can more or less follow what and how I think.)

And what I understand, correct me if I'm wrong At compile-time than the reference type is important and at Runtime although it behaves as Child object or not? (polymorphism, right?
Assigning the value to name and t.name is done at run-time, right?

I hope that I have not mixed up (a lot of) things?

Posts: 78698
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Don't say, “reference type.” A reference type means a type from which objects are (at least in theory) created, meaning arrays, classes, and interfaces. The opposite of reference type is, “primitive type," and there are eight kinds of primitive type. You doubtless meant to say, “declared type.”
Please don't write comments such as to produce long lines, because they are so difficult to read.Write /* comments */ instead, and spread them over multiple lines.
Please avoid single‑letter names for parameters or variables as much as possible; use names that make their meaning obvious.
What does the book say about the problem? Which book is it? Is it Boyarsky and Selikoff? I don't have a copy. Where did the code you showed come from? It shows some poor design. I presume that poor design is there to show a point.
As far as I am concerned, polymorphism and overriding apply to instance methods, instance methods, instance methods, and instance methods. Nothing else. It doesn't even apply to private instance methods because they cannot be overridden.
If an instance method is called at runtime on the name of an object, the bytecode says to look for the method declaration in the Class<?> object that the object was derived from. That is the Cass object corresponding to the runtime type of the object.So, calling an instance method might take you to the Class<Cat> object or to the Class<Dog> object. There you might find a method definition, and that definition will be used. You might get, “Woof‑Woof” or, “Miaow.” That is called late binding, andd is also called dynamic binding and also called runtime binding.
Which version of a static method is called is determined at compile‑time. The compiler sees that the declared type is Animal and calls any static methods on that type, Animal. That is called early binding or static binding or compile‑time binding. The details of a static method are determined by static binding. All fields also undergo compile‑time binding. If you have fields with the same name in superclass and subclass, they do not override each other, but hide each other. They are two fields completely independent of each other, and therefore a potent source of confusion. The same applies to static methods; even if they have the same name, they are independent of each other and can only be hidden not overridden. No, the name field does not bind to any object, but to the declared type of the variable. That is why static members should always be referred to by ClassName.memberName and never by ObjectReferenceName.memberName.
The overridden method in Child calls the fields linked at compile‑time to its declared type, which for t is Person. Yes, that is very confusing code.
The problems of the world fade way as you eat a piece of pie. This tiny ad has never known problems:
a bit of art, as a gift, the permaculture playing cards
    Bookmark Topic Watch Topic
  • New Topic