forums.silverfrost.com

Hi Paul,
I believe so - I copied everything from the FTN95, DLL, and Plato links into the directory where I have FTN95 installed.

I have just loaded the various new DLLs and lib files for version 9.04. After recompiling my application, the program hangs at start up. It's about 160,000 lines of code, and I do not have the time to ...

Hi Paul,
The following example does not quite reproduce the error I have in mind, but it is outputting a surplus value (which is presumably because the size of ia in subroutine s is still in error): ...

Hi Paul,
Any progress on this one? I have work-arounds, but I have quite a few instances that I think are equivalent, where I am passing an array of a derived type, and the routine does not get what ...

The following program should allocate the logical array and assign all values to .false., but in FTN95 the array is not allocated.

Program p
Logical, Dimension(:), Allocatable : ...

Where do these Mod files generally belong? I could not see them in any of the C:\Program Files (x86)\Silverfrost\FTN95 directories.

That is my understanding of AOA too. In my example, AOA should not be taking place, because b was already allocated. My assumption (which may be incorrect) was that because b's shape changed, some for ...

Hi Paul,

MANY thanks for your diligent work on this problem. Let me try the compiler switches and see what that effect is. If AOA has to be switched off, I can deal with that more easily than with ...

Understood Paul. Thanks for looking into this. I am loading a and b into the separate subprograms because typically the module contains a large number of subprograms, and I am looking to make availabl ...

Thanks Paul. I'm relieved you were able to isolate the bug. It has taken a great deal of work to locate the problem and then produce the small example.

Are you able to be more generic about what w ...

Here is an attempt to isolate the problem with the shape of an array being reassigned.
Module m1
Implicit None
Real, Dimension(:,:), Allocatable, Public :: b
Re ...

That would be interesting - if b were already allocated but got resized at the "not sure what happens here" line, that could result in some very difficult to track problems.

Many thanks to everyone's inputs. It has been helpful to know not to expect shape to "work" (if that is the correct word) when its argument is deallocated.

I don't know whether this is a ...

Indeed, I have tried CHECKMATE. But forgetting about the larger programme for now, is Shape not returning an incorrect result even in the simple example? Size also returns 2 after i is deallocated.

Hi Paul,

I seem to get the same output ("2 F") regardless of which compiler options I use.