Header and source file organization - Time & Space Complexity

Time Complexity: Header and source file organization

O(n)

Understanding Time Complexity

When organizing code into header and source files, it's important to understand how this affects the program's execution steps.

We want to see how the program's running time changes as the size of the input or code grows.

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

// header.h
#ifndef HEADER_H
#define HEADER_H

void printNumbers(int n);

#endif

// source.c
#include "header.h"
#include <stdio.h>

void printNumbers(int n) {
    for (int i = 1; i <= n; i++) {
        printf("%d\n", i);
    }
}

int main() {
    printNumbers(5);
    return 0;
}

This code separates the function declaration in a header file and the function definition in a source file. The function prints numbers from 1 to n.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: The for-loop inside printNumbers that prints numbers.
• How many times: It runs exactly n times, once for each number from 1 to n.

How Execution Grows With Input

As n grows, the number of print operations grows in a straight line.

Input Size (n)	Approx. Operations
10	10 print calls
100	100 print calls
1000	1000 print calls

Pattern observation: The work increases evenly as n increases. Double the input, double the work.

Final Time Complexity

Time Complexity: O(n)

This means the program takes longer in direct proportion to the input size n.

Common Mistake

[X] Wrong: "Splitting code into header and source files makes the program run faster."

[OK] Correct: Organizing code this way helps keep code clean and manageable, but it does not change how many steps the program takes when running.

Interview Connect

Understanding how code organization relates to program speed shows you think about both writing clean code and how it runs, a useful skill in real projects.

Self-Check

"What if the function printed numbers twice inside the loop? How would the time complexity change?"

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