Re: COBOL ain't quite dead - yet !


Howard Brazee <howard@xxxxxxxxxx> wrote in message
news:7isgg4lh42b61712dijr6otf1otsscuj92@xxxxxxxxxx
When I worked for EDS a decade or more ago, our published standard was
for each perform to be of a section that consisted of a paragraph and
an exit which wasn't used. I disliked it back then, and hope it has
been changed since.

--

Lots of people these days insist that a PERFORM must address only a
paragraph name (i.e., don't use THRU). This ancient EDS standard at least
conforms in appearance!

PL


.

Relevant Pages

  • Re: Para1 THRU Para2
    ... HB>>> The best way to exit a paragraph this way is with an EXIT ... r> putting everything in one sentence makes the nesting too deep. ... One has to look at this logically, and create a transformation ...
    (comp.lang.cobol)
  • Re: COBOL aint quite dead - yet !
    ... sometimes I will replace the EXIT. ... the exactly the same label made into a comment. ... Putting in a paragraph label is a lightweight ... possibility of errors such as goto the wrong one, ...
    (comp.lang.cobol)
  • Re: COBOL aint quite dead - yet !
    ... sometimes I will replace the EXIT. ... was via the last paragraph. ... In Cobol a label may be the target of a goto, a perform, a drop ...
    (comp.lang.cobol)
  • Re: Infinite Loops and Explicit Exits
    ... Massive changes qualify as a 'redesign'. ... A perform of a section or a perform of a paragraph is no matter as both ... Afterwards they would reset the exit point back to what it ... > was a NULop. ...
    (comp.lang.cobol)
  • Re: Is it possible to use the value of the PROGRAM ID within the source code?
    ... The IBM 705 had an instruction pair something ... And once you were used to using such now known as bad practice ... Then what was EXIT intended for? ... >>a paragraph, how is one to reach an EXIT statement save through PERFORM ... ...
    (comp.lang.cobol)