Why conditionals branch script logic in Bash Scripting - Performance Analysis

Time Complexity: Why conditionals branch script logic

O(n)

Understanding Time Complexity

We want to see how using conditionals affects how long a script takes to run.

Specifically, we ask: does branching with conditionals make the script slower as input grows?

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

#!/bin/bash

for file in "$@"; do
  if [[ -f "$file" ]]; then
    echo "$file is a regular file"
  else
    echo "$file is not a regular file"
  fi
done

This script checks each input argument to see if it is a regular file and prints a message accordingly.

Identify Repeating Operations

• Primary operation: The for-loop that goes through each input file name.
• How many times: Once for each input argument (number of files given).

How Execution Grows With Input

Each file name causes one check and one print. So as the number of files grows, work grows the same way.

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

Pattern observation: The work grows directly with the number of input files.

Final Time Complexity

Time Complexity: O(n)

This means the script takes longer in a straight line as you give it more files to check.

Common Mistake

[X] Wrong: "Adding an if-else makes the script run much slower for each file."

[OK] Correct: The if-else just chooses one path per file; it does not repeat work multiple times. So it adds a tiny fixed cost per file, not extra loops.

Interview Connect

Understanding how conditionals affect script speed helps you write clear and efficient scripts. It shows you how decisions inside loops impact overall work.

Self-Check

"What if we added a nested loop inside the if-block that reads lines from each file? How would the time complexity change?"

Practice

1. What is the main purpose of using if statements in a bash script?

easy

A. To make decisions and run different commands based on conditions

B. To repeat commands multiple times

C. To define functions

D. To declare variables

Solution

1. Step 1: Understand the role of if in scripts

   if statements check conditions and decide which commands to run next.

2. Step 2: Compare with other options

   Repeating commands is done by loops, functions define reusable code, and variables store data, so these are not the main purpose of if.

3. Final Answer:

   To make decisions and run different commands based on conditions -> Option A

4. Quick Check:

   Conditionals branch logic = A [OK]

Hint: If it chooses what to do next, it's an if statement [OK]

Common Mistakes:

• Confusing if with loops
• Thinking if defines functions
• Mixing variable declaration with conditionals

2. Which of the following is the correct syntax to start an if statement in bash?

easy

A. if condition {}

B. if (condition) {

C. if condition then

D. if [ condition ]; then

Solution

1. Step 1: Recall bash if syntax

   Bash requires square brackets around the condition and a semicolon before then.

2. Step 2: Check other options for syntax errors

   Options A, B, and C use incorrect syntax styles not valid in bash.

3. Final Answer:

   if [ condition ]; then -> Option D

4. Quick Check:

   Bash if syntax = D [OK]

Hint: Remember: if [ condition ]; then is bash style [OK]

Common Mistakes:

• Omitting semicolon before then
• Using parentheses instead of brackets
• Missing brackets around condition

3. What will be the output of this script?

#!/bin/bash
num=5
if [ $num -gt 10 ]; then
  echo "Greater than 10"
elif [ $num -eq 5 ]; then
  echo "Equals 5"
else
  echo "Less than 5"
fi

medium

A. Equals 5

B. Greater than 10

C. Less than 5

D. No output

Solution

1. Step 1: Check the value of num

   The variable num is set to 5.

2. Step 2: Evaluate the conditions in order

   First condition checks if 5 > 10 (false), second checks if 5 == 5 (true), so it prints "Equals 5".

3. Final Answer:

   Equals 5 -> Option A

4. Quick Check:

   num=5 matches elif condition = A [OK]

Hint: Check conditions top to bottom; first true runs [OK]

Common Mistakes:

• Assuming first condition is true
• Ignoring elif branch
• Confusing numeric comparison operators

4. Identify the error in this bash conditional snippet:

if [ $value = 10 ]; then
  echo "Value is 10"
fi

medium

A. Missing semicolon before then

B. Using single equals for numeric comparison

C. Brackets should be double [[ ]]

D. No error, script runs fine

Solution

1. Step 1: Understand comparison operators in bash

   For numeric comparison inside [ ], use -eq instead of =.

2. Step 2: Check the snippet

   The snippet uses = which is for string comparison, so numeric comparison is incorrect here.

3. Final Answer:

   Using single equals for numeric comparison -> Option B

4. Quick Check:

   Numeric compare needs -eq not = [OK]

Hint: Use -eq for numbers, = for strings in [ ] [OK]

Common Mistakes:

• Confusing string and numeric operators
• Thinking = works for numbers
• Ignoring bash operator rules

5. You want a script to print "Positive", "Zero", or "Negative" based on a variable num. Which conditional structure correctly branches all cases?

hard

A. if [ $num -ge 0 ]; then echo "Positive"; else echo "Negative"; fi

B. if [ $num = 0 ]; then echo "Zero"; else echo "Non-zero"; fi

C. if [ $num -gt 0 ]; then echo "Positive"; elif [ $num -eq 0 ]; then echo "Zero"; else echo "Negative"; fi

D. if [ $num -lt 0 ]; then echo "Negative"; elif [ $num -gt 0 ]; then echo "Positive"; fi

Solution

1. Step 1: Identify all required cases

   We need to handle positive (>0), zero (=0), and negative (<0) values.

2. Step 2: Check each option for coverage

   if [ $num -gt 0 ]; then echo "Positive"; elif [ $num -eq 0 ]; then echo "Zero"; else echo "Negative"; fi covers all three cases with if, elif, else branches. Others miss zero or one case.

3. Final Answer:

   if [ $num -gt 0 ]; then echo "Positive"; elif [ $num -eq 0 ]; then echo "Zero"; else echo "Negative"; fi -> Option C

4. Quick Check:

   All cases covered with if-elif-else = B [OK]

Hint: Use if-elif-else to cover all conditions [OK]

Common Mistakes:

• Missing zero case
• Using wrong comparison operators
• Not using else for last case