Re: Problem With Cobol Report Writer

> Sure, with COBOL-85 a GOTO isn't necessary anymore at all, but I
> stick to the rule, and recommend it to everybody else. All other
> DIVISIONs, except the ultra-short IDENTIFICATION DIVISION are divided

> in SECTIONS, so the PROCEDURE DIVISION should follow the pattern.

It may well be that the PROCEDURE DIVISION should be divided up into
SECTIONs. In fact I used to do that for the purpose of using
'priorities' in order to overlay the program into the memory space
available to me.

But it doesn't follow, as you seem to claim, that these SECTIONs should
therefore be what the PERFORMs target. After all one doesn't INITIALISE
WORKING-STORAGE as a SECTION.

.

Relevant Pages

  • Re: VOTE
    ... On Tuesday 26 December 2006 15:10, Rick Stevens wrote: ... common way of coding the procedure division. ... There is actually a goto in many languages, including C, C++ and I ... minimize its use--true in almost any procedural language. ...
    (Fedora)
  • Re: VOTE
    ... common way of coding the procedure division. ... in fortran as well. ... There is actually a goto in many languages, including C, C++ and I ... Copyright 2006 by Maurice Eugene Heskett, ...
    (Fedora)
  • Re: VOTE
    ... common way of coding the procedure division. ... I think it's also used in fortran as well. ... think Java, but if you use goto in your C program, your colleagues are liable to break your arms and knee-caps, knock out your teeth and poke out your eyes with a corkscrew and actually get away with it on grounds of justifiable self defence. ...
    (Fedora)
  • Re: VOTE
    ... coding the procedure division. ... There is actually a goto in many languages, including C, C++ and I think Java, but if you use goto in your C program, your colleagues are liable to ... multi-level break statement. ... minimize its use--true in almost any procedural language. ...
    (Fedora)