Having empty statements can be unproductive in PHP

Software ResiliencyCode Reliability

Having empty statements can be unproductive in PHP

This code insight counts a violation each time an empty statement is detected in PHP

<?php

statement1 {
// comment //Violation
}

statement2 (conditions) {
// comment //Violation
}
}
}

Remedy –

Modify the source code to reduce the number of artifacts containing empty statements.

5362

Why you should care

For maintainability reasons, empty statements should be avoided. Empty statements make the source code harder to read and to maintain.

Business Impacts

Production Risk

CAST recommendations

References

http://pear.php.net/package/PHP_CodeSniffer/docs/1.5.2/PHP_CodeSniffer/Squiz_Sniffs_CodeAnalysis_EmptyStatementSniff.html

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