Re: Reviving REMARKS

Chuck Stevens wrote: 
Note also that the use of "*" in Column 7 to indicate that the source image
is a comment, according to ANSI X3.23-1974 page XIV-7, was *not* s standard
feature of COBOL in the '68 standard (although I believe it was a *very*
widely implemented extension even to implementations prior to '68).    The
only two *standard* mechanisms for introducing explanatory material prior to
the '74 standard were the REMARKS paragraph in the IDENTIFICATION DIVISION
and the NOTE statement in the PROCEDURE DIVISION.  The asterisk comment
convention was intended to replace them.

At what point did the NOTE end - was it a sentence-level statement, or was it a "until the next paragraph, everything is a comment" statement?


--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~   /   \  /         ~        Live from Montgomery, AL!       ~
~  /     \/       o  ~                                        ~
~ /      /\   -   |  ~          daniel@thebelowdomain         ~
~ _____ /  \      |  ~      http://www.djs-consulting.com     ~
~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~
~ GEEKCODE 3.12 GCS/IT d s-:+ a C++ L++ E--- W++ N++ o? K- w$ ~
~ !O M-- V PS+ PE++ Y? !PGP t+ 5? X+ R* tv b+ DI++ D+ G- e    ~
~ h---- r+++ z++++                                            ~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
.

Relevant Pages

  • Re: Reviving REMARKS
    ... "comment-entry" items in the Identification Division.) ... In an '85 Standard compiler (without an EXTENSION ignoring ... > REMARKS, when it existed in standard COBOL, was a "paragraph heading" in the ...
    (comp.lang.cobol)
  • Re: Fibonacci program
    ... I keep forgetting that EXIT PERFORM is not a COBOL-85 ... > Some of those are pretty common extensions to the '85 Standard - and ... >> IDENTIFICATION DIVISION. ... >> DISPLAY no2 ...
    (comp.lang.cobol)
  • Re: Method to force keeping of source
    ... It appears to me that your wish is that the COBOL standard should prevent ... environment for the compiler or in the execution environment. ... > implementor defined is one of the problems as I look at the situation as ...
    (comp.lang.cobol)
  • Re: Program templates as Object Classes
    ... Here's the problem with OO COBOL - it is still very incomplete.. ... realized that OO was incomplete without support ... It's about two years ago a former, retired M/F Manager, (not Bill Klein ... Micro Focus above - but he was referring to the fact that Standard ...
    (comp.lang.cobol)
  • Re: Program templates as Object Classes
    ... There are users of OO COBOL; they are just far fewer than either the vendors ... whether from the same vendor or not. ... disagreed with you that XML should be supported *first* by the OO features ... > being spent by J4 to provide these facilities through a standard that will ...
    (comp.lang.cobol)