forums.silverfrost.com

For a few days now the results displayed in the Find Results 1 window are always partially obscured with the text of the string I searched for, rendered in blue. Makes it very difficult to see the res ...

Thanks for your comments.

Having found that my recent FTN95 Express install had made changes to PATH that resulted in use of an older version of both the compiler and library instead of the version ...

The re-install did not help but I restored use of the version 7.1 by removing an entry for the Express version from the PATH setting.

Now my app run OK in CHECK mode.

Thanks folks.

Looks like "What version..." might be an interesting question.

The licence I got was for version 7.1, which I downloaded and installed after using the free personal edition for some time. ...

The project is set for Release Win32 builds in Plato, which is where I do all FTN95 builds. I think that means I am avoiding .NET on the FORTRAN side. That is a requirement for the project.

This i ...

My project has grown in size and I now see this fatal run-time error reported when I try to debug a CheckMate Win32 build:

Salford run-time library.
Insufficient memory available for CHECK ...

The only "objects" being passed across the interface are:

integer (passed both ways)
double (passed both ways)
string (only passed from C# to FORTRAN)
vector of double (passed both way ...

Thanks for your comments Paul.

Please expand on your comment about memory not being locked. I am not (knowingly) using multi-threading. I have made sure that all modules that declare data at the ou ...

The open statement shown lives in some code which can be built into either a .exe or a DLL. The open behaves as expected when running the .exe and returns a iostat of 0 in normal circumstances (the f ...

I have a FORTRAN dll compiled with FTN95 as Debug Win32. This dll is called by code in a .NET C# wrapper which is itself called from a .NET C# EXE.

When the process is running, I want to be able to ...

I have put together the example below to illustrate FTN95 behaviour that surprised me. Look at the commented statement that assigns values to the dest array. FTN95 accepted this without warning and im ...