[Next] [Previous] [Top]

Introduction

Introduction

Topics

• History.

• Fortran 90.

• Availability.

• References.

• Resources.

• The program.

• Coding conventions.

History

FORmula TRANslation

• 1954 Fortran I.

• 1958 Fortran II.

• 1958 Fortran IV.

• 1966 Fortran 66 standard.

• 1978 Fortran 77 standard.

• 1991 Fortran 90 standard.

Fortran 90

ANSI standard

• Superset of Fortran 77.
  • Obsolescent features.

• New features.

• Standard conformance.
  • Compilers must report non-standard and obsolescent code.

  • Standardises vendor extensions.

• Data parallel capability.
  • Array syntax make vector and parallel computing easier.

References

• Fortran 90 handbook

  J.C. Adams et. al., McGraw-Hill, 1992

• Programmer's Guide to Fortran 90

  W.S. Brainerd et. al., Unicomp, 1994

• Fortran 90

  M. Counihan, Pitman, 1991

• Fortran 90 programming

  T.M.R. Ellis et. al., Wesley, 1994

• Fortran 90 for Scientists and Engineers

  B.D. Hahn, Edward Arnold, 1994

• Fortran 90 Explained

  M. Metcalf and J. Ried, Oxford University Press, 1992

• Programming in Fortran 90

  J.S. Morgan and J.L. Schonfelder, Alfred Walker Ltd, 1993

• Programming in Fortran 90

  I.M. Smith, Wiley

Resources

• Fortran 90 FAQ.

• Fortran newsgroups.

• Tutorials, articles and information available via WWW.

• NAG Fortran 90 software repository.

The program

Examples

• A minimum program.

!does nothing

END PROGRAM nothing

• A program to print a message.

!displays a message

WRITE(*,*) `Hello World'

END PROGRAM hi

Compilation

• At the terminal:

Coding convention

Recommended by NAG and others

• Put all Fortran 90 keywords and intrinsic function names in upper case, everything else in lower case.

• Indent by 2 columns in the body of program units and INTERFACE blocks, DO-loops, IF-blocks, CASE-blocks, etc.

• Always include the name of a program, subroutine and function in its END statement.

• In USE statements, use the ONLY clause to document explicitly all entities which are actually accesses from that module.

• In CALL statements and function references, always use argument keywords for optional arguments.