In-depth Analysis and Solutions for [: unexpected operator Error in Shell Scripting

Problem Phenomenon and Background

In Shell programming practice, developers often encounter error messages like [: unexpected operator. This error typically occurs when using specific Shell extension syntax that is not supported by the execution environment. This article will use a specific user case as a basis to deeply analyze the root cause of this error and provide detailed solutions.

Error Case Analysis

Consider the following Shell script code:

#!/bin/sh
#filename:choose.sh
read choose
[ "$choose" == "y" -o "$choose" == "Y" ] && echo "Yes" && exit 0
[ "$choose" == "n" -o "$choose" == "N" ] && echo "No"  && exit 0
echo "Wrong Input" && exit 0

When executing this script with the command sh ./choose.sh, the terminal displays the following error messages:

[: 4: n: :Unexpected operator
[: 5: n: :Unexpected operator

Root Cause Analysis

The core of this problem lies in the compatibility differences between Shell interpreters. The == operator used in the script is a Bash-specific string comparison operator, while POSIX standard Shell only supports the = operator for string comparison.

Specifically:

• Bash Extension Syntax: Bash, as GNU Shell, provides rich extension features, including the == operator
• POSIX Standard Syntax: POSIX Shell standard specifies using = for string equality comparison
• Execution Environment Mismatch: Although the script's shebang specifies #!/bin/sh, the actual execution might use different Shell implementations

Solutions

Solution 1: Modify Execution Method

The most direct solution is to execute the script using the Bash interpreter:

bash ./choose.sh

Or modify the script's shebang to:

#!/bin/bash

Solution 2: Use POSIX-Compatible Syntax

Replace the == operator in the script with the POSIX-standard = operator:

#!/bin/sh
read choose
[ "$choose" = "y" -o "$choose" = "Y" ] && echo "Yes" && exit 0
[ "$choose" = "n" -o "$choose" = "N" ] && echo "No"  && exit 0
echo "Wrong Input" && exit 0

Solution 3: Use Case Statement

For scenarios involving multiple condition matching, using a case statement provides a more elegant solution:

#!/bin/sh
read choose
case "$choose" in
    [yY]) echo "Yes" ; exit 0 ;;
    [nN]) echo "No"  ; exit 0 ;;
    *)    echo "Wrong Input" ; exit 0 ;;
esac

Extended Discussion: Other Common Shell Syntax Pitfalls

The expr command error case mentioned in the reference article further illustrates the syntactic sensitivity in Shell scripting:

Original erroneous code:

a=' expr $a + 1'

Correct写法:

a=`expr $a + 1`

Or using modern Shell syntax:

a=$((a + 1))

Best Practice Recommendations

• Define Execution Environment: Clearly specify the target execution environment when writing scripts and choose appropriate shebang
• Follow POSIX Standards: For scripts requiring cross-platform compatibility,尽量 use POSIX standard syntax
• Testing and Validation: Test script compatibility in different Shell environments
• Use Modern Syntax: Prefer $(( )) for arithmetic operations, avoiding outdated expr command
• Error Handling: Add appropriate error handling mechanisms to enhance script robustness

Conclusion

The [: unexpected operator error in Shell scripting typically stems from syntax compatibility issues. By understanding the differences between various Shell implementations and adopting appropriate solutions, such problems can be effectively avoided. In Shell programming, maintaining code simplicity and portability are crucial principles.