RE: SUBFILE FOR NON DISPLAY PROGRAMMING....

["Peter Dow" <pcdow@xxxxxxxxx>]

Excuse me John, but the end result of your example is the same as the automatic approach. How about an example that checks something external to determine whether increasing the array is reasonable or is caused by a data/programming error?

 

John Paris wrote:
> While I agree that a means to dynamically size arrays is useful - I disagree
> with the automatic approach.  I don't want an array that should never grow
> beyond 200 entries suddenly growing to 5,000 because of a data/programming
> error.  I would much rather have the ability to reset the top of the array when
> I need it to grow.  In fact I am happy enough to manage the memory myself (using
> ALLOC etc.) and simply be able to do something like this:

>  If        Count > %Elem(MyArray)
>  Eval      %Elem(MyArray) = %Elem(MyArray) + 20
>  Eval      Memory = %Elem(MyArray) * %Size(MyArray)
>  ReAlloc   Memory        MyArrayPtr
>  EndIf


+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---