Documents
Resources
Learning Center
Upload
Plans & pricing Sign in
Sign Out
Your Federal Quarterly Tax Payments are due April 15th Get Help Now >>

Further adjustments to arithmetic

VIEWS: 3 PAGES: 3

									June 14, 2005 2:31 PM                            Document Number:     J4/05-0141
                                                                                   Page      1 of 3

Subject:       Editorial/grammatical style issues

Author:        Charles C. Stevens

References in Document:

   1) ISO/IEC 1989:2002, Programming language COBOL 20xx -- Base Document for
      20xx standard (Nelson) (5/12/2005)

   2) J4/05-0125, Combined Editorial Changes to the 2002 Standard #1 (Nelson)

Previous version of document: None

Discussion:

During the discussion of Reference 2, a number of general style issues were raised and
discussed at Meeting #252.

In particular, three rules were constructed that need to be incorporated into the style
guide and applied.

       1) The hyphen may be omitted from terms like "culturally sensitive" when it is
          used in apposition to the noun being modified (" … comparison is culturally
          sensitive") but not when the term is immediately preceding the noun it
          modifies (" … a culturally-sensitive comparison"). The reason for this is that
          the adverb "culturally" directly modifies the adjective "sensitive" and no
          ambiguity is raised when the hyphen is omitted. Its presence in a string like
          this clarifies the hierarchy of the various terms ultimately modifying the noun.

       2) However, in cases like "implementor-defined" and "case-sensitive", the
          hyphen is required because the nouns "implementor" and "case" cannot
          modify the adjectives "defined" and "sensitive". It is necessary to identify
          these combined forms unambiguously as compound words forming
          adjectives, and that is correctly accomplished with the hyphen.

       3) When a term is specifically defined -- as for example "relation condition",
          hyphenation is not required.

Note that all instances of Rule 1 seem to be correctly followed in Reference 1.

A violation of Rule 3 on Page 98, 8.4.2.10.2, Predefined-address, at the end of Syntax
Rule 1, is corrected by 05-0133, Function pointers.

Recommended changes to Reference 1:

1) Page 25, 6.2.4, Continuation of lines, note following second paragraph: Replace
   "previous COBOL standards" with "the previous COBOL standard". Rationale: We
June 14, 2005 2:31 PM                           Document Number:      J4/05-0141
                                                                                   Page   2 of 3

   are only concerned here about differences with the immediately-preceding standard,
   not a greater part of the history of COBOL. (Reference 2 Item 1).

2) Page 43, 7.2.8.2, CALL-CONVENTION directive, general rule 2a: Change
   "implementor defined" to "implementor-defined". Rationale: style guide rule 2
   above.

3) Page 64, 7.2.16.2, LISTING directive, general rule 1: Change "implementor defined"
   to "implementor-defined". Rationale: style guide rule 2 above.

4) Page 68, 8.3.1.1.1, User-defined words, last paragraph on page, in the note:
   Change "case sensitive" to "case-sensitive". Rationale: style guide rule 2 above.
   (Reference 2 Item 3).

5) Page 142, 8.10, Context-sensitive words, last paragraph: Change "context sensitive"
   to "context-sensitive". Rationale: style guide rule 2 above. (Reference 2 Item 9).

6) Page 182, 9.3.14.2, Life cycle for instance objects, third paragraph, change
   "implementor defined" to "implementor-defined". Rationale: style guide rule 2
   above.

7) Page 337, 13.16.39.2, PICTURE clause, syntax rule 14, second paragraph: change
   "implementor defined" to "implementor-defined". Rationale: style guide rule 2 above.

8) Page 383, 13.16.59.3, USAGE clause, general rule 3: change "implementor defined"
   to "implementor-defined". Rationale: style guide rule 2 above.

9) Page 337, 13.16.39.2, PICTURE clause, syntax rule 17: change "implementor
   defined" to "implementor-defined". Rationale: style guide rule 2 above.

10) Page 447, 14.8.4.3, CALL statement, general rule 2, last paragraph, change
    "Procedure division structure." to "Procedure division structure, general rules."
    Rationale: current working draft reference is incomplete. (Reference 2 Item 14).

11) Page 666, 15.62.2, NUMVAL-C function, argument rule 3: Change "case
    insensitive" to "case-insensitive" and "case sensitive" to "case-sensitive". Rationale:
    style guide rule 2 above. (Reference 2 Item 20).

12) Page 667, 15.62.2, NUMVAL-C function, argument rule 6b1: Change "case
    insensitive" to "case-insensitive" and "case sensitive" to "case-sensitive". Rationale:
    style guide rule 2 above. (Reference 2 Item 21).

13) Page 683, 15.78.3, STANDARD-COMPARE function, note in returned value rule 5:
    Change "case sensitive" to "case-sensitive". Rationale: style guide rule 2 above.
    (Reference 2 Item 22).
June 14, 2005 2:31 PM                           Document Number:      J4/05-0141
                                                                                   Page   3 of 3

14) Page 691, 15.86.2, TEST-NUMVAL-C function, argument rule 3: Change "case
    insensitive" to "case-insensitive" and "case sensitive" to "case-sensitive". Rationale:
    style guide rule 2 above. (Reference 2 Item 23).

15) Page 753, D.4.3.2.2, Item attributes, first paragraph, last sentence: Change "case
    sensitive" to "case-sensitive". Rationale: style guide rule 2 above. (Reference 2
    Item 28).

16) Page 755, D.4.5.1.1.1, Names of programs, last paragraph, last sentence: Change
    "case sensitive" to "case-sensitive". Rationale: style guide rule 2 above.
    (Reference 2 Item 29).

17) Page 756, D.4.5.1.2.1, Names of functions, first paragraph, last sentence: Change
    "case sensitive" to "case-sensitive". Rationale: style guide rule 2 above.
    (Reference 2 item 30).

18) Page 830, D.24, CALL-CONVENTION directive, second paragraph, first sentence:
    Change "case sensitive" to "case-sensitive". Rationale: style guide rule 2 above.
    (Reference 2 item 33).

19) Page 830, D-24, CALL-CONVENTION directive, comments in example: Change
   from "case insensitive" to "case-insensitive" and from "case sensitive" to "case-
   sensitive".

								
To top