RE: DIM question (Was MOVE/MOVEL and %Scan)

> From: Charlie Massoglia
>
> In V4R4 the following will not compile:
>
> D  array2                      S                      dim(%elem(array1))
> like(array1)
> D  array1                      S            7P  2  dim(12)
>
> Prior to V5R1, the argument of a built in function used on the
> DIM, OCCURS,
> OVERLAY, or PERRCD keywords in D-specs must have been previously
> defined in
> the source.  That is the first time we have had serial dependence of
> definition in RPG.  That restriction has been eliminated as of V5R1.

To be fair, though, Charlie, this is also the first time we have been able
to define expressions as arguments to those keywords.  The compiler folks in
effect added a preprocessor to allow these definitions.  The first
implementation was a single-pass preprocessor, which is quite a bit easier
to write than one that allows non-serial processing.  So, "eliminating the
restriction" was actually a neat bit of coding.

To my mind, my concern about the MOVE/MOVEL issue notwithstanding, the
additions to the RPG language have been nothing short of remarkable.  The
integration of the Java language is another area where the compiler writers
have shown an incredible ability to merge new technologies with legacy
constructs.  And perhaps that's why when I see something that really isn't
necessary that I get a little upset.  The RPG language has the ability to be
one of the premier binding languages between business applications and
middleware, and I hope the compiler team continues with their great work.  I
just hope it's not at the expense of the core ability of RPG, which is and
always will be business application design.

Joe