> There's architectural spaghetti and there are lower levels of spaghetti.... > The problem isn't merely converting goto to PERFORM-TIMES. It's that deep in th

> There's architectural spaghetti and there are lower levels of spaghetti.... > The problem isn't merely converting goto to PERFORM-TIMES. It's that deep in that loop you're also doing raw database operations, writing stuff to a IBM 3270 terminal, and triggering a batch job to the program monitor. I'm not saying that's not a problem, just that it feels like it could be an anachronism to use "spaghetti code" to refer to that in the context of a COBOL program.