Access Modifier for Methods

[Thomas Markl]

Access Modifier for Methods

abstract class AbstractTest {
  int x = 3;
  abstract void method();
  int getX() {return x;}
}
public class Test36 extends AbstractTest {
  public void method() { 
     //abstract class has to be extended in implementing class
     //and have either implement abstract methods or declare 
     //them abstract again.
     //If they implement the abstract method as happened here
     //then it MUST HAVE THE ACCESS MODIFIER "PUBLIC"!!!!!!
     System.out.println("method "+ x);
  }
  static public void main(String args[]) {
     Test36 po = new Test36();
     po.method();
  }
}

Questions:
a) It is ok to say „static public void main(String args[]) ..“ (True/False)
b) It is ok to say „public void static main(String args[]) ..“ (True/False)
c) It is ok to say „void abstract method();“ (True/False)
d) It is ok to say „void method() {} instead of public void method() {}
When you implement abstract method (True/False)

Please answer and give a reason.
Thanks.
Thomas.

[Jessica Sant]

You can answer the true/false questions yourself -- plop the code in a compiler, what happens when you substitute these lines in?
a) static public void main(String args[])
b) public void static main(String args[])
c) void abstract method()
d) void method() {} instead of public void method() {}

[Anthony Villanueva]

Originally posted by Thomas Markl:
Questions:
a) It is ok to say „static public void main(String args[]) ..“ (True/False)
b) It is ok to say „public void static main(String args[]) ..“ (True/False)
c) It is ok to say „void abstract method();“ (True/False)
d) It is ok to say „void method() {} instead of public void method() {}
When you implement abstract method (True/False)

Please answer and give a reason.

For the example given above:
a. True
b. False. Modfiers + return value in that order, e.g. public static void main(String args[])
c. False. See b.
d. True. An overriding method can be at most as restrictive as the method being overriden.