Re: Weird behavior with dynamically sized arrays

To be clear, I absolutely intend to abide by the boundaries of the
allocation. I exceeded this in the test because the dump indicated there
were over 200 elements in the array. I am mostly interested as to why I am
unable to get the contents of the array listed in the dump.

WRT your "clobbered" reference, do I presume correctly that the memory
clobbered will only affect the job (activation group?) that the program
runs in?

- Dan

On Wed, Mar 8, 2017 at 2:05 AM, Peter Dow <petercdow@xxxxxxxxx> wrote:

Hi Dan,

Interesting. You allocated space for 16 elements, then proceed to populate
101 elements. There's no error because you told RPG there are 50,000
elements. Having blasted past the space you allocated, who knows what got
clobbered?

Keep track of the number of elements allocated, and don't exceed that when
populating elements of the array.