Splitting code into multiple files - Cheat Sheet & Quick Revision

Recall & Review

beginner

Why do we split C code into multiple files?

Splitting code into multiple files helps organize the program better, makes it easier to manage, and allows multiple people to work on different parts at the same time.

beginner

What is a header file (.h) used for in C?

A header file contains declarations like function prototypes and variable declarations that other files can use to know how to interact with the code without seeing the full details.

beginner

How do you include one file in another in C?

You use the #include directive with the file name in quotes for your own files, like #include "myfile.h".

beginner

What command compiles multiple C files together?

You can compile multiple files by listing them all in the compiler command, for example: gcc main.c utils.c -o program

beginner

What is the role of a .c file compared to a .h file?

A .c file contains the actual code (function definitions), while a .h file contains declarations (function prototypes and constants) to share with other files.

Which file type usually contains function declarations in C?

A .txt file

B .c file

C .exe file

D .h file

Header files (.h) contain declarations like function prototypes.

How do you tell the compiler to compile multiple C files together?

A List all .c files in the gcc command

B Use #include for .c files

C Put all code in one file

D Use a .h file only

You list all source files in the compiler command, like gcc main.c utils.c -o program.

What does #include "file.h" do in a C program?

A Copies the content of file.h into the current file

B Runs file.h as a program

C Compiles file.h separately

D Deletes file.h

#include literally inserts the content of the header file into the current file before compiling.

Why should you use header files in multi-file C programs?

A To store executable code

B To share declarations and avoid repeating code

C To make the program run faster

D To hide code from the compiler

Header files share declarations so multiple files know about functions and variables.

What happens if you forget to include a header file with function declarations?

A The program ignores the missing functions

B The program runs faster

C The compiler may give errors or warnings about missing functions

D The program compiles without any issues

Without declarations, the compiler doesn't know about the functions and will report errors.

Explain how to split a simple C program into two files: one for main and one for helper functions.

Think about separating code and sharing declarations.

Describe the difference between a .c file and a .h file and why both are important.

Focus on code vs declarations and sharing.

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