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


  • Subject: Re: Multiple occurance data structure
  • From: Dave Mahadevan <mahadevan@xxxxxxxx>
  • Date: Fri, 27 Jun 1997 17:46:39 -0400
  • Organization: Stoner and Associates

Scott:

Compiler listing is not enough.  Sometimes a compile fails after you
make a change and you assume it compiled ok.  So maybe, you had 10 to
start with, changed it to 25, program failed to compile for some other
reason and so is running the version with index 10.  My suggestion is to
get a clean compile and may be use STRISDB to look at the source.


Scott Cornell wrote: Problem - program blows up on an "index out of

> range error" for one of our client's whose
> database has 10 values to be loaded into MDEARN,
> e.g. the error occurs when INDX in the above
> snippet reaches 11.  I'm confused... since MDEARN
> is defined w/25 occurances, 11 shouldn't cause an
> index error, right?  Compile listing shows
> MDEARN(25) and yet, sure enough, in the program
> dump after the error, MDEARN says dimension(10)
> and only shows 10 spaces allocated to the
> structure.  What's up with this... did RPG III
> suddenly start allocating memory for data
> structures dynamically?
>


begin:          vcard
fn:             Dave Mahadevan
n:              Mahadevan;Dave
email;internet: mahadevan@fuse.net
note:           old address is mahade19@eos.net


x-mozilla-cpt:  ;0
x-mozilla-html: FALSE
end:            vcard


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.