Why you should care
A piece of source code in your software could be compared to a page of a book. In a book, a human can’t easily read and understand a very long line – it’s all about eye comfort. That’s even more true when reading code, since each keyword could be translated into many words (e.g. “!=” means “is different than”). In addition to negatively affecting readability, having very long lines can destroy the positive impact of code indentation, which makes the code even harder to understand and maintain (because of chaotic line returns). Having shorter lines of code in your application can help developers more quickly understand how the code works. It also tends to reduce semantic misinterpretations that could drive to unexpected behaviors (i.e. bugs).
Static code analysis tools can help your development teams identify this code insight, while peer code review is useful to educate the long-line addicts. Ideally, one line of code is a unit element that means or performs something specific – a part of a sentence if you will.
It is generally agreed that the ideal length for a line of code is from 80 to 100 characters.
How we detect
This code insight counts the number of characters for each line of code and verifies that an application doesn’t globally contain too many long lines. Depending on thresholds defined by CAST based on its expertise and experience in measuring software, Highlight counts penalty points contributing to the Software Agility health factor.
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.