Why storage classes are needed - Performance Analysis

Time Complexity: Why storage classes are needed

O(n)

Understanding Time Complexity

We want to see how the use of storage classes affects the time it takes for a program to run.

Specifically, we ask: does choosing different storage classes change how fast the program runs as input grows?

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

#include <stdio.h>

void countUp(int n) {
    static int counter = 0;
    for (int i = 0; i < n; i++) {
        counter++;
    }
    printf("Counter: %d\n", counter);
}

int main() {
    countUp(5);
    countUp(3);
    return 0;
}
    

This code uses a static storage class variable inside a function to keep track of a count across calls.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: The for-loop that runs from 0 to n-1.
• How many times: Exactly n times each call to countUp.

How Execution Grows With Input

As n grows, the number of loop steps grows directly with n.

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

Pattern observation: The work grows in a straight line as n increases.

Final Time Complexity

Time Complexity: O(n)

This means the time to run grows directly with the size of the input n.

Common Mistake

[X] Wrong: "Using static variables makes the loop run faster because the variable keeps its value."

[OK] Correct: The static variable only keeps its value between calls; it does not reduce the number of loop steps. The loop still runs n times each call.

Interview Connect

Understanding how storage classes affect program behavior helps you explain how variables live and change over time, which is a key skill in writing efficient and clear code.

Self-Check

"What if we changed the static variable to a regular local variable? How would the time complexity change?"

Practice

1. Why are storage classes needed in C programming?

easy

A. To allocate memory dynamically

B. To define the data type of variables

C. To perform arithmetic operations

D. To control the lifetime and visibility of variables

Solution

1. Step 1: Understand the role of storage classes

   Storage classes in C define how long a variable exists and where it can be accessed.

2. Step 2: Differentiate from other concepts

   Data types define variable type, arithmetic operations perform calculations, and dynamic memory allocation is separate from storage classes.

3. Final Answer:

   To control the lifetime and visibility of variables -> Option D

4. Quick Check:

   Storage classes = control lifetime and visibility [OK]

Hint: Storage classes manage variable life and access [OK]

Common Mistakes:

• Confusing storage classes with data types
• Thinking storage classes allocate memory dynamically
• Assuming storage classes perform operations

2. Which of the following is the correct syntax to declare a variable with static storage class in C?

easy

A. count static int;

B. static int count;

C. int static count;

D. int count static;

Solution

1. Step 1: Recall correct order of storage class declaration

   In C, the storage class specifier comes before the data type.

2. Step 2: Verify each option's syntax

   static int count; uses 'static int count;' which is correct. Other options place 'static' incorrectly.

3. Final Answer:

   static int count; -> Option B

4. Quick Check:

   Storage class before type = correct syntax [OK]

Hint: Storage class keyword always precedes data type [OK]

Common Mistakes:

• Placing storage class after variable name
• Mixing order of keywords
• Using invalid syntax like 'count static int;'

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

void func() {
    static int count = 0;
    count++;
    printf("%d ", count);
}

int main() {
    for(int i = 0; i < 3; i++) {
        func();
    }
    return 0;
}

medium

A. 1 2 3

B. 3 3 3

C. 0 1 2

D. 1 1 1

Solution

1. Step 1: Understand static variable behavior inside function

   The static variable 'count' retains its value between function calls and initializes only once.

2. Step 2: Trace the loop and function calls

   Each call to func() increments count: first call prints 1, second 2, third 3.

3. Final Answer:

   1 2 3 -> Option A

4. Quick Check:

   Static variable increments across calls = 1 2 3 [OK]

Hint: Static variables keep value between calls [OK]

Common Mistakes:

• Assuming static variable resets each call
• Confusing static with automatic variables
• Ignoring initialization behavior

4. Identify the error in the following C code related to storage class usage:

extern int x = 10;

int main() {
    printf("%d", x);
    return 0;
}

medium

A. Missing 'static' keyword before 'int x'

B. 'x' should be declared inside main function

C. 'extern' variable cannot be initialized

D. No error, code runs fine

Solution

1. Step 1: Understand 'extern' storage class rules

   An 'extern' variable declaration cannot have an initializer; it only declares the variable.

2. Step 2: Analyze the code

   Here, 'extern int x = 10;' tries to initialize 'x' which is invalid and causes a compilation error.

3. Final Answer:

   'extern' variable cannot be initialized -> Option C

4. Quick Check:

   Extern declarations must not initialize variables [OK]

Hint: Extern declarations cannot initialize variables [OK]

Common Mistakes:

• Initializing extern variables
• Assuming extern means static
• Declaring variables only inside main

5. You want a variable in C that keeps its value between function calls but is only accessible inside that function. Which storage class should you use?

hard

A. static

B. extern

C. auto

D. register

Solution

1. Step 1: Understand variable lifetime and scope requirements

   The variable must keep its value between calls (persistent lifetime) and be local to the function (limited scope).

2. Step 2: Match storage classes to requirements

   'static' inside a function keeps the variable value between calls and restricts scope to that function.

3. Final Answer:

   static -> Option A

4. Quick Check:

   Static inside function = persistent and local [OK]

Hint: Use static for persistent local variables [OK]

Common Mistakes:

• Using auto which resets each call
• Using extern which is global
• Using register which is for CPU registers