Re: EXIT SECTION/PARAGRAPH

Interesting ...
I just checked the MF 5.0 LRM and they mark EXIT FUNCTION/METHOD with an
ISO2002 bubble (and an MF bubble)

But they only mark EXIT PARAGRAPH/SECTION/CYCLE with MF bubbles.

This means that OFFICIALLY, they only claim it as an extension - not as a part
of their PARTIAL implementation of the '02 Standard.

My guess (only a guess) is that this is a DOX error and that they really do
conform (and think they conform) to the '02 Standard for this feature.

Although they do NOT claim full conformance to the entire '02 Standard, their
LRM does mark those individual features that they claim are implemented in
accordance to that Standard (that were not in the '85 Standard). See their
explanation of the ISO2002 bubble in the NOTATION section.

--
Bill Klein
wmklein <at> ix.netcom.com
"Rick Smith" <ricksmith@xxxxxxx> wrote in message
news:13eb33f2np62be7@xxxxxxxxxxxxxxxxxxxxx

"Robert" <no@xxxxxx> wrote in message
news:96uae3106tktv1aclfgel7fsg6j7lm0nsq@xxxxxxxxxx
On Fri, 7 Sep 2007 12:59:30 -0400, "Rick Smith" <ricksmith@xxxxxxx> wrote:
[snip]
EXIT PARAGRAPH in an unnamed paragraph
transfers control to the end of the paragraph, as
required by 2002, EXIT statement GR(11).

Micro Focus gives a fatal error:

procedure division.
if 1 = 2
exit paragraph
end-if
goback


3 exit paragraph
* 161-S**********************
**
** Can only be used within a Paragraph
cob: error(s) in compilationl

Does Micro Focus claim the compiler conforms to the
COBOL 2002 standard?

Or, are you assuming that EXIT PARAGRAPH as an
extension to the COBOL 1985 standard has the same
behavior as the COBOL 2002 standard?

Incidently, the relation "1 = 2" is a syntax error in both
the current and previous standards. At least one of the
items must be a variable! [This was discussed a year or
so ago, in conjunction with PERFORM UNTIL 1 = 0.]





.

Relevant Pages

  • Re: If you were inventing CoBOL...
    ... I can't get COBOL to produce a *floating* version of the most common ... EXIT PARAGRAPH and EXIT SECTION provide good support for structure ... disallowed in other contexts in the '02 standard. ... EXIT PARAGRAPH and EXIT SECTION are big helps here. ...
    (comp.lang.cobol)
  • Re: Is it possible to use the value of the PROGRAM ID within the source code?
    ... This was used by some compilers to generate null code that ... I can't recall a mandatory EXIT, even on the earliest IBM compilers. ... >paragraph without a statement until the '74 standard. ... During meetings to formulate a Programming Standard, ...
    (comp.lang.cobol)
  • Re: exit() values and the C standards?
    ... I've come across 2 differing definitions: ... that may be passed to exit() to indicate successful or ... "The C Standard defines the values 0, EXIT_SUCCESS, and ... If you're limiting the portability of your code to a particular operating system, then you can use other values that have specific meaning according to that operating system. ...
    (comp.lang.c)
  • Re: Infinite Loops and Explicit Exits
    ... they aren't planning to "replace NEXT SENTENCE" in the next standard; ... I note that EXIT, EXIT PROGRAM, EXIT METHOD, EXIT FUNCTION, EXIT SECTION and ... same contexts, with some utility. ... But what is the run-time utility of the EXIT SENTENCE as a separate ...
    (comp.lang.cobol)
  • Re: GL/ Casting News (spoiler)
    ... > "Well I don't want to burst your bubble, but I am certain they will ... > some sort of exit for them," ... > them to write an exit for them. ...
    (rec.arts.tv.soaps.cbs)