- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello,
I am an employee at a small engineering company in Oklahoma specializing in designing heaters. Our programs are written in Lahey Fortran and are currently being upgraded to Intel Fortran. They are primarily used to do intensivecalculationson heat transfer, pipe width, and other heater specifications. We are looking to move from fortran to either C#, C++, or VBA. I was curious as to the thoughts of the members of this board what the best direction would be to go. Can one of these languages utilizes fortran code or compile with an obj compiled by a fortran compiler?
Link Copied
2 Replies
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
What are your reasons for changing languages?
Are youwilling to introduce bugs just for the sake of a language change?
You can add a front-end GUI that is not Fotran and keep the bulk of the computation portion in Fortran.
If it ain't broke, don't break it.
Jim
Are youwilling to introduce bugs just for the sake of a language change?
You can add a front-end GUI that is not Fotran and keep the bulk of the computation portion in Fortran.
If it ain't broke, don't break it.
Jim
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I have just gone througha similar exercise - abandoning the old Lahey compiler and migrating to the Intel compiler.
Itested two different Fortran compilers, and the conversion from Lahey to Intel was fairly straightforward; I never succeeded with the "other" compiler, so it will remain nameless.
You will have to learn to get along without the old Ed editor - the Intel Visual Studioeditor is terrible in comparison.
In case you were using Winteracter, it migrates seamlessly, once you figure out how to link - follow the instructions. There will be some learning involved, but orders of magnitude less than if you try a conversion to one of the other languages you mention. You can link an .obj file compiled under fortran to a C or VBS program, but all you are doing is asking for trouble - check this forum and you will find many people with questions involving mixed language programming.
Why are you doing this? Let me guess - no one at your "small engineering company" has ever studied Fortran in school,and you have legacy code that none of thenewer employees knows how to maintain.
If that is the motivation, I suggest that you search the numerous newsgroups where discussions on the pros and cons of Fortran vs C programming and the wisdom of attemptingconversions of this sort,abound.
Itested two different Fortran compilers, and the conversion from Lahey to Intel was fairly straightforward; I never succeeded with the "other" compiler, so it will remain nameless.
You will have to learn to get along without the old Ed editor - the Intel Visual Studioeditor is terrible in comparison.
In case you were using Winteracter, it migrates seamlessly, once you figure out how to link - follow the instructions. There will be some learning involved, but orders of magnitude less than if you try a conversion to one of the other languages you mention. You can link an .obj file compiled under fortran to a C or VBS program, but all you are doing is asking for trouble - check this forum and you will find many people with questions involving mixed language programming.
Why are you doing this? Let me guess - no one at your "small engineering company" has ever studied Fortran in school,and you have legacy code that none of thenewer employees knows how to maintain.
If that is the motivation, I suggest that you search the numerous newsgroups where discussions on the pros and cons of Fortran vs C programming and the wisdom of attemptingconversions of this sort,abound.
Reply
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page