Total complexity of your project is 2264ish. 20% (486/2264) of your
complexity lies in RGB, and I’m guessing that its all building up
your constants (from the names in your report).
What does flog ... | grep -v '^ ' give (just the top-level stuff)
Server#run is a good candidate for refactoring (3% of complexity!),
as is Policy#verify_gem (2%!). main#none is just toplevel code.
(OpenURI is in there for fixing proxy stuff :/)
Note: values are an arbitrary, they only matter relative to the
total, and relative to other modules or methods.
Total complexity of your project is 2264ish. 20% (486/2264) of your
complexity lies in RGB, and I’m guessing that its all building up
your constants (from the names in your report).
Pretty much.
What does flog ... | grep -v '^ ' give (just the top-level stuff)
I think I’m getting it now. Inasmuch as the reported complexity
indicates the likelihood of harder to understand code or potentially
slower code, the percentage of complexity makes a difference.
Not a lot of value for the project I’m flogging right now (the
successor to color-tools that will be used in the upcoming PDF::Writer
1.1.4). Thanks.
What does flog ... | grep -v '^ ' give (just the top-level stuff)
Server#run is a good candidate for refactoring (3% of complexity!), as
is Policy#verify_gem (2%!). main#none is just toplevel code. (OpenURI
is in there for fixing proxy stuff :/)
Note: values are an arbitrary, they only matter relative to the total,
and relative to other modules or methods.
Ah … so it’s a “complexity profile”. Couldn’t flog display its report
with percentages and cumulative percentages? So, for your example, you’d
get: