Splitting code into multiple files - Step-by-Step Execution

Concept Flow - Splitting code into multiple files

Start: main.c

↓

Include header.h

↓

Call function from utils.c

↓

Link all files

↓

Run program

↓

Output result

The main file includes a header to use functions from another file. The compiler links all files to create the final program.

Execution Sample

C

#include "utils.h"

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

This main file calls the add function defined in another file.

Execution Table

Step	File	Action	Details	Output/Result
1	main.c	Include	Includes utils.h to use add()	No output
2	main.c	Call function	Calls add(3, 4)	No output
3	utils.c	Execute function	add returns 7	Returns 7
4	main.c	Store result	result = 7	No output
5	main.c	Return from main	Returns 7 to OS	Program ends with code 7

💡 Program ends after main returns the result from add function.

Variable Tracker

Variable	Start	After add(3,4)	Final
result	undefined	7	7

Key Moments - 3 Insights

Why do we include a header file instead of the .c file?

We include the header file (utils.h) to tell the compiler about the function's existence and signature. The actual code is in utils.c, which is linked later. See execution_table step 1 and 3.

How does the program know where the add function is?

The compiler uses the header file to check the function call, and the linker connects main.c and utils.c so the function code is found. See execution_table steps 1, 3, and 4.

What happens if we forget to link utils.c?

The linker will give an error because it can't find the add function's code. The program won't compile successfully. This is why linking all files is important (concept_flow step 4).

Visual Quiz - 3 Questions

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

A 3

B 7

C undefined

D 4

💡 Hint

Check variable_tracker after add(3,4) and execution_table step 3.

At which step does the program return the final value to the operating system?

A Step 5

B Step 2

C Step 1

D Step 3

💡 Hint

Look at execution_table step 5 where main returns.

If we remove the include of utils.h in main.c, what will happen?

A The program will compile and run fine.

B The linker will fail to find add function.

C The compiler will warn or error about missing function declaration.

D The program will return 0 instead of 7.

💡 Hint

Refer to key_moments about including header files and compiler checks.

Concept Snapshot

Splitting code into multiple files:
- Put function declarations in header (.h) files.
- Put function definitions in source (.c) files.
- Include headers in files that use those functions.
- Compile all .c files and link them together.
- This keeps code organized and reusable.

Full Transcript

This example shows how to split C code into multiple files. The main.c file includes utils.h to use the add function. The add function is defined in utils.c. When compiling, both files are linked so the program knows where to find add. The variable 'result' stores the return value of add(3,4), which is 7. The program ends by returning this value. Including the header file lets the compiler check the function call. Forgetting to link utils.c causes errors. This method helps organize code by separating declarations and definitions.

Practice

1. What is the main reason to split C code into multiple files?

easy

A. To reduce the number of variables

B. To make the program run faster

C. To organize code and make it reusable

D. To avoid using header files

Solution

1. Step 1: Understand code organization

   Splitting code into multiple files helps keep related code parts separate and easier to manage.

2. Step 2: Recognize code reuse benefit

   It also allows reusing code in different programs without rewriting it.

3. Final Answer:

   To organize code and make it reusable -> Option C

4. Quick Check:

   Splitting code = Organize and reuse [OK]

Hint: Think about code clarity and reuse benefits [OK]

Common Mistakes:

• Assuming splitting files makes code run faster
• Thinking header files are not needed
• Believing it reduces variables automatically

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

easy

A. #include utils.h

B. #include

C. include "utils.h"

D. #include "utils.h"

Solution

1. Step 1: Understand header file inclusion syntax

   To include your own header files, use double quotes around the filename.

2. Step 2: Differentiate system and user headers

   Angle brackets are for system headers, double quotes for user headers like utils.h.

3. Final Answer:

   #include "utils.h" -> Option D

4. Quick Check:

   User header files use "filename" [OK]

Hint: Use quotes for your headers, angle brackets for system [OK]

Common Mistakes:

• Using angle brackets for user headers
• Omitting # in include directive
• Not using quotes or brackets around filename

3. Given two files:

// file1.c
#include 
void greet();
int main() {
    greet();
    return 0;
}

// file2.c
#include 
void greet() {
    printf("Hello from file2!\n");
}

What is the output when compiled and run together?

medium

A. Hello from file2!

B. Compilation error: greet not declared

C. No output

D. Runtime error

Solution

1. Step 1: Check function declaration and definition

   file1.c declares greet() and calls it; file2.c defines greet() printing the message.

2. Step 2: Understand linking multiple files

   Compiling both files together links greet() correctly, so the program prints the message.

3. Final Answer:

   Hello from file2! -> Option A

4. Quick Check:

   Function declared and defined across files prints message [OK]

Hint: Declare before use, define in another file, link both [OK]

Common Mistakes:

• Forgetting to compile both files together
• Missing function declaration in file1.c
• Expecting compilation error due to separate files

4. You have two files:

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

// helper.c
#include 
void print_message() {
    printf("Hi!\n");
}

// helper.h
void print_message();

Compiling with gcc main.c gives an error: undefined reference to 'print_message'. What is the likely cause?

medium

A. Missing semicolon in helper.h

B. helper.c was not compiled or linked properly

C. print_message() is not declared in main.c

D. main.c does not include stdio.h

Solution

1. Step 1: Understand the error message

   "undefined reference" means the linker can't find the function definition.

2. Step 2: Check compilation command

   If helper.c is not compiled or linked, the function print_message() is missing at link time.

3. Final Answer:

   helper.c was not compiled or linked properly -> Option B

4. Quick Check:

   Linker error = missing compiled file [OK]

Hint: Always compile and link all source files together [OK]

Common Mistakes:

• Not compiling helper.c with main.c
• Ignoring linker errors thinking it's a syntax error
• Assuming declaration alone is enough

5. You want to split a program into main.c and math_ops.c. math_ops.c defines int add(int a, int b). How should you organize files and compile to use add in main.c correctly?

hard

A. Declare add in math_ops.h, include it in main.c, compile with gcc main.c math_ops.c

B. Define add in main.c and call it from math_ops.c, compile separately

C. Include math_ops.c directly in main.c with #include, compile main.c only

D. Declare add in main.c only, compile math_ops.c separately

Solution

1. Step 1: Create a header file math_ops.h

   Declare the function prototype int add(int a, int b); in math_ops.h.

2. Step 2: Include math_ops.h in main.c and compile both files

   Include math_ops.h in main.c to use add(), then compile with gcc main.c math_ops.c to link both.

3. Final Answer:

   Declare add in math_ops.h, include it in main.c, compile with gcc main.c math_ops.c -> Option A

4. Quick Check:

   Header declares, source defines, compile both [OK]

Hint: Use header for declarations, compile all sources together [OK]

Common Mistakes:

• Including .c files instead of headers
• Not declaring functions before use
• Compiling only one source file