if-then-else in Bash Scripting - Time & Space Complexity

Time Complexity: if-then-else

O(1)

Understanding Time Complexity

We want to understand how the time it takes to run an if-then-else statement changes as the input changes.

Specifically, does adding more data make it slower?

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

#!/bin/bash

value=$1

if [ "$value" -gt 10 ]; then
  echo "Value is greater than 10"
else
  echo "Value is 10 or less"
fi

This script checks if a number is greater than 10 and prints a message accordingly.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: Single if-then-else condition check
• How many times: Exactly once per script run

How Execution Grows With Input

The script runs the if-then-else check once no matter what the input number is.

Input Size (n)	Approx. Operations
10	1 check
100	1 check
1000	1 check

Pattern observation: The number of operations stays the same regardless of input size.

Final Time Complexity

Time Complexity: O(1)

This means the time to run the if-then-else does not grow with input size; it stays constant.

Common Mistake

[X] Wrong: "If the input number is bigger, the script takes longer because it has to compare more digits."

[OK] Correct: The if-then-else only checks the value once, no matter how big the number is. It does not look at each digit separately.

Interview Connect

Understanding that simple condition checks run in constant time helps you explain how your scripts behave as inputs change. This clear thinking is useful in many scripting and automation tasks.

Self-Check

"What if we added a loop inside the if-then-else that runs n times? How would the time complexity change?"

Practice

1. What does the if-then-else structure do in a bash script?

easy

A. It comments out lines in the script.

B. It repeats a set of commands multiple times.

C. It defines a function to reuse code.

D. It lets the script choose between two paths based on a condition.

Solution

1. Step 1: Understand the purpose of if-then-else

   The if-then-else structure checks a condition and runs code based on whether the condition is true or false.

2. Step 2: Compare with other options

   Repeating commands is done with loops, functions reuse code, and comments do not execute code.

3. Final Answer:

   It lets the script choose between two paths based on a condition. -> Option D

4. Quick Check:

   if-then-else = choose path [OK]

Hint: If you see a condition, it's likely if-then-else [OK]

Common Mistakes:

• Confusing if-then-else with loops
• Thinking if-then-else defines functions
• Mixing comments with control flow

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

easy

A. if [ condition ]; then

B. if { condition } then

C. if(condition) then

D. if condition then

Solution

1. Step 1: Recall bash if syntax

   Bash requires spaces around brackets and a semicolon before then: if [ condition ]; then.

2. Step 2: Check other options

   if(condition) then misses spaces and semicolon, B uses braces incorrectly, D misses brackets and semicolon.

3. Final Answer:

   if [ condition ]; then -> Option A

4. Quick Check:

   Spaces and semicolon needed [OK]

Hint: Remember spaces around [ ] and semicolon before then [OK]

Common Mistakes:

• No spaces around brackets
• Missing semicolon before then
• Using parentheses or braces incorrectly

3. What will be the output of this script?

#!/bin/bash
x=5
if [ $x -gt 3 ]; then
  echo "Greater"
else
  echo "Smaller"
fi

medium

A. No output

B. Smaller

C. Greater

D. Syntax Error

Solution

1. Step 1: Evaluate the condition

   The condition checks if x (5) is greater than 3, which is true.

2. Step 2: Determine which branch runs

   Since condition is true, the script prints "Greater".

3. Final Answer:

   Greater -> Option C

4. Quick Check:

   5 > 3 = Greater [OK]

Hint: Check numeric comparison carefully [OK]

Common Mistakes:

• Confusing -gt with -lt
• Missing spaces causing syntax errors
• Assuming else runs when condition is true

4. Find the error in this script:

#!/bin/bash
if [ $num -eq 10 ]
  echo "Ten"
else
  echo "Not Ten"
fi

medium

A. Missing then after condition

B. Wrong comparison operator

C. Missing fi at the end

D. No error

Solution

1. Step 1: Check if statement syntax

   The if condition must be followed by then keyword to start the true block.

2. Step 2: Identify missing part

   The script misses then after the condition line.

3. Final Answer:

   Missing then after condition -> Option A

4. Quick Check:

   if needs then [OK]

Hint: Always put then after condition in if [ ] [OK]

Common Mistakes:

• Forgetting then keyword
• Using wrong comparison operators
• Missing fi to close if

5. You want a script that prints "Even" if a number is even, and "Odd" if it is odd. Which script correctly uses if-then-else to do this?

num=4
# Choose correct script

hard

A. if [ $num % 2 -eq 0 ]; then
echo "Even"
else
echo "Odd"
fi

B. if (( num % 2 == 0 )); then
echo "Even"
else
echo "Odd"
fi

C. if [ $num % 2 == 0 ]; then
echo "Even"
else
echo "Odd"
fi

D. if [ $num / 2 -eq 0 ]; then
echo "Even"
else
echo "Odd"
fi

Solution

1. Step 1: Understand arithmetic evaluation in bash

   Using double parentheses (( )) allows arithmetic expressions and comparisons directly.

2. Step 2: Check each option

   if [ $num % 2 -eq 0 ]; then echo "Even" else echo "Odd" fi uses % inside [ ] without arithmetic evaluation. if [ $num % 2 == 0 ]; then echo "Even" else echo "Odd" fi uses % inside [ ] without arithmetic evaluation. if [ $num / 2 -eq 0 ]; then echo "Even" else echo "Odd" fi uses / instead of % for modulus. if (( num % 2 == 0 )); then echo "Even" else echo "Odd" fi correctly uses (( )) with modulus and comparison.

3. Final Answer:

   if (( num % 2 == 0 )); then echo "Even" else echo "Odd" fi -> Option B

4. Quick Check:

   Use (( )) for arithmetic if [OK]

Hint: Use (( )) for math conditions in bash [OK]

Common Mistakes:

• Using [ ] with arithmetic operators incorrectly
• Confusing / with % for modulus
• Missing then keyword