There is not as much to remember about overloading methods as compared to overriding methods.
From RHE, an overloaded method is any method in the same class including methods inherited from a superclass with the same name but different argument lists.
They are really independent methods and return type, accessibility, and exception lists can vary any way you want.
So for you example, yes that is overloading as you are giving them a different order. The test will try to get you by having two methods and just change the return type like this:
public int methodA(String s)
private String methodA(String t)
This is not overloading and will cause a compile error because the compiler looks at the argument list and not return type. This is logical when you think about it because when calling a method, the compiler would not know which method you wanted if both took just one string value. The compiler is not going to know what the return type is going to be, so it wouldn't know where to start. But if you had one taking an int and the other taking a String, the compiler will know which method to call by the argument you pass in.
One more note, overloading is not considered Object Oriented programming, while overriding is considered OOP. Just in case you get that question also. Overriding has to do with inheritance and
polymorphism while overloading is just a play on names and method calls.
All this can be found in RHE chapter 6.
Bill
