What is the use/advantage of function overloading?
相关问题
- how to define constructor for Python's new Nam
- Keeping track of variable instances
- Object.create() bug?
- std::vector of objects / pointers / smart pointers
- Dynamic Casts or Function Overloads?
相关文章
- 接口B继承接口A,但是又不添加新的方法。这样有什么意义吗?
- Generics and calling overloaded method from differ
- Should client-server code be written in one “proje
- Algorithm for maximizing coverage of rectangular a
- NameError: name 'self' is not defined, eve
- Overloading a super class's function
- Is there an existing solution for these particular
- Implementation Strategies for Object Orientation
It is the mechanism of function with same name but perform different task on different instance. We easily remember the names that are commonly used.
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.
IMO, the primary benefit is consistency in the naming of methods / functions which logically perform very similar tasks, and differ slightly in by accepting different parameters. This allows the same method name to be reused across multiple implementations.
e.g. The overloads: (Good)
Are preferable to 'uniquely named' functions: (Worse)
This way the coder writing a client which calls / consumes these functions can operate at a higher level of conceptual thinking ("I need to find a person") and doesn't need to remember / locate a contrived function name.
With static typing, the compiler will be left to match the applicable overload based on the usage parameters. For dynamic typing, this same match up will happen at run time, possibly resulting in failure if no appropriate match is found.
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 likeprintint()
,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.
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.]
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.
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.