[mod.computers.vax] FORTRAN source conversion

blinn@renko.DEC.COM.UUCP (02/14/87)

In Message-ID: <1318@leadsv.UUCP> posted 11 Feb 87 17:14:01 GMT,
Gary Trimble (trimble@leadsv.UUCP) asks

> We are about to port a fairly large amount of VAX FORTRAN to a Sun
> Workstation. The developer's took advantage(?) of lots of DEC
> specific variances from vanilla FORTRAN. Questions:
>  
> 1) Does anyone in netland know of a conversion or profiling utility
> the checks for adherence to "pure" FORTRAN 77 (or FORTRAN IV)?
> Purchasing a software product that runs on the VAX (vms) or Sun
> is not out of the question.

The VAX Fortran compiler is willing to help you with this.  When you are
compiling the source, you can use the qualifier "/STANDARD=SYNTAX" to flag
all syntax extensions to the ANSI standard.  This won't help with semantic
extensions -- statements that work in a particular way on a VAX but in a
different way on another machine due to the way they are interpreted.

Specifying "/STANDARD" with no arguments is equivalent to specifying
	"/STANDARD=(SYNTAX,NOSOURCE_FORM)".  
(SOURCE_FORM flags statements that use tab formatting or contain lowercase
characters; I trust Sun's Fortran can handle this.)

If you use this in conjunction with the Language Sensitive Editor, it will
be easy to interactively review the areas of code that have used extensions.

For reasons that should be obvious, I'd prefer not to comment on either the
feasibility or desirability of moving your applications to a Sun platform. 

Regards,

Tom

Dr. Thomas P. Blinn
U. S. Volume Operations
Digital Equipment Corporation
Two Iron Way -- MRO3-3/R18
Marlboro, Mass. 01752-9003

Internet: blinn%furilo@decwrl.dec.com
Easynet:  FURILO::BLINN
Usenet:	  {decvax,ucbvax,allegra}!decwrl!furilo.dec.com!blinn
Voice:	  (617) 467-5562
Note:
  Opinions expressed herein are my own, and do not necessarily represent
  those of my employer or anyone else, living or dead, real or imagined.