4 ms·
It's all about balance really and this is part of the problem. 1500 lines of code for a function/method would strongly suggest a problem. In the same way as a
by reallydontask 7y ago
It's all about balance really and this is part of the problem.
1500 lines of code for a function/method would strongly suggest a problem. In the same way as a 200 function/methods would make it hard to follow.
- barking 7y agoIf breaking up a procedure results in the creation of a bunch of smaller procedures that are only called once then I think I'd prefer to leave it as it was with well demarcated and commented sub-sections. It saves you the job of inventing descriptive procedure names as well as jumping between procedures. I seem to recall also that in Code Complete, Steve McConnell claimed that there was an inverse relation between the length of a procedure and the number of errors per line of code.
- CuriouslyC 7y agoHow is an inline function different from a demarcated and commented subsection? It seems to me that the semantic and enforced correctness benefits of functions would make using them in this way a no brainer.