VAX VMS Fortran to Fortran 77
in [Fortran]
|
Prev: subroutine reference
Next: gfortran
From: rfengineer55 on 9 Jun 2010 11:15 I'm Compiling some Fortran source from the FCC using a couple compilers. One is Gfortran, the other is Microsoft Fortran 5.1 and I'm running into some compile errors due to som dialect differences between the VA VMS aqnd Fortran 77. I have Googled until my fingers a sore from typing, and I have not found a good resource that comprehensively spells out the dialect differences. Anyone in the group here know of such a source? Anyone here have experience with going from VAX VMS fortran to Fortran 77? Thanks Jeff Chief Engineer Northern Illinois University
From: mecej4 on 9 Jun 2010 11:20 On 6/9/2010 10:15 AM, rfengineer55 wrote: > I'm Compiling some Fortran source from the FCC using a couple > compilers. One is Gfortran, the other is Microsoft Fortran 5.1 and I'm > running into some compile errors due to som dialect differences > between the VA VMS aqnd Fortran 77. > > I have Googled until my fingers a sore from typing, and I have not > found a good resource that comprehensively spells out the dialect > differences. Anyone in the group here know of such a source? Anyone > here have experience with going from VAX VMS fortran to Fortran 77? > > Thanks > > Jeff > Chief Engineer > Northern Illinois University Microsoft Fortran also had some non-standard extensions. Please post the sections of the code that generate systax errors. Intel Fortran has a /vms switch to make it accept VMS I/O statement extensions. Many current Fortran compilers come with VAX compatibility libraries. -- mecej4
From: Lynn McGuire on 9 Jun 2010 11:26 > I'm Compiling some Fortran source from the FCC using a couple > compilers. One is Gfortran, the other is Microsoft Fortran 5.1 and I'm > running into some compile errors due to som dialect differences > between the VA VMS aqnd Fortran 77. > > I have Googled until my fingers a sore from typing, and I have not > found a good resource that comprehensively spells out the dialect > differences. Anyone in the group here know of such a source? Anyone > here have experience with going from VAX VMS fortran to Fortran 77? You dont say what your new platform is. If Windows XP (or newer), then the free Open Watcom ( http://openwatcom.org/ ) F77 compiler is very good about Vax VMS upward compatibility. Lynn
From: Ken Fairfield on 9 Jun 2010 11:38 On Jun 9, 8:15 am, rfengineer55 <rfenginee...(a)aol.com> wrote: > I'm Compiling some Fortran source from the FCC using a couple > compilers. One is Gfortran, the other is Microsoft Fortran 5.1 and I'm > running into some compile errors due to som dialect differences > between the VA VMS aqnd Fortran 77. > > I have Googled until my fingers a sore from typing, and I have not > found a good resource that comprehensively spells out the dialect > differences. Anyone in the group here know of such a source? Anyone > here have experience with going from VAX VMS fortran to Fortran 77? In addition to what mecej4 and Lynn McGuire said, some of us here have extensive experience with VMS Fortran extensions. But you'll need to post specific code samples w/error messages for us to have a chance at suggesting work-arounds. While gfortran is a good choice, I'd stay far away from any version of Microsoft Fortran... Versions of Intel Fortran have a heritage of DEC (i.e., VMS) Fortran engineers and will likely support many of the extensions you're bumping into... -Ken
From: glen herrmannsfeldt on 9 Jun 2010 13:52
rfengineer55 <rfengineer55(a)aol.com> wrote: > I'm Compiling some Fortran source from the FCC using a couple > compilers. One is Gfortran, the other is Microsoft Fortran 5.1 and I'm > running into some compile errors due to som dialect differences > between the VA VMS aqnd Fortran 77. > I have Googled until my fingers a sore from typing, and I have not > found a good resource that comprehensively spells out the dialect > differences. Anyone in the group here know of such a source? Anyone > here have experience with going from VAX VMS fortran to Fortran 77? In many manuals, DEC would use a different ink color for extensions to the language. If you are using a scanned version of the manual, then that distinction may have been lost. Without knowing the specific features you are using, it is hard to say more. -- glen |