Re: Pointer usage danger?

The right thing to do, is to not DIM the ARRAY2 variable, since you don't know what the individual coming behind you might do.

But the answer to the question I think you asked, is that the mere setting of a pointer does not cause memory to be overlaid. Something must be done with a variable that's based on the pointer in order for that to happen.

Did I understand the question?

"M. Lazarus" <mlazarus@xxxxxxxx> wrote:

Given this code:

D Array1 DS Dim( 10 )
D Field1 2a
D Field2 75a

D Array2 DS Dim( %Elem( Array1 ))
D Based( Array1Ptr ) Inz( %Addr( Array1 ))
D Field1a Like( Field1 )
D Field2a Like( Field2 )

D Array1Ptr s *

/Free
Array1Ptr = %Addr( Array1( 10 )) ;
...

At this point, the first element of Array2 should be positioned
over the last element (#10) of Array1. Assuming I don't attempt to
access element 2 in Array2, is this safe to do or will the shift of
Array2, elements 2-10, overlay memory it shouldn't?

-mark

--
This is the RPG programming on the IBM i / System i (RPG400-L) mailing
list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.

--
Sent from my Galaxy tablet phone with with K-9 Mail. Please excuse my brevity.