Reusability and maintenance - Time & Space Complexity

Time Complexity: Reusability and maintenance

O(n)

Understanding Time Complexity

When we write reusable and maintainable code, we want to know how it affects how long the program takes to run.

We ask: does making code reusable change how the program grows with bigger inputs?

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

#include <stdio.h>

void printArray(int arr[], int size) {
    for (int i = 0; i < size; i++) {
        printf("%d ", arr[i]);
    }
    printf("\n");
}

int main() {
    int data[] = {1, 2, 3, 4, 5};
    printArray(data, 5);
    return 0;
}
    

This code uses a reusable function to print elements of an array.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: The for-loop inside printArray that goes through each array element.
• How many times: It runs once for each element in the array, so size times.

How Execution Grows With Input

As the array gets bigger, the loop runs more times, directly matching the size.

Input Size (n)	Approx. Operations
10	10 loop steps
100	100 loop steps
1000	1000 loop steps

Pattern observation: The number of steps grows evenly as the input size grows.

Final Time Complexity

Time Complexity: O(n)

This means the time to run grows in a straight line with the size of the input.

Common Mistake

[X] Wrong: "Making code reusable always makes it slower or more complex."

[OK] Correct: Reusable code often just wraps the same steps in a function, so the main work still grows the same way with input size.

Interview Connect

Understanding how reusable functions affect time helps you write clean code without worrying about hidden slowdowns.

Self-Check

"What if the reusable function called another function inside a nested loop? How would the time complexity change?"

Practice

1. What is the main benefit of using functions in C for reusability and maintenance?

easy

A. Functions use less memory than variables

B. Functions make the program run faster

C. You can write code once and use it many times

D. Functions prevent all bugs automatically

Solution

1. Step 1: Understand the purpose of functions

   Functions allow you to group code that performs a task so you can reuse it multiple times without rewriting.

2. Step 2: Connect reusability to maintenance

   Using functions reduces repeated code, making it easier to update and maintain.

3. Final Answer:

   You can write code once and use it many times -> Option C

4. Quick Check:

   Functions improve reusability = You can write code once and use it many times [OK]

Hint: Functions let you reuse code easily [OK]

Common Mistakes:

• Thinking functions always make code faster
• Confusing functions with variables
• Believing functions fix all bugs automatically

2. Which of the following is the correct syntax to declare a function named add that takes two integers and returns an integer in C?

easy

A. int add(int a, int b);

B. add int(int a, int b);

C. int add(a, b) int a; int b; { return a + b; }

D. function add(int a, int b) { return a + b; }

Solution

1. Step 1: Identify correct function declaration syntax

   In C, a function declaration specifies the return type, function name, and parameter types inside parentheses.

2. Step 2: Check each option

   int add(int a, int b); matches the correct syntax: int add(int a, int b);. Others have wrong order, keywords, or syntax.

3. Final Answer:

   int add(int a, int b); -> Option A

4. Quick Check:

   Correct C function declaration = int add(int a, int b); [OK]

Hint: Function declarations start with return type and name [OK]

Common Mistakes:

• Using 'function' keyword (not in C)
• Wrong parameter syntax
• Missing return type

3. What will be the output of the following C code?

int square(int x) {
    return x * x;
}

int main() {
    int result = square(4);
    printf("%d", result);
    return 0;
}

medium

A. Compilation error

B. 8

C. 4

D. 16

Solution

1. Step 1: Understand the function behavior

   The function square returns the input multiplied by itself, so square(4) returns 16.

2. Step 2: Check the main function output

   The main function calls square(4), stores 16 in result, and prints it with printf.

3. Final Answer:

   16 -> Option D

4. Quick Check:

   square(4) = 16 [OK]

Hint: Multiply input by itself to find square [OK]

Common Mistakes:

• Confusing multiplication with addition
• Expecting 8 instead of 16
• Thinking code has syntax errors

4. Identify the error in the following C code that tries to reuse a function:

int multiply(int a, int b) {
    return a * b;
}

int main() {
    int result = multiply(5);
    printf("%d", result);
    return 0;
}

medium

A. multiply is called with only one argument instead of two

B. main function should return void

C. printf format specifier is incorrect

D. Function multiply is missing a return statement

Solution

1. Step 1: Check function definition and call

   The function multiply requires two integer arguments, but in main it is called with only one argument.

2. Step 2: Identify the error type

   This mismatch causes a compilation error because the number of arguments does not match the function signature.

3. Final Answer:

   multiply is called with only one argument instead of two -> Option A

4. Quick Check:

   Argument count mismatch = multiply is called with only one argument instead of two [OK]

Hint: Match function call arguments to definition [OK]

Common Mistakes:

• Ignoring argument count mismatch
• Thinking printf format is wrong
• Assuming main must return void

5. You want to write a reusable function in C that calculates the average of an array of integers. Which approach improves reusability and maintenance the most?

hard

A. Write the average calculation code inside main() every time you need it

B. Create a function that takes an integer array and its size, then returns the average

C. Use global variables to store the array and size, then write a function without parameters

D. Copy and paste the average calculation code wherever needed

Solution

1. Step 1: Understand reusability principles

   Reusable code should be modular, accept inputs, and avoid global state to be flexible and maintainable.

2. Step 2: Evaluate each option

   Create a function that takes an integer array and its size, then returns the average creates a function with parameters for array and size, making it reusable for any array. Others either duplicate code or rely on globals, reducing reusability.

3. Final Answer:

   Create a function that takes an integer array and its size, then returns the average -> Option B

4. Quick Check:

   Function with parameters improves reusability = Create a function that takes an integer array and its size, then returns the average [OK]

Hint: Functions with parameters are reusable and maintainable [OK]

Common Mistakes:

• Using global variables reduces flexibility
• Duplicating code increases errors
• Writing code only inside main limits reuse