Re: Question regarding uniqueness



You can ignore my last post (which was a different change). The change that
relates to this is in the '02 Standard, page 827 which states,

"67) Implicit qualification of data-names within the same group. Data-names
referenced in a data description entry need not be qualified when they are
defined in the same group as the subject of the entry, unless qualifiers are
needed to establish uniqueness within that group."

--
Bill Klein
wmklein <at> ix.netcom.com
"Roger While" <simrw@xxxxxxxxxxxx> wrote in message
news:f8cm2c$vpa$00$1@xxxxxxxxxxxxxxxxxxxx
IDENTIFICATION DIVISION.
PROGRAM-ID. t11.
DATA DIVISION.
WORKING-STORAGE SECTION.

01 K525-AII-DRVR-RSTRT-DATA.
03 VARIABLE1 PIC X(8) VALUE SPACES.
03 K525-FRMT-FILE-ARRAY.
06 K525-FRMT-FILE-ARRAY-ROW
OCCURS 6 TIMES
ASCENDING KEY IS VARIABLE1.
09 VARIABLE1 PIC X(8) VALUE SPACES.
09 OTHER-DATA-ITEM PIC S9(5).
PROCEDURE DIVISION.
GOBACK.

This compiles with big iron and MF.
Why?
Of course, this is a stupid definition.
Any attempt in the PROC div to reference any field
would lead to a compile failure.
OC throws this out at compile time.





.



Relevant Pages

  • Re: Infinite Loops and Explicit Exits
    ... But explicit qualification is often not necessary. ... >>pollution, you don't understand namesapces. ... > reported at compile time. ... It would not have been reported at compile time at all. ...
    (comp.lang.cobol)
  • Re: creaping coupling......
    ... In C++ it would be trivial to break that source code dependency, ... When you compile a .java module, ... In Java and C# it's asserted at compile time. ...
    (comp.object)
  • Re: VB Compiler Warnings & other woes ...
    ... you will get this warning in vs 2005. ... > have a direct legacy language path of evolution to consider. ... >> compile time errors rather than runtime. ...
    (microsoft.public.dotnet.languages.vb)
  • Re: No exceptions?
    ... time that was removed before runtime; there's no way to generate a compile time exception for the unexceptionable, but there are not many ways of avoiding a runtime exception if the compile time y had defined attributes. ... Thus, as soon as one compiles a statement that references any such resource, one would get a compile-time error. ... I think many products go to elaborate lengths and introduce arbitrary concepts to handle such cases, at least some of them try to prevent catalogue updates in a transaction (Jim Gray described a logical '2-phase' protocol for intension locks many years ago and I've seen it implemented and I've seen the complications that seem never to end due to the intricacy, for example a reversal of Jonathan's converse problem, a sequential transaction that references y and then deletes y's definition - what should happen if the reference is then referred to again? ...
    (comp.databases.theory)
  • Re: float to pointer coercion (cost 13)
    ... Do you compile two versions of the ... but it is given two entry ... but to the immediate-args entry point. ... ((DOUBLE-FLOAT DOUBLE-FLOAT) ...
    (comp.lang.lisp)