>>>what was then called structured programming
>Actually, the structured programming ideas were pretty good.
>They were primarily aimed at COBOL so many of the ideas no longer apply.
>One of the key ideas was that unless code is reused, putting it in modules just for the sake of modularity makes the code less readable and adds no value.
>
>That's still true.
>
>XBase and languages like it made SP largely irrelevant tho,
>One of the basic tenets of SP was the elmiination of the GOTO and there IS no GOTO in XBase.
>I'm not sure about Basic tho. Did some variants keep the GOTO alive?
>
>One of the SP tenets that I see violated all the time is the notion that a module should have one entry point and one exit point.
>The elmiination of GOTO took care of the entry point, but when I see XBase and .NET code with returns sprinkled throughout the module I still shudder.
>I know that it's sometimes more efficient to have several, but it still makes sense to me that there should be only one exit point and that's how I code.

I wasn't knocking structured programming. All I meant was the the developer(s) of this abominable code don't seem to have even been familiar with development techniques that are 40 years old.