No explicit EXIT instruction in last statement in KSH can be risky

Production RiskSoftware ResiliencyCode Reliability

No explicit EXIT instruction in last statement in KSH can be risky

This code insight counts one violation each time the last instruction of the script is not EXIT.
5362

Why you should care

If no exit is used, the default behaviour is to exit with the return code of the last command executed. A well controlled error management practice is to to terminate with an explicit EXIT statement.

Business Impacts

Production Risk

CAST recommendations

References

5362

About CAST and Highlight’s Code Insights

Over the last 25 years, CAST has leveraged unique knowledge on software quality measurement by analyzing thousands of applications and billions of lines of code. Based on this experience and community standards on programming best practices, Highlight implements hundreds of code insights across 15+ technologies to calculate health factors of a software.

See featuresHow it works