gotostatement. The ideals of structured programming have been so completely incorporated in modern programming that some newer languages, eg Java, don't even have the
gotostatement. The Java designers must have thought leaving out
gotowas risky because
gotois still reserved as a keyword, but is not used.
MacCabe proposed measuring flow complexity of a function (method) as the number of decision points. His algorithm is to count 1 for just entering the method, plus one for each if, for, while, do-while, case, &&, and ||. To update his measure for Java we should also add 1 for each ?: operator, catch statement, and default clause.
Break up complex methods. A MacCabe complexity under 5 is good, from 5-10 is ok, and over 10 is too complex. A high flow complexity may also be a symptom of a function which does too much and has low cohesion. But don't take these numbers too seriously -- you may have comprehensible control flow despite high numbers, eg generated by one large case statement. But how do you simplify a method? Presumably all decisions have to be made. You simplify a method by breaking it into two or more methods, so the complexity, the demands on the human to keep many things in their mind at the same time, are reduced.