C++ Programming - OOPS Concepts - Discussion

Can you clear me why All function calls are resolved at compile-time in Procedure Oriented Programming?

Answer is right.

C supports only "Early Binding" in which all the functions related to their function calls are resolved at compile time.

C++ Supports both "Early Binding" and "Late Binding". Late Binding is the process of resolving functions related to function calls during Run time.

In C++ virtual calling mechanisms are resolved at run-time.

Hence, Option (c) only 1 correct.

Because when you create an object of a class you indirectly call the constructor function of that class. So, in OOPS, all functions are not resolved at compile time only.

While creating objects we are indirectly calling constructors. So all functions cannot be be resolved by compiler alone.

What about calling a function in C by pointer to function? Isn't that kind of dynamic?

Going through above discussion I feel that the answer is wrong.

Example:

struct Emp
{
char name[10+1];
int age;
};
int main()
{
struct Emp e;
int *ptr = malloc(sizeof(e));
}

Malloc get resolved at run time and not compile time. Similarly calloc, realloc.

In C there is no concept of compile time and runtime, so all function calls are resolved at compile time, but in OOPs, there are two different concepts of compile time and runtime.

Some types of functions are resolved at compile time, and some are at runtime, but this question mentioned that all functions are resolved at compile time, which is absolutely wrong.