× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  1.  Home
  2. RPG400-L
  3. March 2017

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.


As an Amazon Associate we earn from qualifying purchases.

This thread ...
Follow-Ups:
Replies:
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.