× 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.



The only ways I know of to absolutely avoid this, are to (1) Avoid DIM() altogether, or (2) Define the index to a size that exceeds RPG's limitation for %ELEM. (I don't know if there is a limit (X) to DIM(X).)

Why don't I know this? 'Cuz I tend to favor linked lists and the like for new development of large arrays, so it's a value that I've not bothered investigating. But the price for avoiding arrays, is inability to use any of the related RPG goodies. (%LOOKUP comes to mind...)
++
Dennis
++


Bravely sent from my Galaxy tablet phone.
++


Dave <dfx1@xxxxxxxxxxxxxx> wrote:

Hi everyone,

A coworker got caught out by the For EndFor loop.

D wI S 3 0

For wI = 1 to %elem(arrayWith999Elements)

etc.
EndFor;

I said it was normal at the end that wI should be incremented to 1000,
thus making the program crash.

I wondered what the normal way would be to avoid this. I always use 5I
0 for my array index.
The coworker changed the DIM setting to 998!

As an Amazon Associate we earn from qualifying purchases.

This thread ...

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.