Here documents (<<EOF) in Bash Scripting - Time & Space Complexity

Time Complexity: Here documents (<<EOF)

O(n)

Understanding Time Complexity

We want to understand how the time it takes to run a script with a here document changes as the input grows.

Specifically, how does the script's work increase when the here document content gets bigger?

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

cat <<EOF
Line 1
Line 2
Line 3
EOF

This script uses a here document to send multiple lines of text to the cat command, which prints them out.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: Reading and printing each line from the here document.
• How many times: Once for each line inside the here document.

How Execution Grows With Input

As the number of lines in the here document grows, the script reads and prints more lines.

Input Size (n lines)	Approx. Operations
10	10 reads and prints
100	100 reads and prints
1000	1000 reads and prints

Pattern observation: The work grows directly with the number of lines; doubling lines doubles work.

Final Time Complexity

Time Complexity: O(n)

This means the time to run the script grows linearly with the number of lines in the here document.

Common Mistake

[X] Wrong: "The here document runs instantly no matter how many lines it has."

[OK] Correct: Each line must be read and processed, so more lines mean more work and more time.

Interview Connect

Understanding how input size affects script time helps you write efficient scripts and explain your reasoning clearly in interviews.

Self-Check

"What if the here document content was piped to a command that processes lines twice? How would the time complexity change?"

Practice

1. What is the main purpose of using a here document (<

easy

A. To provide multiple lines of input or text to a command easily

B. To create a new file automatically

C. To run commands in the background

D. To define a function in the script

Solution

1. Step 1: Understand the here document concept

   A here document lets you send multiple lines of text or commands as input to a command in a script.

2. Step 2: Identify the correct purpose

   It is not for creating files, running background commands, or defining functions, but for providing multiline input.

3. Final Answer:

   To provide multiple lines of input or text to a command easily -> Option A

4. Quick Check:

   Here document = multiline input [OK]

Hint: Here documents send blocks of text to commands [OK]

Common Mistakes:

• Thinking it creates files automatically
• Confusing with background job control
• Assuming it defines functions

2. Which of the following is the correct syntax to start a here document in bash?

easy

A. command <

B. <

C. command EOF<<

D. << command EOF

Solution

1. Step 1: Recall the here document syntax

   The correct syntax places the command first, then <

2. Step 2: Match the options

   Only command <

3. Final Answer:

   command < -> Option A

4. Quick Check:

   Command before <

Hint: Command comes before <

Common Mistakes:

• Putting <
• Swapping EOF and <<
• Adding spaces incorrectly

3. What will be the output of this script?

cat <

medium

A. Hello $USER

B. Hello (your username)

C. Syntax error

D. Hello EOF

Solution

1. Step 1: Understand variable expansion in here documents

   Without quotes around EOF, variables like $USER are expanded to their values.

2. Step 2: Predict the output

   The script prints Hello followed by your actual username, not the literal $USER.

3. Final Answer:

   Hello (your username) -> Option B

4. Quick Check:

   Unquoted EOF expands variables [OK]

Hint: Unquoted EOF expands variables inside [OK]

Common Mistakes:

• Expecting $USER to print literally
• Thinking it causes syntax error
• Confusing EOF marker as output

4. Identify the error in this script snippet:

cat <<'EOF'
Hello $USER
EOF

medium

A. The EOF marker should not be quoted

B. EOF must be uppercase

C. Missing semicolon after <<'EOF'

D. Variables inside quoted EOF are not expanded, so $USER prints literally

Solution

1. Step 1: Understand quoting effect on here documents

   Quoting the EOF marker disables variable expansion inside the here document.

2. Step 2: Identify the output behavior

   Because of quotes, $USER prints literally, which may be unexpected.

3. Final Answer:

   Variables inside quoted EOF are not expanded, so $USER prints literally -> Option D

4. Quick Check:

   Quoted EOF disables variable expansion [OK]

Hint: Quoted EOF means no variable expansion [OK]

Common Mistakes:

• Thinking quotes cause syntax error
• Expecting variables to expand inside quoted EOF
• Believing EOF must be uppercase

5. You want to create a script that sends this exact text to a file, including the literal string $PATH:

Path is: $PATH

Which here document syntax should you use?

hard

A. cat <<"EOF" > file.txt
Path is: $PATH
EOF

B. cat < file.txt
Path is: $PATH
EOF

C. cat <<'EOF' > file.txt
Path is: $PATH
EOF

D. cat < file.txt
Path is: \$PATH
EOF

Solution

1. Step 1: Understand how to prevent variable expansion

   To keep $PATH literal, quote the EOF marker to disable expansion.

2. Step 2: Choose the correct syntax

   Using <<'EOF' prevents $PATH from expanding, so the exact text is written.

3. Final Answer:

   cat <<'EOF' > file.txt Path is: $PATH EOF -> Option C

4. Quick Check:

   Quote EOF to keep variables literal [OK]

Hint: Quote EOF to keep variables literal in output [OK]

Common Mistakes:

• Not quoting EOF and expecting literal $PATH
• Using escape \$PATH inside unquoted EOF
• Using double quotes which still expand variables