forums.silverfrost.com

I have used COSD(Arg) and SIND(Arg) with Arg in Degrees with Intel compilers, but I guess these are extensions not supported by FTN95. They must be non-standard extensions.

Yes, of course, and thank you. Sorry for the silly question. I have been working with Intel Interoperative Systems, which I guess does the interfaces in the background for me.

I have many Fortran ...

I get the error:
"An unhandled exception of type 'System.InvalidProgramException' occurred in Ftn95.dll"
"Additional information: Common Language Runtime detected an invalid program. ...

Yes, it works reversing the indexes. thank you!

Fortran arrays are mapped to .NET arrays. The (column major) ordering is not changed because this transformation would be expensive for large arrays. Your code must allow for this difference. Thus the ...

I am sorry I misinterpreted your question.

It is really odd to ask for the dll to be in c:, but perhaps you can modify the path variable to point in the directory you have the dll. Would that solve ...

I'm working in Win32. The DLL is an "unmanaged" wrapper for a .NET project.

I don't use "!dec$ attributes dllimport::" (I can't see any help on it either?)

K

What do you ...

Silverfroft FTN, VS, and TFS interface bugs and Workaround(s)

1- If you retrieve a Solution (containing a FTN Project) from TFS, VS will not be able to get all the files if they are in folders. Ins ...

If you change the name of a file in a VS FTN project, the name will change in the Win folder but not on the .ftn95p project file, which will cause you untold amount of trouble. Do not!!! change file n ...

VS 2010 crashes if a Silverfrost/FTN Application Extension Project/ is referenced in more than one C# Class Library. Why? It shouldn't. I can reference a Intel Visual Fortran Dll project from multiple ...

My Q's are about Silverfrost implementation of the interface with VS 2010 and TFS.

If you delete a file in a FTN project, it does not get deleted in the Win folder and will create problems for you ...

.NET or win32 project? do you use !dec$ attributes dllimport:: ???

Also note that in the fortran project the Linker option Interface Only should be set to No, which is the default, but just in case.

I found a way of using fixed size arrays. I would not recommend it because involves the use of pointers, but it is possible.

Imagine you have this subroutine in fortran:

subroutine Example( ...

.NET will not pass/receive fixed size arrays, only assumed size arrays, so in your legacy code, change every declaration of array(number[,number]) to array(:[,:]) and you should be ok