Hello all, after reading Larry Barnes' OT post on OCT31 and DEC25,
(while working with someone elses code) I got to thinking about
programming do's, don'ts and gotcha's. Actually, that isn't true. I got
rather annoyed at the way much of the code was written. Then I humbly
considered whether it was simply my empirical and educational bias
rearing its ugly head, or simply a matter of programming styles.
So, even though many in this august group of professionals, at times, may
make me feel that my measly 11 years, or so, in the field makes me virtually a
programming neophyte in comparison (especially with some of the history
you all have behind you ! ) I wanted to submit a few questions or topics, if you
will. These reference COBOL II/XL. But please feel no need to limit reponses to
it, because I also seem to program in other languages along the same guidelines
as those I use in COBOL. Which was the first programming language I learned,
and the one in which I've done the most work.
- Is it better to use what I call "Fall-Down" or Fall-Thru logic ? i.e. No
main flow control, but what I like to call "The Pachinko Machine" effect.
- Are explicit scope terminators (END-IF/END-CALL/END-PERFORM...)
better or more efficient than implicit scope terminators ?
- When branching to perform a paragraph of instructions is it better to
use an exit paragraph and perform thru it ? i.e. PERFORM
PARAGRAPH-1 THRU PARAGRAPH-1-EXIT. Using the "EXIT"
statement.
Yes, they are perhaps a tad generalized in a sense. And "better" is usually
subject to relativity. Nonetheless, I value the opinion of the people that
congregate in this virtual community. So...
Thank you.
-------------------------------------------------------------------------
David Burney [log in to unmask]
Summit Racing Equipment http://www.summitracing.com
-----------
"Then hate me when thou wilt; if ever, now..."
William Shakespeare - Sonnet X
-----------
All opinions expressed herein are my own and reflect,
in no way, those of my employer.
|
