Re: Strange Porting Problem CVF to IVF, requesting help and ideas.

Steve Lionel <steve.lionel@xxxxxxxxx> wrote:

Array bounds checking is good but doesn't help if you use (*)
dimensioned arrays. Argument type mismatches can also get you into
trouble - in Intel Fortran, add the options /gen_interface and
/warn:interface to help catch these.

The suggestion was that arrays in other COMMON blocks
were overwriting the desired variable. I don't believe (*)
is allowed in COMMON arrays.

But yes, if a COMMON array were passed as a subprogram
argument it could be referenced through a (*) dimension and
not be bounds checked.

-- glen
.

Relevant Pages

  • Re: DIM vs. Dynamic
    ... not matter if the equates are simply an include of a standard BP schema item ... dynamic arrays that got me thinking. ... 100,000 assignments were finished in the dynamic array case in only ... The difference between dynamic and dimensioned arrays ...
    (comp.databases.pick)
  • Re: Strange Porting Problem CVF to IVF, requesting help and ideas.
    ... On 2006-09-27 15:55:53 -0300, glen herrmannsfeldt said: ... dimensioned arrays. ... is allowed in COMMON arrays. ... They go to some trouble to make thier ...
    (comp.lang.fortran)
  • DIM vs. Dynamic
    ... The previous post on EQU had some discussion of dimensioned arrays vs. ... 100,000 assignments were finished in the dynamic array case in only ... process that runs *way** too long, I'm going with dynamic arrays only ...
    (comp.databases.pick)
  • Re: Arrays of Arrays is useful, a hallmark of OO, and missing in MVBASIC
    ... All in unidata. ... Agreed that storing multiple dynamic arrays in dimensioned arrays is a ... way to ameliorate the slow speed of dynamic arrays until it goes away ... memory on the fly (one time dimensioning of dimensioned arrays doesnt ...
    (comp.databases.pick)