4/3/2023 0 Comments Dfport.mod simply fortran![]() On the other hand, adding a USE DFPORT sentence in the subroutine works, but as I commented this is undesired.Ĭan we somehow "initialize" the system calls so that the Fortran code also works in the dll, while keeping compatibility with Unix?Īnother option would be to create two versions of a subroutine just containing the "getenv" call. ![]() However, calling the dll from the GUI causes an error and the GUI informs of a write attempt into protected memory. In Windows, both exe and dll build with no comments. Our dll's are called by a GUI writen with MS VS2008 Express -it could be migrated to VS2010 Professional if that would help. Windows dll (static) (Win32 / 圆4) - same source as above, except that the "main" program is not included in the project Basically, from the same source files we build: ![]() This sentence is not desired because our software is multiplatform, while DFPORT is -afaik- Windows-specific. However, we are facing a problem that we did not have with CVF: some of our subroutines callgetenv, and until now we were able of using these system calls with no USE DFPORT sentence but now, with IVF, this statement is needed. In our company we use a big number of critical programs written in pure Fortran 77, and we are nowadays successfully performing a transition from CVF to IVF (XE 2013) because of the transition to 圆4.ĩ9,9% of the times the source code remains compatible, and that is great news.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |