Boston Linux & Unix (BLU) Home | Calendar | Mail Lists | List Archives | Desktop SIG | Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings
Linux Cafe | Meeting Notes | Blog | Linux Links | Bling | About BLU

BLU Discuss list archive


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Discuss] FORTRAN -> ???



On 01/22/2012 02:14 PM, Jack Coats wrote:
> F2C would be my initial recommendation.
>
> Depends on which dialect of FORTRAN you are converting.
> Cut my teeth on FORTRAN IV, but also had some experience
> with FORTRAN II and FORTRAN 77, but mainly FORTRAN IV
I have been involved in many conversions in my past. Some of these were
COBOL to COBOL. I even had a system that had been written in COBOL by a
FORTRAN programmer which ended up as FORTRAN compiled by a COBOL
compiler. There are a number of issues you really need to take into
account.
First the conversion itself. As mentioned before F2C is reasonable and
you get the output in C, not C++.
Secondly testing to make sure the results are what you want
Third, and probably the most important is maintainability. What you will
get is essentially FORTRAN compiled in C. The first programming language
I learned was FORTRAN II. But, if the resulting code does not look like
C or C++ you still are going to have trouble maintaining the code.
So, my advice might be to start with F2C, but to do a rewrite.

-- 
Jerry Feldman <gaf at blu.org>
Boston Linux and Unix
PGP key id:3BC1EB90 
PGP Key fingerprint: 49E2 C52A FC5A A31F 8D66  C0AF 7CEA 30FC 3BC1 EB90





BLU is a member of BostonUserGroups
BLU is a member of BostonUserGroups
We also thank MIT for the use of their facilities.

Valid HTML 4.01! Valid CSS!



Boston Linux & Unix / webmaster@blu.org