3 SC3013

Lawrence Velázquez edited this page 2024-03-08 20:05:45 -05:00

Table of Contents

• In POSIX sh, -nt is undefined.
• Problematic code:
• Correct code:
• Rationale:
• Exceptions:
• Related resources:

In POSIX sh, -nt is undefined.

Problematic code:

#!/bin/sh
if [ Foo.java -nt Foo.class ]
then
  javac Foo.java
fi

Correct code:

The easiest fix is to switch to a shell that does support -nt, like bash:

#!/bin/bash
if [ Foo.java -nt Foo.class ]
then
  javac Foo.java
fi

Otherwise, find can be used:

#!/bin/sh
if [ -n "$(find Foo.java -newer Foo.class)" ]
then
  javac Foo.java
fi

Rationale:

test -nt is an extension in ksh, bash and dash, but it is not specified by POSIX.

Exceptions:

If you only intend to target shells that supports this feature, you can change the shebang to a shell that guarantees support, or ignore this warning.

You can use # shellcheck disable=SC3000-SC4000 to ignore all such compatibility warnings.

Related resources:

• Greg's Wiki
  • BashFAQ #3: How can I sort or compare files based on some metadata attribute (newest / oldest modification time, size, etc)?
  • Bashism - Conditionals

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.