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

? a PERFORM does a push, jump, (blahblahblah), pop, jump... guy *did* save code as measured by executable static memory size. Of course he also added to the number of instructions necessary to run the program because of the added PERFORMs overhead (duh). YMMV as to whether that's a good tradeoff for maintainability.

call from the subroutine?" test into the bin and put whatever the common statements were outside the mainline to be PERFORMed from the mainline as well as from everywhere else.

(Now it) sounds like an input read from a tape file with alot of level-breaks (a flattened rdb)(?).

Yeah but you said 'spaghetti code'; (to me) that means something that's basically duct-tape and string... patches by people with different writing methods (or lack of) for instance. If there was a consistent "method in the madness" then that's just a different structuring-coding method ('spaghetti code' being an inaccurate slur).

If you're using a mainline and perform statements, then you want-need to put high-iteration code at the front of the program to avoid paging. (You still don't want it in the mainline (which is just flow-control) though)

That's good 'cause I don't speak 'C'. ("Why did the chicken cross the fanfold? To write a C program"), but it sounds like basically you're tossing main control back and forth between two parts of the program.

no clue. Maybe the mainline should've explicitly included the flow-control part of the subroutine...

rpl