Dear community, it’s no secret: I’m a big fan of CleanABAP and always looking for chances to improve my own coding style based on the guiding principles of “readable, testable, maintainable”. To do this, you have to think outside the box. So always look for suggestions for improvement everywhere.
Fresh ideas or confirmations of approaches can be found, for example, in other programming languages like Java, or, as in this case, in the “Sonar Rules“, published by company SonarSource.
They use these rules in their software for static code analysis and kindly made the individual rules available online. Divided into the criteria “Vulnerability”, “Bug”, “Security Hotspot” and “Code Smell”.
A good source to check your own ABAP programming style, although you may not have to conform to all the rules (this is ultimately the same situation as with the CleanABAP Style Guide).
In any case, a big thank you for making the rules freely available. A small note at the end: There are rules to read not only for ABAP, but also for COBOL, for example. Also interesting to see.
Enjoy browsing
Michael