Shouldn't be a problem as long as you aren't passing the arrays back and forth between the programs, then they would all need to be dimensioned the same. -Dianne
George Gallen wrote: >WOW. I just found an interesting "feature" of UV. > >You can MATREAD a record that has more fields than are dimensioned, > and you can MATWRITE that record back out INTACT without getting an error, > >It only bombs with an out of bounds error when you try to reference a >subscript > past the dimension. > >So....as long as any of those program dont try to mess with data it doesn't >know > about, we "should" be safe. > >George > > > >>-----Original Message----- >>[mailto:[EMAIL PROTECTED] Behalf Of George Gallen >> >>I'm modifying some programs that were written about 15-20 years ago, >>there must be 30 or 40 that >> interact with each other. >> >>Here is the problem. >>All the programs use dimensioned arrays, and they were dimensioned to >>exactly what was needed >>at the time, now I need to add 4 fields to one program. But I'm afraid >>if another program reads this >>newly created array, it will bomb out with an array out of bounds >>error. >> >>What is on my side, is all the programs that reference these files, all >>use the same variable name. >> >>My initial thought was to write a small program that will >> 1. open a program >> 2. search for a dimension of the suspect variable(s) >> 3. increase it's dimension level >> 4. write the program back out >> 5. recompile the program (I don't believe any are cataloged) >> >>Any other ideas? ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
