Production RiskSoftware ResiliencyCode Reliability
Macro definitions cause resiliency issues
Production Risk
Macro definitions cause resiliency issues
This code insight counts one violation each time a macro without parameters defines a literal constant.
Literal constants are number, character or strings :
– numbers, possibly preceded with . or \
– characters enclosed with ‘
– strings, enclosed with ‘ or “
Exemple of violations : (123, .25, \123), un caractere (‘…’) ou une chaine (“…”)
Why you should care
Code with macro definitions can cause resiliency issues.
Business Impacts
CAST recommendations
References
https://www.tutorialspoint.com/sql/sql-transactions.htm
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