Re: Code problems with Perform Thru Exit causes fall through
- From: Howard Brazee <howard@xxxxxxxxxx>
- Date: Fri, 27 Jul 2007 14:17:42 -0600
On Fri, 27 Jul 2007 19:44:16 GMT, spambait@xxxxxxxxxx (Doug Miller)
wrote:
Being lazy and not wanting to do this type of checking I avoid all
need for it by using code that never requires it. ie No SECTIONs, no
GOTO, no THRU, no EXIT PERFORM/PARAGRAPH/SECTION, no NEXT SENTENCE.
Agree completely.
Me too.
Scope terminators have completely removed the need for NEXT
SENTENCE. And anybody who uses SECTIONs in the Procedure Division should be
shot.
Please don't shoot me. I have to use IDMS copy statements that were
coded with sections. Back when SORT required statements I started
having a.
REST-OF-THE-PROGRAM SECTION.
I still use that when adding paragraphs to programs with sections.
Besides the problems mentioned in the previous message, I am irritated
with the following code:
PERFORM MY-SECTION THRU MY-SECTION-EXIT.
MY-SECTION.
MY-PROGRAM.
....
MY-SECTION-EXIT.
EXIT.
.
- Follow-Ups:
- Re: Code problems with Perform Thru Exit causes fall through
- From: Doug Miller
- Re: Code problems with Perform Thru Exit causes fall through
- References:
- Code problems with Perform Thru Exit causes fall through
- From: Lizette Koehler
- Re: Code problems with Perform Thru Exit causes fall through
- From: Richard
- Re: Code problems with Perform Thru Exit causes fall through
- From: Doug Miller
- Code problems with Perform Thru Exit causes fall through
- Prev by Date: Re: Code problems with Perform Thru Exit causes fall through
- Next by Date: Re: unstring empty string
- Previous by thread: Re: Code problems with Perform Thru Exit causes fall through
- Next by thread: Re: Code problems with Perform Thru Exit causes fall through
- Index(es):