Header files and include directive - Step-by-Step Execution

Concept Flow - Header files and include directive

Start Program

↓

Encounter #include directive

↓

Preprocessor copies header file content

↓

Compiler compiles combined code

↓

Program uses declarations from header

↓

Program runs with included functions/definitions

↓

End

The program starts, sees the #include directive, copies the header file content into the source, then compiles and runs using those declarations.

Execution Sample

C

#include <stdio.h>

int main() {
    printf("Hello\n");
    return 0;
}

This code includes the standard input-output header to use printf, then prints Hello.

Execution Table

Step	Action	Details	Result
1	Read source file	Find #include <stdio.h>	Prepare to insert stdio.h content
2	Preprocessor action	Copy content of stdio.h into source	Source now has printf declaration
3	Compiler compiles	Compile combined source code	printf function recognized
4	Run main()	Call printf("Hello\n")	Output: Hello
5	Return 0	Program ends successfully	Exit code 0

💡 Program ends after main returns 0

Variable Tracker

Variable	Start	After Step 4	Final
Output	""	"Hello\n"	"Hello\n"

Key Moments - 3 Insights

Why do we use #include <stdio.h> instead of writing printf ourselves?

The execution_table step 2 shows the preprocessor copies stdio.h content, which declares printf. This lets the compiler know about printf without rewriting it.

What happens if we forget to include the header file?

At step 3, the compiler won't recognize printf and will give an error because it lacks the declaration from the header file.

Is the header file code copied every time we compile?

Yes, step 2 shows the preprocessor copies the header content each time before compiling, so the compiler sees the full combined code.

Visual Quiz - 3 Questions

Look at the execution_table, what happens at step 2?

A The compiler throws an error

B The preprocessor copies the header file content into the source code

C The program runs and prints output

D The main function returns 0

💡 Hint

Check the 'Action' and 'Details' columns in step 2 of execution_table

At which step does the program actually print 'Hello'?

A Step 1

B Step 3

C Step 4

D Step 5

💡 Hint

Look at the 'Run main()' action in execution_table

If we remove #include <stdio.h>, what will happen at step 3?

A The compiler will give an error about printf being undeclared

B The compiler will recognize printf anyway

C The program will print Hello without issues

D The preprocessor will add stdio.h automatically

💡 Hint

Refer to key_moments about missing header causing compiler errors

Concept Snapshot

#include directive inserts header file content
Header files declare functions and macros
Preprocessor copies header content before compiling
Allows use of functions like printf
Missing header causes compiler errors
Always include needed headers

Full Transcript

This visual trace shows how the C program uses the #include directive to bring in header files. The program starts and the preprocessor finds #include <stdio.h>. It copies the content of stdio.h into the source code, so the compiler knows about printf. Then the compiler compiles the combined code. When running main, printf prints Hello. The program ends returning 0. Without including stdio.h, the compiler would not recognize printf and give an error. The header file content is copied every time before compiling to provide declarations and macros needed by the program.