Shell String Manipulation: Safe Methods for Retrieving the Last Character

Problem Background and Phenomenon Analysis

In Shell script development, retrieving the last character of a string is a common requirement. The original implementation uses string length calculation and substring extraction:

str=$1
i=$((${#str}-1))
echo ${str:$i:1}

This approach works correctly with ordinary strings, such as returning / when input is abcd/. However, when the input contains special characters like abcd*, the script exhibits unexpected behavior, outputting the file list in the current directory instead of the expected * character.

Root Cause: Shell Expansion Order

The core issue lies in the order of Shell expansions. According to the Bash reference manual, variable expansion occurs before filename expansion. When variables are unquoted, Bash performs variable expansion first, then applies filename expansion (globbing) to the result.

In the abcd* example, variable expansion yields the string abcd*, which is then interpreted by filename expansion as a wildcard pattern, matching all files in the current directory starting with abcd, ultimately outputting the file list instead of the last character.

Standard Solution: Parameter Expansion Syntax

Bash provides dedicated parameter expansion syntax to directly retrieve the last character of a string:

echo "${str: -1}"

Or equivalently:

echo "${str:0-1}"

Both syntaxes leverage Bash's support for negative indices, counting from the end of the string. -1 denotes the last character, -2 the second last, and so on.

Critical Detail: Importance of the Space

In the ${str: -1} syntax, the space after the colon is mandatory. If omitted, written as ${str:-1}, Bash interprets it as the use-default-values syntax:

${parameter:-word}
Use Default Values. If parameter is unset or null, the expansion of word is substituted. Otherwise, the value of parameter is substituted.

This means when str is empty or unset, the expression returns 1 instead of retrieving the last character.

Importance of Variable Quoting

Even in the original method, proper variable quoting can prevent filename expansion issues:

str=$1
i=$((${#str}-1))
echo "${str:$i:1}"

By enclosing variables in double quotes, Shell is prevented from performing word splitting and filename expansion on the variable value. Additionally, parameters should be quoted when calling the script:

bash last_ch.sh 'abcd*'

Alternative Methods Comparison

Besides parameter expansion, external command combinations can be used:

echo -n $str | tail -c 1

Here, the -n option prevents echo from outputting a newline, and tail -c 1 extracts the last byte. While functional, this method involves process creation and piping, resulting in inferior performance compared to built-in parameter expansion.

Best Practices Summary

Considering performance, conciseness, and reliability, using the ${str: -1} syntax is recommended for retrieving the last character of a string. Key takeaways include:

• Always quote variables to prevent unintended expansions
• Ensure the space after the colon in parameter expansion is preserved
• Quote parameters containing special characters when calling scripts
• Understand the impact of Shell expansion order on script behavior

These practices apply not only to retrieving the last character but to all Shell programming tasks involving string manipulation and variable operations.