What does Overloading a Method mean in practice?

What does Overloading a Method mean in practice?

• A. Giving two methods the same name but different method signatures.
• B. Providing two methods with identical names and identical signatures.
• C. Overriding a method in a subclass.
• D. Using the same name for different classes.

Answer: (A)

Overloading a method means having multiple methods with the same name in the same scope but with different parameter lists. This lets the same operation be performed in slightly different ways based on the inputs, while keeping a single, familiar name you call. The reason this is the best description is that the key idea is the same name with different signatures (different numbers or types of parameters). The return type usually isn’t what distinguishes the versions, so you can’t rely on the return type alone to tell them apart. For example, you might have a method named print that works with different inputs: one version takes an int and prints a number, another takes a String and prints text. When you call print(5), the compiler selects the int version; when you call print("hi"), it selects the String version. This is different from providing two methods with identical signatures, which would be a conflict. It’s also different from overriding, where a subclass provides a new implementation for a method with the same signature as one in a parent class. And it isn’t about using the same name across different classes—that’s just naming, not overloading within a class.

Overloading a method means having multiple methods with the same name in the same scope but with different parameter lists. This lets the same operation be performed in slightly different ways based on the inputs, while keeping a single, familiar name you call.

The reason this is the best description is that the key idea is the same name with different signatures (different numbers or types of parameters). The return type usually isn’t what distinguishes the versions, so you can’t rely on the return type alone to tell them apart.

For example, you might have a method named print that works with different inputs: one version takes an int and prints a number, another takes a String and prints text. When you call print(5), the compiler selects the int version; when you call print("hi"), it selects the String version.

This is different from providing two methods with identical signatures, which would be a conflict. It’s also different from overriding, where a subclass provides a new implementation for a method with the same signature as one in a parent class. And it isn’t about using the same name across different classes—that’s just naming, not overloading within a class.