Function prototypes - Step-by-Step Execution

Concept Flow - Function prototypes

Write function prototype

↓

Use function in main

↓

Compiler checks prototype

↓

Call function with correct args?

No→Error

Yes↓

Function definition later

↓

Program compiles and runs

The compiler first sees the function prototype, then checks calls against it before the function is defined.

Execution Sample

C

int add(int a, int b);  

int main() {
    int result = add(3, 4);
    return 0;
}

int add(int a, int b) {
    return a + b;
}

This code declares a function prototype for add, calls it in main, then defines it later.

Execution Table

Step	Action	Evaluation	Result
1	Read prototype: int add(int a, int b);	Compiler stores signature	Allows calls before definition
2	Enter main function	Ready to execute main	Variables initialized
3	Call add(3, 4)	Check prototype matches call	Match found, call allowed
4	Jump to add function definition	Execute add with a=3, b=4	Return 7
5	Store return value in result	result = 7	Ready for next statement
6	main returns 0	Program ends	Successful execution

💡 Program ends after main returns 0

Variable Tracker

Variable	Start	After add call	Final
a	N/A	3	N/A (local to add)
b	N/A	4	N/A (local to add)
result	undefined	7	7

Key Moments - 3 Insights

Why do we need a function prototype before calling the function?

The prototype tells the compiler the function's name, return type, and parameters so it can check calls before seeing the full function. See step 1 and 3 in the execution_table.

What happens if the function call does not match the prototype?

The compiler gives an error because the call does not match the expected parameters. This is checked at step 3 in the execution_table.

Can the function be defined after main if we have a prototype?

Yes, the prototype allows calling the function before its full definition, as shown by steps 1 and 4.

Visual Quiz - 3 Questions

Look at the execution_table, what is the value of 'result' after step 5?

A 7

B 3

C undefined

D 0

💡 Hint

Check the 'result' variable in variable_tracker after the add call.

At which step does the compiler check if the function call matches the prototype?

A Step 1

B Step 3

C Step 4

D Step 6

💡 Hint

Look at the 'Action' and 'Evaluation' columns in execution_table.

If we remove the prototype line, what will happen when compiling?

A Program compiles and runs normally

B Function runs but returns wrong value

C Compiler error at function call

D Program runs but main returns 1

💡 Hint

Recall why the prototype is needed from key_moments and execution_table step 3.

Concept Snapshot

Function prototypes declare a function's name, return type, and parameters before its use.
They let the compiler check calls before the full function is defined.
Syntax: return_type function_name(parameter_types);
Without prototypes, calls before definitions cause errors.
Prototypes improve code organization and compilation safety.

Full Transcript

In C programming, a function prototype is a declaration that tells the compiler about a function's name, return type, and parameters before the function is actually defined. This allows you to call the function in your code before writing its full definition. The compiler uses the prototype to check that calls to the function have the correct number and types of arguments. If the call does not match the prototype, the compiler will give an error. This helps catch mistakes early. The prototype is usually placed at the top of the file or in a header file. When the program runs, the function is called as usual, and the definition is used to execute the function's code. This way, prototypes help organize code and ensure correctness during compilation.