Question

Can someone explain me "Function Overriding and polymorphism in C++" Give me some examples.

Answer 1

Didn't I answer this yesterday? Did you not understand my explanation?

double area(double radius)
{
return 3.14*radius*radius;
}
double area(double width, double height)
{
return width * height;
}

This is an overloaded function called area. Calling area in main will call either the first version or the second depending on how many argument you pass to it:

int main()
{
double x, y, circle, rectangle;
circle = area(x); //This will call the first declaration of area
rectangle = area(x, y); //This will call the second declaration of area
return 0;
}

Is this clear enough for you, or are you confused?

Answer 2

I have tried to understand this way.


#include<iostream>
using namespace std;

void printNumber(int x)
{
cout<<"I am printing an integer<<x<<endl;
}

void printNumber(int x)
{
cout<<"I am printing a float<<x<<endl;
}

int main()
{
int a=54;
float b=3.154;

printNumber(a);
printNumber(b);

}

Answer 3

that won;t work because both versions of printNumber that you wrote take the same number and type of argument one int
the key to function overloading is to make two versions of a function that take *different numbers and/or types* of arguments
i.e.
printNumber(char c)
printNumber(int x)
printNumber(int x, char c)

all these are overloads, but you *cannot* make another such as

printNumber(int n)

because this takes the same number of arguments, just one int, and we already have a version of printNumber that does that

Answer 4

#include<iostream>
using namespace std;

void printNumber(int x)
{
cout<<"I am printing an integer<<x<<endl;
}

void printNumber(float x) \\i made a mistake here. i corrected it
{
cout<<"I am printing a float<<x<<endl;
}

int main()
{
int a=54;
float b=3.154;

printNumber(a);
printNumber(b);

}

Answer 5

You have the right idea.this would be a valid overload, but I'd avoid trying to distinguish an overridden function by a difference like int, float, double, etc, since a float may accidentally become an int during a program's execution, or a float may be promoted to a double, causing confusing behavior for the programmer. It's bad practice, but technically viable.