0

Well, the question is not what is method or variable hiding. The question is why is it discouraged to use it.

If some one is clear of static and dynamic binding , everything seems logical. I agree that static variables and methods should be called by class Name and not by object reference to make code easy to understand , but why is this practice of hiding discouraged ?

Is it just because so that code becomes even more easier to read or is it some thing else ?

Number945
  • 4,631
  • 8
  • 45
  • 83
  • 1
    can you make an example of what you mean by hiding? – luksch Apr 12 '18 at 17:21
  • 1
    https://docs.oracle.com/javase/tutorial/java/IandI/hidevariables.html – baao Apr 12 '18 at 17:22
  • @luksch please see this : https://docs.oracle.com/javase/tutorial/java/IandI/override.html – Number945 Apr 12 '18 at 17:23
  • 4
    s/easier to read/more difficult to screw up/ – Louis Wasserman Apr 12 '18 at 17:33
  • Sorry, but I don't get your point. "Hiding" is an essential point in JAVA. It seems that you misunderstood something in the Oracle tutorial. It is always recommendable to keep the access to your variables limited to getters and setters except for static variables. Otherwise you would loose control over what other classes do with your values. –  Apr 12 '18 at 17:46

2 Answers2

0

It dont make a lot of sense to do overriding of a static method, because the overriding was though for polymorphism things, but you are not manipulating objects but classes instead when you´r calling the method. So it could take you to execute it in a non-static way and you would be subject to the type of the declared variable and NOT the instance of it.

Augusto93
  • 1
  • 2
0

I'm actually pretty happy with the docs here (thanks @baao): https://docs.oracle.com/javase/tutorial/java/IandI/override.html.

Note the difference between hiding and overriding: - Hiding refers to a static method in a subclass with the same signature as the static method in the superclass and is considered bad practice - Overriding is what allows subclasses to modify inherited behavior, and is not bad practice.

I'll use the example again from the docs: 

public class Animal {
    public static void testClassMethod() {
        System.out.println("The static method in Animal");
    }
    public void testInstanceMethod() {
        System.out.println("The instance method in Animal");
    }
}

public class Cat extends Animal {
    public static void testClassMethod() {
        System.out.println("The static method in Cat");
    }
    public void testInstanceMethod() {
        System.out.println("The instance method in Cat");
    }

    public static void main(String[] args) {
        Cat myCat = new Cat();
        Animal myAnimal = myCat;
        myAnimal.testClassMethod();
        // "The static method in Animal"
        myAnimal.testInstanceMethod();
        // "The instance method in Cat"
    }
}

To quote another answer as well from What is method hiding in Java? Even the JavaDoc explanation is confusing: "Calling static methods on instances rather than classes is a very bad practice, and should never be done."

kyle
  • 691
  • 1
  • 7
  • 17
  • This does not answer the question which very clearly asks **why**. You state "is considered bad practice" and "Calling static methods on instances rather than classes is a very bad practice, and should never be done." yet do not answer the question directly. – Annan Yearian Feb 07 '23 at 11:01