forums.silverfrost.com

[Paul]

When can we expect FTN95 to be upgraded to the point where SALFLIBC.DLL is no longer required for normal .NET CLR applications?

[Andrew]

Internally this is now possible, as long as standard conforming Fortran 95 is used. There are however a couple of issues to be dealt with before it can be made public. We need to produce a new build of ftn95lib.dll (and associated .mdl files) that have no reliance on salflibc.dll (you will see that salflibc.dll is listed in the manifest of ftn95lib if you examine the assembly with ILDASM). This different build of ftn95lib then needs to be made available to the public.

The other issue is that of the personal edition. FTN95 uses a Win32 routine to display the personal banner, and there is no common cross-platform way of displaying another banner at present. There is an implementation of System.Windows.Forms in progress with mono but this is still in cvs and is not complete. The personal edition of the compiler is the same as the full edition of the compiler, with the exception of the banner and we need to keep a protection scheme in place. The full edition of FTN95 is therefore required, along with the modified build of ftn95lib, along with some compile time switches.

If the intention is to run the assemblies under mono then please see my reply in this thread:

http://forums.silverfrost.com/forums/forum.asp?forumid=1&page=0&select=185#xx185xx

We have successfully run FTN95 .NET assemblies under mono on Windows, but the same assemblies fail on the same version of mono under Linux (on the machines we tried). This may of course even be distribution specific.

If I have any more information about these issues I will post in the forums.