Re: [EXTERNAL] RE: File having an array using new free form

"RPG400-L" <rpg400-l-bounces@xxxxxxxxxxxx> wrote on 06/15/2018 12:13:12
PM:

Sorry, I don't understand what you mean by "the resulting I-specs are
not qualified". To me, having CHE.IMLFCMPTID in the I spec says that the

I spec _is_ qualified.

But I agree that it's tricky, and maybe not an ideal way to code any
more, now that we can just code the data structure on the I/O opcode
without relying on I specs at all.

Once upon a time, I would have agreed that simply having a period
in the variable name meant that it was qualified. But, now the compiler
requires that such coding also has to be associated with an explicitly
"qualified" data structure name -- no more assumptions. But if you look
at the generated I-spec you will see that there is no "qualified"
specification for the record format name which heads up the data structure
for the "default" input buffer.

Yes, I know you said that I-specs are not necessarily storage
definitions. But, in the absence of a separate data structure associated
with the I/O, the I-spec is certainly a storage definition and, in the
compiler listing, there is no difference shown for an I-spec definition
that does not represent storage vs. an I-spec definition that does.


Sincerely,

Dave Clark