Wed Oct 17 - Avoiding Code Smells by Walter Bright
Stanislav Blinov
stanislav.blinov at gmail.com
Wed Oct 31 13:42:20 UTC 2018
On Wednesday, 31 October 2018 at 13:37:07 UTC, rikki cattermole
wrote:
> On 01/11/2018 2:33 AM, Stanislav Blinov wrote:
>> On Wednesday, 31 October 2018 at 13:28:54 UTC, rikki
>> cattermole wrote:
>>
>>> But at the end of the day, it just depends on the scope of
>>> the module. Is it getting to large? If so, split.
>>
>> Yup. LOC aren't a particulalry informative metric.
>> Documentation, comments, unit tests, blanks, all contribute to
>> it. Split by scope, by concept, by responsibility, by any
>> implementation-relevant metric, not by LOC. As the joke goes,
>> your word processor is doomed to fail once it also starts
>> sending out emails...
>
> Actually it is quite informative. As a code smell it does tell
> you pretty decently in my experience if your scope is too large
> or if you are in need of refactoring.
Well, yes, it can be a litmus test, I guess. I meant to say that
it isn't per se a deciding factor.
More information about the Digitalmars-d-announce
mailing list