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.

Practice

1. What is the main purpose of a header file in C programming?

easy

A. To execute the program's main logic

B. To declare functions and variables for sharing between source files

C. To contain the actual implementation code of functions

D. To store compiled machine code

Solution

1. Step 1: Understand header file role

   Header files declare functions and variables so multiple source files can use them.

2. Step 2: Differentiate from source files

   Source files contain the actual code, not declarations.

3. Final Answer:

   To declare functions and variables for sharing between source files -> Option B

4. Quick Check:

   Header files declare, source files define [OK]

Hint: Headers declare, sources define code [OK]

Common Mistakes:

• Confusing header files as containing code
• Thinking header files execute code
• Mixing compiled code with header files

2. Which of the following is the correct way to include a header file named math_utils.h in a C source file?

easy

A. #include

B. import math_utils.h

C. #include "math_utils.h"

D. include math_utils.h

Solution

1. Step 1: Identify correct include syntax for user headers

   User-defined headers use double quotes: #include "filename".

2. Step 2: Differentiate from system headers

   System headers use angle brackets, but user headers like math_utils.h use quotes.

3. Final Answer:

   #include "math_utils.h" -> Option C

4. Quick Check:

   User headers use quotes [OK]

Hint: Use quotes for your own headers [OK]

Common Mistakes:

• Using angle brackets for user headers
• Using import instead of #include
• Omitting # in include directive

3. Given these files:

// math_utils.h
int add(int a, int b);

// math_utils.c
#include "math_utils.h"
int add(int a, int b) { return a + b; }

// main.c
#include 
#include "math_utils.h"
int main() {
    printf("%d\n", add(3, 4));
    return 0;
}

What will be the output when running the compiled program?

medium

A. 7

B. 34

C. 0

D. Compilation error

Solution

1. Step 1: Understand function declaration and definition

   math_utils.h declares add(), math_utils.c defines it to return sum of a and b.

2. Step 2: Trace main function call

   main.c calls add(3, 4), which returns 7, then prints it.

3. Final Answer:

   7 -> Option A

4. Quick Check:

   3 + 4 = 7 [OK]

Hint: Function returns sum, so output is 7 [OK]

Common Mistakes:

• Thinking add concatenates numbers
• Expecting compilation error due to missing code
• Confusing printf format

4. Consider this code snippet:

// utils.h
void print_message();

// utils.c
#include "utils.h"
void print_message() {
    printf("Hello!\n");
}

// main.c
#include "utils.h"
int main() {
    print_message();
    return 0;
}

When compiling, an error says implicit declaration of function 'printf'. What is the fix?

medium

A. Add #include <stdio.h> in utils.c

B. Add #include <stdio.h> in utils.h

C. Add #include <stdio.h> in main.c

D. Remove print_message function

Solution

1. Step 1: Identify cause of error

   printf is declared in stdio.h; utils.c uses printf but lacks this include.

2. Step 2: Fix by including stdio.h in utils.c

   Adding #include <stdio.h> in utils.c provides printf declaration, fixing error.

3. Final Answer:

   Add #include <stdio.h> in utils.c -> Option A

4. Quick Check:

   Include stdio.h where printf is used [OK]

Hint: Include stdio.h in files using printf [OK]

Common Mistakes:

• Including stdio.h only in header file
• Including stdio.h only in main.c
• Ignoring missing printf declaration

5. You want to organize a C project with multiple source files sharing utility functions. Which is the best practice for header and source file organization?

hard

A. Put function definitions in header files and include them everywhere

B. Put function declarations and definitions together in each source file without headers

C. Put all code in a single source file without headers

D. Put all function declarations in one header file and definitions in one source file, then include the header where needed

Solution

1. Step 1: Understand modular organization

   Separating declarations in headers and definitions in source files allows sharing and reuse.

2. Step 2: Avoid putting definitions in headers

   Definitions in headers cause multiple definition errors when included in many files.

3. Final Answer:

   Put all function declarations in one header file and definitions in one source file, then include the header where needed -> Option D

4. Quick Check:

   Headers declare, sources define, include headers [OK]

Hint: Declare in headers, define in sources, include headers [OK]

Common Mistakes:

• Defining functions in headers causing linker errors
• Not using headers causing duplicate declarations
• Putting all code in one file reducing modularity