I was commenting directly at the static method the OP asked about, and at static methods in general.
Understood -- but why assume that Cyclomatic Complexity or Interface Complexity *must* be analyzed statically?
As a measure, complexity is a very bad indicator of anything useful. Some, (most) systems are complex by their very nature.
I understand that metrics are often abused, but that doesn't mean they're useless.
It would be foolish to try to maximize one metric without considering the tradeoffs -- as shown by your experience of driving down CC while allowing LOC to mushroom... But being able to compare several different implementations on the basis of multiple metrics seems helpful.
The most reliable car, is one without an engine. It's less complex, but is it "better"?
Of course you should include "do the tests pass" as one of your key metrics.
Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
Want more info? How to link
or How to display code and escape characters
are good places to start.