Re: SAME AS ('02 Standard) Clause - and circulatiy



Rick,
Once again, you can submit an interpretation request IF YOU WANT TO, but my
impression is that you think the standard does (or should) tell implementers in
what order to do things. Other than the "text manipulation" and "compilation"
stages, this is simply NOT true. The Standard tells them what to do and it is
up to them to figure out HOW. If you changed your example to:

1 C SAME AS A2 OF B.
1 B.
2 B1 PIC X.
2 B2.
COPY A.

with a COPY member of A that read
3 A1 PIC X.
3 A2 PIC X.

I think you would agree that an implementer could (and would) be able to resolve
it. Therefore, as the SRs and GRs ALLOW for your original source code, it is up
to the implementer to figure out how (even if it requires multiple passes) to do
it.

--
Bill Klein
wmklein <at> ix.netcom.com
"Rick Smith" <ricksmith@xxxxxxx> wrote in message
news:13ddluk7ihjpmc2@xxxxxxxxxxxxxxxxxxxxx
In the game "Break the Standard", I came up with one
that appears to have anomalous behavior

1 C SAME AS A2 OF B.
1 B.
2 B1 PIC X.
2 B2 TYPE TO A.
1 A IS TYPEDEF.
2 A1 PIC X.
2 A2 PIC X.

SAME AS SR(1) permits qualified names; SR(7) permits
reference to an elementary item; and GR(1) covers
expansion using A2 OF B. However A2 OF B can not
be known until B2 of B is expanded and I find no
general rule requiring the expansion of B2 OF B to reveal
A2; nor any syntax rule limiting [SAME AS] data-name-1
to what is explicitly defined in source code.

Reverse the order of the level-number 1 items and expansion
of B2 OF B makes A2 OF B known before the expansion
of C.

In other words, as written, it appears to be a syntax error;
reversed, there appears to be no error.





.



Relevant Pages

  • Re: hubbles constantly expanding universe
    ... > So even without gravity, your body, the earth and moon, etc. would all ... Of course without gravity the ... > world such expansion of the universe would be unobservable. ... You cited platinum for a length standard (just as a "for instance" I'm ...
    (sci.physics.relativity)
  • Re: CONSTANT ENTRY (was "forward" references (was: COBOL subscript range checking))
    ... level of complexity to COBOL compiler development ... when we get away from these references in the "text manipulation ... I think it is clear that the '02 Standard *does* ... place such a requirement on the implementer - and as far as I can tell ...
    (comp.lang.cobol)
  • Re: topology of Lispers
    ... To mee it looks more like COBOL. ... do (decf cat-count) ... Anyhow the original implementation did have mechanisms for expansion, but they were not included in the CL standard. ...
    (comp.lang.lisp)
  • Re: A word similar to CREATE, but decoupled from the input stream
    ... I did use the phrase "lower level primitive" which might have ... inseparable and detrimental to allowing a slightly more general form of ... an existing word as a standard. ...
    (comp.lang.forth)
  • Re: CONSTANT ENTRY (was "forward" references (was: COBOL subscript range checking))
    ... level of complexity to COBOL compiler development ... when we get away from these references in the "text manipulation stage" - ... this requirement is placed on the implementer. ... As someone who both helped develop the '02 Standard and eventually expressed my ...
    (comp.lang.cobol)