JiscMail Logo
Email discussion lists for the UK Education and Research communities

Help for COMP-FORTRAN-90 Archives


COMP-FORTRAN-90 Archives

COMP-FORTRAN-90 Archives


COMP-FORTRAN-90@JISCMAIL.AC.UK


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

COMP-FORTRAN-90 Home

COMP-FORTRAN-90 Home

COMP-FORTRAN-90  1998

COMP-FORTRAN-90 1998

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

making F90 code Elf90/F compatible

From:

[log in to unmask]

Reply-To:

[log in to unmask]

Date:

Tue, 21 Jul 1998 01:37:24 EDT

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (138 lines)

I find the Elf90 (www.lahey.com) and F (www.imagine1.com/imagine1)
subset Fortran 90 compilers to be useful supplements to a full 
Fortran 90 compiler (in my case Digital Visual Fortran) . I think they 
meet the creators'  stated goal of preserving the power of Fortran while
eliminating redundancies. The Elf90 features of (1) disallowing unreferenced 
variables, variables used before set, and variables set but never later used
and (2) the tracing of execution errors to a specific line in the code 
are very valuable. 

An obvious problem one has in writing Essential Fortran 90 (Loren Meissner's
term for Elf90 + F) programs is that the vast majority of code in the public 
domain and in commercial libraries such as IMSL is unavailable.
Michael Metcalf has written a program to make some F77 to F90 conversions, 
and Alan Miller has done this as well as write a program to make some
F90 -> Elf90 conversions. There are many other transformations to be done to 
get an F program. 

Below is an incomplete list of changes that need to be made to a free source 
form F90 program to make it an Elf90/F compatible -- (mi) means that Miller's
code makes the transformation, and (met) is for Metcalf's program. Any
programs
to implement some of the other transformations from F90 to Elf90/F would 
be much appreciated. 

Vivek Rao 

******************************************************************************
**************
INCOMPLETE LIST OF CHANGES TO MAKE TO F90 CODE TO GET F/ELF90 CODE

Note that almost all changes required by Elf90 are required by F, but not
vice-versa. 

<GENERAL RULES>	
Use only the generic form of intrinsic functions. 

Do not use semicolons to start a new statement. 
Place each statement on a separate line.

replace a 'data' statements with regular
assignment statements 

replace 
'real x ; parameter x = 5.0'
with
'real, parameter :: x = 5.0'

(mi) replace 'endif' with 'end if' , 'elseif' with 'else if' , 'enddo' with
'end do'

replace the 'where' statement with a where construct 

replace single quotes with double quotes to 
enclose strings 

do not use keywords as variable names ; for example, 
replace 'real, parameter :: tiny = 1.0e-6' with 
'real, parameter :: tiny_real = 1.0e-6' 

replace 'print*,' with 'write (unit=*,fmt=*)'

replace 'open (1,file_name)' with 'open (unit=1,file=file_name,status="read
write",action="replace")'

replace one-line if statements with if-then-end if structures 

convert all keywords to lower case 

replace 'stop "program is stopping"' with 
'write (unit=*,fmt=*) "program is stopping" ; stop'

replace tabs with spaces 

(mi,met) get rid of labeled statements ; replace do-continue with do - end do 

(mi) replace '.lt. .le. .eq. .ge. .gt.' with '< <= == >= >' respectively 

<DECLARATIONS IN MAIN PROGRAM AND PROCEDURES>

(mi) replace 'character*5' with 'character (len=5)' 

use double colons in all declaration statements 

replace 'pause' statements with 'stop' or by prompting for input 

<MODULES>

declare all module procedures 'public' or 'private'

if a module 'A' USEs another module, place a 'private' statement in module A

place the 'implicit none' statement after any use statements 
in the beginning of a module, and remove 'implicit none' statements
from module procedures

<PROCEDURES>

place a 'return' statement just before the end of each procedure

replace statements such as 'real, allocatable :: x(:),y(:,:)' with 
'real, dimension(:),  allocatable :: x ; real, dimension(:,:), allocatable ::
y'

replace statements such as 'real :: x(n),y(n,n)' with 
'real, dimension(n)  :: x ; real, dimension(n,n) :: y'

do not call subroutines from functions

replace 'intent(inout)' with 'intent(in out)' 

in a subroutine, all arguments must have specified intent
 
in a function, all arguments must have specified intent(in) 

in a subroutine, first declare all intent(in) arguments, then all intent(out)
arguments, 
then local variables

always use a result statement for functions -- replace 
'function func(x)' with 'function func(x) result(value)'

in a function, first declare all intent(in) arguments, then the function
result, then
local variables 

in a procedure, put all optional arguments at the end of the argument list

replace 'common' statement with a module

(mi,met) replace 'end' with 'end program program_name' , and do an analogous
replacement
for subroutines and functions  

(mi) replace 'go to' with a cycle or exit statement where possible 


%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

Top of Message | Previous Page | Permalink

JiscMail Tools


RSS Feeds and Sharing


Advanced Options


Archives

December 2023
February 2023
November 2022
September 2022
February 2022
January 2022
June 2021
November 2020
September 2020
June 2020
May 2020
April 2020
December 2019
October 2019
September 2019
March 2019
February 2019
January 2019
November 2018
October 2018
September 2018
August 2018
July 2018
May 2018
April 2018
March 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
December 2015
November 2015
October 2015
September 2015
August 2015
June 2015
April 2015
March 2015
January 2015
December 2014
November 2014
October 2014
August 2014
July 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
July 2013
June 2013
May 2013
April 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
August 2010
July 2010
June 2010
March 2010
February 2010
January 2010
December 2009
October 2009
August 2009
July 2009
June 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
January 2007
2006
2005
2004
2003
2002
2001
2000
1999
1998
1997


JiscMail is a Jisc service.

View our service policies at https://www.jiscmail.ac.uk/policyandsecurity/ and Jisc's privacy policy at https://www.jisc.ac.uk/website/privacy-notice

For help and support help@jisc.ac.uk

Secured by F-Secure Anti-Virus CataList Email List Search Powered by the LISTSERV Email List Manager