In some programming dialects, work over-burdening or technique over-burdening is the capacity to make various elements of a similar name with various usage. Calls to an over-burden capacity will run a particular usage of that work fitting to the setting of the call, permitting one capacity call to perform distinctive errands relying upon setting.
For instance, doTask() and doTask(object O) are over-burden capacities. To call the last mentioned, an article must be passed as a parameter, though the previous does not require a parameter, and is called with an unfilled parameter field. A typical blunder is dole out a default an incentive to the article in the second capacity, which would result in a vague call mistake, as the compiler wouldn't know which of the two strategies to utilize.
For instance, doTask() and doTask(object O) are over-burden capacities. To call the last mentioned, an article must be passed as a parameter, though the previous does not require a parameter, and is called with an unfilled parameter field. A typical blunder is dole out a default an incentive to the article in the second capacity, which would result in a vague call mistake, as the compiler wouldn't know which of the two strategies to utilize.
Comment