10 SC1037

John Gardner edited this page 2021-12-22 19:31:44 +11:00

Table of Contents

• Braces are required for positionals over 9, e.g. ${10}.
• Problematic code:
• Correct code:
• Rationale:
• Exceptions
• Related resources:

Braces are required for positionals over 9, e.g. ${10}.

Problematic code:

echo "Ninth parameter: $9"
echo "Tenth parameter: $10"

Correct code:

echo "Ninth parameter: $9"
echo "Tenth parameter: ${10}"

Rationale:

For legacy reasons, $10 is interpreted as the variable $1 followed by the literal string 0.

Curly braces are needed to tell the shell that both digits are part of the parameter expansion.

Exceptions

If you wanted the trailing digits to be literal, ${1}0 will make this clear to both humans and ShellCheck.

In dash, $10 is (wrongly) interpreted as ${10}, so some 'reversed' care should also be taken:

bash -c 'set a b c d e f g h i j; echo $10 ${1}0' # POSIX: a0 a0
dash -c 'set a b c d e f g h i j; echo $10 ${1}0' # WRONG: j a0

Related resources:

• BashFaq: How can I access positional parameters after $9?
• StackOverflow: How to handle more than 10 parameters in shell
• Autoconf Manual: Shell Substitutions - documents some non-POSIX older shells too

ShellCheck

• Installation

  • CentOS6
  • More Installation Guides

• Usage

  • Directive
  • Ignore

• Integrating and extending

  • Misc. contributions
  • Azure Pipelines
  • Buildkite
  • CircleCI
  • DevGuide
  • Integration
  • JUnit
  • Phabricator
  • TravisCI
  • GitLab CI
  • Drone
  • GitHub Actions

• Severity

• Template

Each individual ShellCheck warning has its own wiki page like SC1000. Use GitHub Wiki's "Pages" feature above to find a specific one, or see Checks.