What is the use/advantage of function overloading?

Question

What is the use/advantage of function overloading?

Answer 1

IMHO the benefit is consistency in the naming of functions which perform the same task, just with different parameters.

Answer 2

A function/method is sometimes able to take different kinds of parameters in order to do it's job. This is the time for function overloading. Otherwise, you would have to have different functions for the same functionality, which is confusing and bad practice.

• Constructors are functions, so they can be overloaded. This is very handy.
• When you first get into overloading, it's easy to get over-fancy, thinking you're doing future developers a favor by giving them more convenient options. Try to avoid this. Unneeded overloads can confuse future developers and cause unnecessary code to maintain.

Answer 3

It providing multiple behaviour to same object with respect to attributes of object.

For example a method called addUs(a b) adds a and b.

So the definition will be:

int addUs(int a int b){
  return a+b;
}

But now if you want your arguments to be Objects of a class say:

class Demo{
  int height;
  int width;
}

You want the same function addUs() to return a new object which would have attributes height and width having values as sum of the height & width of the 2 arguments passed.

So now the definition would be:

Demo addUs(Demo a Demo b){
  this.height a.height + b.height;
  this.widht a.widht + b.width;
  return this;
}

Answer 4

Sometimes you have multiple ways of accomplishing the same thing based on the context and inputs available. For type-strict static languages the function definitions can be pretty rigid and need to be explicitly defined ahead of time.

Constructors are generally the best classic example of this. If you're building a complex object and don't have all the pieces, you still want to be able to pass what you have to a constructor and let it fill in the rest. And what you have may vary wildly and need to be defined in different ways as parameters to the constructors.

Answer 5

Very valid question.

You get consistency in naming, but at the cost of ambiguity about exact implementation.

• The real issue is human memory for method names, right? we find it easier to remember names that are commonly used.

• and economy of typing, allowing for shorter method names? fewer different names means (mathematically) that the name itself carries less information.

These two issues shouldn't be any concern, with IDEs that find/guess/insert method names rapidly based on the first few characters, and parameter/return types.

But I do think there is a cost, in preciseness of coding, as well as a benefit.

Answer 6

1. Multiple behaviors to the same function based on the parameters.

2. Your function may want to work with some optional details. For example, the following example wants to add a member to the Members object, with whatever detail the user knows. Here age is the minimum detail to create a member, age and memberOf are optional. [Note: definition of functions are not provided in the code snippet.]

   public class Members
   {
       public System.Collections.Generic.List<Member> TeamMembers;
   
   
   public AddMember(Member m) {}
   public AddMember(string name) {}
   public AddMember(string name, int age) {}
   public AddMember(string name, int age, string[] memberOf) {}
   
   
   public class Member
   {
       public string Name { get; set; }
       public int Age { get; set; }
       public string[] MemberOf { get; set; }
   }
   
   
   }
   

3. You may want your method to be suitable for multiple type of objects. ex. Console.WriteLine() method is capable of writing empty line, bool, int, string, char[], float etc. on the console. This was made possible because of function overloading.

Answer 7

You might want to do similar things in code with different parameters. If you had to give every function a different name, code readability would be very bad.

Answer 8

ad-hoc polymorphism is good stuff !!

Answer 9

Overloading is a form of polymorphism. It allows the programmer to write functions to do conceptually the same thing on different types of data without changing the name. (It also allows the programmer to write functions to do conceptually different things depending on parameters, but that's a Real Bad Idea.)

This allows consistency in notation, which is good both for reading and for writing code. I/O is a very common use. In most languages in common use, there's a function or operator that will output whatever you like, such as printf() and kin in C, operator<<() in C++, PRINT in the old BASICS I used to use, whatever. Languages that require functions like printint(), printstring(), printfloat(), and the like have never caught on.

It works very well with C++ templates and any other construct where you don't necessarily know what the variable type is at the time of writing the code.