Why Function libraries (sourcing scripts) in Bash Scripting? - Purpose & Use Cases

The Big Idea

What if fixing one bug could instantly fix it everywhere in your scripts?

The Scenario

Imagine you have many bash scripts that all need to perform the same tasks, like checking if a file exists or formatting output. You copy and paste the same code into each script manually.

The Problem

This manual copying means if you find a bug or want to improve the code, you must update every script one by one. It's slow, easy to forget, and causes mistakes. Your scripts become messy and hard to maintain.

The Solution

Function libraries let you write common functions once in a separate script file. Then, you source that file in your scripts to reuse the functions. Fix or improve the function in one place, and all scripts get the update instantly.

Before vs After

✗ Before

echo "Check file"
if [ -f "$file" ]; then
  echo "File exists"
fi

# Repeat this in every script

✓ After

source ./file_utils.sh
check_file "$file"

# One place for the function, many scripts use it

What It Enables

You can build clean, reusable, and easy-to-maintain bash scripts that save time and reduce errors.

Real Life Example

A system admin writes a network_tools.sh library with functions to check server status and ping hosts. They source it in many scripts to monitor servers without rewriting code.

Key Takeaways

Manual code duplication wastes time and causes errors.

Function libraries let you write code once and reuse it everywhere.

Sourcing scripts keeps your bash projects clean and easy to update.

Practice

1. What is the main purpose of using function libraries in bash scripting?

easy

A. To reuse functions across multiple scripts without rewriting code

B. To make scripts run faster by compiling them

C. To encrypt scripts for security

D. To automatically update scripts from the internet

Solution

1. Step 1: Understand function libraries

   Function libraries contain reusable functions that can be shared across scripts.

2. Step 2: Identify the benefit

   Reusing functions avoids rewriting code and keeps scripts clean and maintainable.

3. Final Answer:

   To reuse functions across multiple scripts without rewriting code -> Option A

4. Quick Check:

   Function reuse = To reuse functions across multiple scripts without rewriting code [OK]

Hint: Function libraries let you reuse code easily [OK]

Common Mistakes:

• Thinking libraries speed up script execution
• Confusing libraries with encryption tools
• Assuming libraries auto-update scripts

2. Which of the following is the correct syntax to source a script named lib.sh in bash?

easy

A. load lib.sh

B. import lib.sh

C. source lib.sh

D. include lib.sh

Solution

1. Step 1: Recall bash sourcing commands

   Bash uses source or . to load another script.

2. Step 2: Identify correct syntax

   source lib.sh correctly loads the script named lib.sh.

3. Final Answer:

   source lib.sh -> Option C

4. Quick Check:

   source command = source lib.sh [OK]

Hint: Use 'source' or '.' to load scripts in bash [OK]

Common Mistakes:

• Using 'import' which is not a bash command
• Using 'include' or 'load' which are invalid in bash
• Forgetting to specify the script name

3. Given two files:

lib.sh:
function greet() {
  echo "Hello, $1!"
}

main.sh:
source ./lib.sh
greet "Alice"

What will be the output when running bash main.sh?

medium

A. greet: command not found

B. No output

C. Hello, $1!

D. Hello, Alice!

Solution

1. Step 1: Understand sourcing effect

   The source ./lib.sh command loads the greet function into main.sh.

2. Step 2: Analyze function call

   Calling greet "Alice" runs the function, echoing "Hello, Alice!".

3. Final Answer:

   Hello, Alice! -> Option D

4. Quick Check:

   Function loaded and called = Hello, Alice! [OK]

Hint: Sourcing loads functions so they can be called directly [OK]

Common Mistakes:

• Not sourcing the library before calling the function
• Expecting variable $1 to be literal
• Confusing function definition with execution

4. Consider this script snippet:

source lib.sh
greet "Bob"

But running it gives: main.sh: line 2: greet: command not found
What is the most likely cause?

medium

A. lib.sh does not define the greet function

B. The source command is misspelled

C. The greet function is called before sourcing lib.sh

D. lib.sh has wrong file permissions

Solution

1. Step 1: Check function definition in lib.sh

   If greet is not defined in lib.sh, sourcing won't load it.

2. Step 2: Analyze error message

   "command not found" means the function is missing, not a syntax or permission error.

3. Final Answer:

   lib.sh does not define the greet function -> Option A

4. Quick Check:

   Missing function definition = lib.sh does not define the greet function [OK]

Hint: Check if function exists in sourced file first [OK]

Common Mistakes:

• Assuming source command typo without checking
• Ignoring function order in script
• Not verifying file permissions

5. You want to create a reusable library utils.sh with a function timestamp that prints the current date and time. How should you write and use it in your script run.sh to print the timestamp?

hard

A. In utils.sh: timestamp() { date; } and in run.sh: ./utils.sh; timestamp

B. In utils.sh: timestamp() { echo $(date); } and in run.sh: source utils.sh; timestamp

C. In utils.sh: function timestamp { echo date; } and in run.sh: ./utils.sh; timestamp

D. In utils.sh: timestamp() { date; } and in run.sh: bash utils.sh; timestamp

Solution

1. Step 1: Define timestamp function correctly

   Use timestamp() { echo $(date); } to print current date and time.

2. Step 2: Source utils.sh in run.sh and call function

   Use source utils.sh to load the function, then call timestamp.

3. Final Answer:

   In utils.sh: timestamp() { echo $(date); } and in run.sh: source utils.sh; timestamp -> Option B

4. Quick Check:

   Correct function and sourcing = In utils.sh: timestamp() { echo $(date); } and in run.sh: source utils.sh; timestamp [OK]

Hint: Use echo $(date) inside function and source before calling [OK]

Common Mistakes:

• Running utils.sh instead of sourcing it
• Using echo date instead of echo $(date)
• Calling function without sourcing library