Balanced Parentheses Problem Using Stack in DSA C - Time & Space Complexity

Time Complexity: Balanced Parentheses Problem Using Stack

O(n)

Understanding Time Complexity

We want to know how the time to check balanced parentheses grows as the input string gets longer.

Specifically, how many steps does it take to verify if parentheses are balanced?

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

bool isBalanced(char* expr) {
    Stack s = createStack();
    for (int i = 0; expr[i] != '\0'; i++) {
        if (expr[i] == '(') {
            push(&s, '(');
        } else if (expr[i] == ')') {
            if (isEmpty(&s)) return false;
            pop(&s);
        }
    }
    return isEmpty(&s);
}
    

This code checks if parentheses in a string are balanced using a stack.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: Loop through each character of the input string once.
• How many times: Exactly once for each character (n times for input length n).

How Execution Grows With Input

Each character is checked once, so the steps grow directly with input size.

Input Size (n)	Approx. Operations
10	About 10 checks and stack operations
100	About 100 checks and stack operations
1000	About 1000 checks and stack operations

Pattern observation: Operations increase linearly as input size increases.

Final Time Complexity

Time Complexity: O(n)

This means the time to check balanced parentheses grows in direct proportion to the input length.

Common Mistake

[X] Wrong: "The time complexity is higher because of stack operations inside the loop."

[OK] Correct: Each stack operation (push/pop) takes constant time, so they do not add extra loops or multiply the steps.

Interview Connect

Understanding this linear time check helps you handle many real-world problems involving matching pairs efficiently.

Self-Check

"What if we also had to check for multiple types of brackets like {}, [], and ()? How would the time complexity change?"

Practice

1. What is the main purpose of using a stack in the Balanced Parentheses problem?

easy

A. To keep track of opening parentheses and match them with closing ones

B. To count the total number of parentheses in the expression

C. To reverse the order of parentheses in the expression

D. To store only the closing parentheses encountered

Solution

1. Step 1: Understand the role of stack in parentheses matching

   A stack helps to remember the last opening parenthesis to match it with the next closing one.

2. Step 2: Identify why other options are incorrect

   Counting or reversing parentheses does not solve matching pairs; storing only closing parentheses misses the matching logic.

3. Final Answer:

   To keep track of opening parentheses and match them with closing ones -> Option A

4. Quick Check:

   Stack tracks openings for matching = B [OK]

Hint: Stack remembers last opening bracket for matching [OK]

Common Mistakes:

• Thinking stack counts parentheses instead of matching
• Using stack to store only closing parentheses
• Ignoring order of parentheses

2. Which of the following code snippets correctly pushes an opening parenthesis '(' onto a stack named stack in C?

easy

A. push(stack, '(');

B. stack.push('(');

C. stack->push('(');

D. push('(', stack);

Solution

1. Step 1: Recognize typical C stack push syntax

   In C, stack operations are usually functions like push(stack, element).

2. Step 2: Analyze each option

   push(stack, '('); matches the common C function call syntax. Options B and C use dot or arrow notation typical in C++ or OOP, not plain C. push('(', stack); has arguments reversed.

3. Final Answer:

   push(stack, '('); -> Option A

4. Quick Check:

   C stack push syntax = A [OK]

Hint: In C, use push(stack, element) function call [OK]

Common Mistakes:

• Using C++ style stack.push() in C
• Reversing arguments in push function
• Using arrow operator on non-pointer stack

3. What will be the output of the following C code snippet that checks balanced parentheses?

char expr[] = "({[]})";
int result = isBalanced(expr);
printf("%d", result);

Assume isBalanced returns 1 if balanced, 0 otherwise.

medium

A. Runtime error

B. 0

C. Compilation error

D. 1

Solution

1. Step 1: Analyze the expression "({[]})"

   The expression has matching pairs: '(' with ')', '{' with '}', '[' with ']'. All are properly nested.

2. Step 2: Understand isBalanced function behavior

   Since the expression is balanced, isBalanced returns 1, so printf prints 1.

3. Final Answer:

   1 -> Option D

4. Quick Check:

   Balanced expression returns 1 = A [OK]

Hint: Balanced nested pairs return 1 from isBalanced [OK]

Common Mistakes:

• Assuming only () pairs are valid
• Confusing balanced with equal count
• Expecting 0 for nested but balanced

4. Identify the bug in this C function snippet for checking balanced parentheses:

int isBalanced(char* expr) {
  Stack s;
  for (int i = 0; expr[i] != '\0'; i++) {
    if (expr[i] == '(') push(&s, '(');
    else if (expr[i] == ')') {
      if (isEmpty(&s)) return 0;
      pop(&s);
    }
  }
  return isEmpty(&s);
}

medium

A. Return statement should be inside the loop

B. Stack s is not initialized before use

C. pop() is called without checking if stack is empty

D. The function does not check for other types of brackets

Solution

1. Step 1: Check stack initialization

   The stack variable 's' is declared but not initialized, so push/pop operations may fail.

2. Step 2: Verify other parts

   Other options are less critical: checking only () is a limitation but not a bug; pop is called after empty check; return outside loop is correct.

3. Final Answer:

   Stack s is not initialized before use -> Option B

4. Quick Check:

   Uninitialized stack causes errors = D [OK]

Hint: Always initialize stack before push/pop [OK]

Common Mistakes:

• Ignoring stack initialization
• Assuming pop safe without empty check
• Thinking return must be inside loop

5. Given the expression "[{()}](({}))", which of the following modifications to the isBalanced function will correctly handle all types of brackets: (), {}, and []?

hard

A. Ignore brackets inside quotes and only check outer brackets

B. Count total opening and closing brackets separately and compare counts

C. Push opening brackets and check matching closing brackets by popping and comparing types

D. Replace all brackets with parentheses before checking

Solution

1. Step 1: Understand bracket matching logic

   To handle multiple bracket types, push opening brackets and on closing bracket, pop and check if types match.

2. Step 2: Evaluate other options

   Counting brackets ignores order; ignoring brackets inside quotes is unrelated; replacing brackets loses type info.

3. Final Answer:

   Push opening brackets and check matching closing brackets by popping and comparing types -> Option C

4. Quick Check:

   Match types by push/pop for all brackets = C [OK]

Hint: Match each closing bracket with last opening of same type [OK]

Common Mistakes:

• Counting brackets without order check
• Ignoring bracket types
• Replacing brackets loses matching info