Header and source file organization - Step-by-Step Execution

Concept Flow - Header and source file organization

Write declarations in header (.h)

↓

Include header in source (.c)

↓

Write function definitions in source (.c)

↓

Compile source files

↓

Link object files

↓

Run program

This flow shows how declarations go in header files, definitions in source files, then compilation and linking to run the program.

Execution Sample

C

#include "math_utils.h"

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

This code includes a header file declaring 'add', then calls 'add' defined in a source file.

Execution Table

Step	Action	File Affected	Details	Result
1	Write function declaration	math_utils.h	int add(int a, int b);	Declaration available for other files
2	Write function definition	math_utils.c	int add(int a, int b) { return a + b; }	Function implemented
3	Include header	main.c	#include "math_utils.h"	Declaration visible in main.c
4	Call function	main.c	int result = add(3, 4);	Calls add defined in math_utils.c
5	Compile source files	math_utils.c, main.c	gcc -c math_utils.c main.c	Object files created
6	Link object files	math_utils.o, main.o	gcc math_utils.o main.o -o program	Executable created
7	Run program	program	./program	Program runs, add returns 7

💡 Program runs successfully using organized header and source files

Variable Tracker

Variable	Start	After main call	Final
result	undefined	7	7

Key Moments - 3 Insights

Why do we put function declarations in header files instead of source files?

Declarations in header files let multiple source files know about the functions without repeating code. See step 1 and 3 in execution_table.

What happens if we forget to include the header file in the source file that calls the function?

The compiler may not know the function signature, causing errors or warnings. Step 3 shows including the header to avoid this.

Why do we compile source files separately before linking?

Compiling separately creates object files for each source, then linking combines them. This modular approach is shown in steps 5 and 6.

Visual Quiz - 3 Questions

Look at the execution_table, at which step is the function 'add' actually implemented?

A Step 2

B Step 1

C Step 3

D Step 4

💡 Hint

Check the 'Action' and 'Details' columns in step 2 for function definition.

According to variable_tracker, what is the value of 'result' after calling add(3, 4)?

A 3

B 4

C 7

D undefined

💡 Hint

Look at 'After main call' column for 'result' in variable_tracker.

If we skip step 3 (including the header in main.c), what is the likely outcome?

A Program runs normally

B Compiler error or warning about 'add'

C Linker error only

D Runtime error only

💡 Hint

Step 3 shows including header to declare 'add' before calling it.

Concept Snapshot

Header files (.h) contain function declarations.
Source files (.c) contain function definitions.
Include headers in source files to share declarations.
Compile source files separately, then link.
This organization helps modular and error-free code.

Full Transcript

In C programming, we organize code by putting function declarations in header files and function definitions in source files. The header file math_utils.h declares the function add. The source file math_utils.c defines add. The main.c file includes math_utils.h to know about add before calling it. We compile math_utils.c and main.c separately into object files, then link them to create the executable. This organization helps keep code modular and avoids errors. The variable 'result' stores the sum returned by add. Including headers ensures the compiler knows function signatures. Skipping header inclusion causes compiler errors. This step-by-step flow shows how header and source files work together to build a C program.