Re: newbie question on cobol syntax

In article <Ip4Xh.81928$OL2.22938@xxxxxxxxxxxxxxxxxxxxxx>,
William M. Klein <wmklein@xxxxxxxxxxxxxxxxx> wrote:
Actually,
If you have code that compiled with "FCOBOL" - or even with OS/VS COBOL and
you NOW are using the newer (IBM) compilers, then changing every NEXT SENTENCE
to CONTINUE should never change the logic flow.

The only time that there is a "difference in logic flow" is when you MIX old
COBOL (with NEXT SENTENCE) *with* scope terminators (END-IF or whatever).

Bingo, Mr Klein... code that has been around that long has, in my
experience, been through a few hands of vary levels of capability; styles
are mixed and stability, at times, a wee bit... precarious.

Therefore, if you are worried about "base of code" BUT are using newer
compiler,
then feel "safe" in changing NEXT SENTENCE to CONTINUE.

I've felt safe about things which the Testing Crew grew a bit... upset
about. Increasing the number of code changes, or so I have seen,
increases the size of the Test Plan and the amount of time folks spend
dealing with it.

DD
.

Relevant Pages

  • Re: why the usage of gets() is dangerous.
    ... "Paul Hsieh" wrote in message ... warning that it is dangerous to use gets. ... basically all C compilers implement getsto have ... It is possible, though rather difficult, to implement a safe gets, that is to say one that always terminates the program with an error message if the buffer is exceeded. ...
    (comp.lang.c)
  • Re: newbie question on cobol syntax
    ... you NOW are using the newer (IBM) compilers, ... The only time that there is a "difference in logic flow" is when you MIX old ... but I've run across a bit of the 'installed base' that requires NEXT ...
    (comp.lang.cobol)
  • Re: Thou shalt have no other gods before the ANSI C standard
    ... On Sat, 26 Feb 2005 22:14:34 GMT, Randy Howard ... > I am not sure it is always safe, for example if the length of the ... If you do know of compilers that do it, ... > you have access to them to try some sample code on them? ...
    (sci.crypt)
  • Re: mv quasi-quotation
    ... Hmm, and I had just recommended using,. ... Or are compilers ... generally smart enough to recognize that reusing the list from ... multiple-value-list is safe in this context? ...
    (comp.lang.lisp)
  • Re: Thou shalt have no other gods before the ANSI C standard
    ... Randy Howard wrote: ... > I am not sure it is always safe, ... those compilers. ... string length, which is much simpler to optimize. ...
    (sci.crypt)