It goes back further than that. Some dialects of FORTRAN supported both multiple entry points
and multiple exit points. It was widely considered to be a nightmare to have both in the same module.
Structured Programming, after all, was developed to, er, "structure" code so that more time could be spent figuring out what something did as opposed to how it did it. It took a wild collection of spaghetti, with gotos, entries, returns
et al. and reduced it to a set of simple consistent constructs. People tend to forget that this was quite a radical concept back then - after all, spaghetti code was more "efficient". An assertion that was open to argument even then. But structured code is easier for a machine process to optimize, so no one argues anymore.
It's not so much that I adopted a "rules are made to be broken"
philosophy, as that I added a rule of my own.
Diverging a second level, however, I'd like to observe that an academic of some note, whose name, alas, I forget claimed that the concept of "not" in and of itself is troublesome to a lot of people to the degree that he'd actually arranged special instruction on the subject. Myself, I studied the Propositional Calculus and worked with IBM mainframe JCL (If "condition" is NOT true, then DO NOT execute this program). Probably explains why when I first tried to make my own pretzels they came out so well.