学习Shell脚本：是否存在类似Python的EAFP异常处理风格？

Great question! While Shell scripting doesn’t have a formal "EAFP" (Easier to Ask for Forgiveness than Permission) label like Python, the core idea of attempting an operation first and handling failures afterward is absolutely common and widely used in shell scripts.

What EAFP Looks Like in Shell #

In Python, you rely on try/except blocks to catch exceptions. In Shell, we leverage command exit status codes (where 0 means success, non-zero means failure) along with operators like || (execute on failure) or if ! to handle errors after the fact—instead of pre-checking every possible condition.

Example 1: Reading a File (EAFP vs LBYL)

Traditional "Look Before You Leap" (LBYL) approach (pre-checking every condition):

if [ -f "$file_path" ]; then
    cat "$file_path"
else
    echo "Error: File $file_path does not exist!" >&2
fi

EAFP approach (try the operation first, handle failure if it happens):

cat "$file_path" || echo "Oops! Failed to read $file_path. It might not exist or we lack permissions." >&2

For more complex error handling logic:

if ! cat "$file_path"; then
    echo "Critical error: Could not access $file_path" >&2
    # Add recovery steps here, like exiting the script or falling back to a default file
    exit 1
fi

Example 2: Creating a Directory

Instead of checking if the directory exists before creating it:

# EAFP style
mkdir "$new_dir" || {
    echo "Warning: Failed to create $new_dir. It may already exist." >&2
    # Optional: Add fallback logic, like using the existing directory anyway
}

Why This Works in Shell #

Shell commands naturally return exit codes, making it straightforward to chain failure handlers. This approach also avoids race conditions—for example, if you check if a file exists and then try to read it, the file could be deleted between the check and the read. Using EAFP skips the pre-check and handles the failure directly, eliminating that risk.

Advanced Error Handling #

For more complex scenarios, you can use trap to catch signals or exit codes globally, but the core EAFP philosophy remains: prioritize executing the desired action over pre-validating every possible edge case.

内容的提问来源于stack exchange，提问作者Wizard