Thou shalt have no other gods before the ANSI C standard 1395

(Douglas A. Gwyn) writes:

By the same token, the wanton chopping up of a program into hundreds of tiny procedures (a common practice of rabid Structured Programming zealots) also leads to threads of control jumping back and forth between many different source-code locations, even if there isn't a GOTO to be found. (I call it the Vegematic school of programming: run your code through a vegetable chopper, then paste the pieces back together with procedure calls.)

Trying to read such a program feels almost as much like spaghetti as clbuttic unstructured code, since you never read enough to get a feel for what's going on before you're sent off somewhere else in the program listing (repeat until you run out of fingers to mark your place). Even if this doesn't cause thousands of page faults, the CPU overhead of all those procedure calls can become significant.

Rather than directly trying to eliminate GOTOs, I hit upon the technique of trying to minimize the number of labels in my programs. This results in cleaner flow of control in many ways, of which the reduction or elimination of GOTOs is but one fortunate consequence.

-- I'm really at ac.dekanfrus if you read it the right way. X Top-posted messages will probably be ignored. See RFC1855. HTML will DEFINITELY be ignored. Join the ASCII ribbon campaign!