Fortran (previously FORTRAN) is a general-purpose, procedural, imperative programming language that is especially suited to numeric computation and scientific computing. Originally developed by IBM in the 1950s for scientific and engineering applications, Fortran came to dominate this area of programming early on and has been in continual use for over half a century in computationally intensive areas such as numerical weather prediction, finite element analysis, computational fluid dynamics (CFD), computational physics, and computational chemistry. It is one of the most popular languages in the area of High-performance computing and programs to benchmark and rank the world's fastest supercomputers are written in Fortran.
Fortran (a blend word derived from The IBM Mathematical Formula Translating System) encompasses a lineage of versions, each of which evolved to add extensions to the language while usually retaining compatibility with previous versions. Successive versions have added support for processing of character-based data (FORTRAN 77), array programming, module-based programming and object-based programming (Fortran 90 / 95), and object-oriented and generic programming (Fortran 2003).
In late 1953, John W. Backus submitted a proposal to his superiors at IBM to develop a more efficient alternative to assembly language for programming their IBM 704 mainframe computer. Backus' historic FORTRAN team consisted of programmers Richard Goldberg, Sheldon F. Best, Harlan Herrick, Peter Sheridan, Roy Nutt, Robert Nelson, Irving Ziller, Lois Haibt and David Sayre.
A draft specification for The IBM Mathematical Formula Translating System was completed by mid-1954. The first manual for FORTRAN appeared in October 1956, with the first FORTRAN compiler delivered in April 1957. This was an optimizing compiler, because customers were reluctant to use a high-level programming language unless its compiler could generate code whose performance was comparable to that of hand-coded assembly language.
While the community was skeptical that this new method could possibly out-perform hand-coding, it reduced the amount of programming statements necessary to operate a machine by a factor of 20, and quickly gained acceptance. Said creator John Backus during a 1979 interview with Think, the IBM employee magazine, "Much of my work has come from being lazy. I didn't like writing programs, and so, when I was working on the IBM 701 (an early computer), writing programs for computing missile trajectories, I started work on a programming system to make it easier to write programs.
The language was widely adopted by scientists for writing numerically intensive programs, which encouraged compiler writers to produce compilers that could generate faster and more efficient code. The inclusion of a complex number data type in the language made Fortran especially suited to technical applications such as electrical engineering.
By 1960, versions of FORTRAN were available for the IBM 709, 650, 1620, and 7090 computers. Significantly, the increasing popularity of FORTRAN spurred competing computer manufacturers to provide FORTRAN compilers for their machines, so that by 1963 over 40 FORTRAN compilers existed. For these reasons, FORTRAN is considered to be the first widely used programming language supported across a variety of computer architectures.
The development of FORTRAN paralleled the early evolution of compiler technology; indeed many advances in the theory and design of compilers were specifically motivated by the need to generate efficient code for FORTRAN programs.
IFstatements for checking exceptions (
QUOTIENT OVERFLOW, and
DIVIDE CHECK); and
IFstatements for manipulating sense switches and sense lights
ASSIGN, and assigned
READ INPUT TAPE,
WRITE OUTPUT TAPE,
WRITE TAPE, and
FREQUENCYstatement (for providing optimization hints to the compiler)
Over the next few years, FORTRAN II would also add support for the
DOUBLE PRECISION and
COMPLEX data types.
C AREA OF A TRIANGLE WITH A STANDARD SQUARE ROOT FUNCTION C INPUT - CARD READER UNIT 5, INTEGER INPUT C OUTPUT - LINE PRINTER UNIT 6, REAL OUTPUT C INPUT ERROR DISPLAY ERROR OUTPUT CODE 1 IN JOB CONTROL LISTINGREAD INPUT TAPE 5, 501, IA, IB, IC501 FORMAT (3I5)C IA, IB, AND IC MAY NOT BE NEGATIVE C FURTHERMORE, THE SUM OF TWO SIDES OF A TRIANGLE C IS GREATER THAN THE THIRD SIDE, SO WE CHECK FOR THAT, TOOIF (IA) 777, 777, 701701 IF (IB) 777, 777, 702702 IF (IC) 777, 777, 703703 IF (IA+IB-IC) 777,777,704704 IF (IA+IC-IB) 777,777,705705 IF (IB+IC-IA) 777,777,799777 STOP 1C USING HERON'S FORMULA WE CALCULATE THE C AREA OF THE TRIANGLE799 S = FLOATF (IA + IB + IC) / 2.0AREA = SQRT(S * (S - FLOATF(IA)) * (S - FLOATF(IB)) *+ (S - FLOATF(IC)))WRITE OUTPUT TAPE 6, 601, IA, IB, IC, AREA601 FORMAT (4H A= ,I5,5H B= ,I5,5H C= ,I5,8H AREA= ,F10.2,+ 13H SQUARE UNITS)STOPEND
IBM also developed a FORTRAN III in 1958 that allowed for inline assembler code among other features; however, this version was never released as a product. Like the 704 FORTRAN and FORTRAN II, FORTRAN III included machine-dependent features that made code written in it unportable from machine to machine. Early versions of FORTRAN provided by other vendors suffered from the same disadvantage.
READ INPUT TAPE), while adding new features such as a
LOGICALdata type, logical Boolean expressions and the logical IF statement as an alternative to the arithmetic IF statement. FORTRAN IV was eventually released in 1962, first for the IBM 7030 ("Stretch") computer, followed by versions for the IBM 7090 and IBM 7094.
By 1965, Fortran IV was supposed to be the "standard" and in compliance with American Standards Association X3.4.3 FORTRAN Working Group.
BLOCK DATAprogram units
DATAstatement for specifying initial values
EXTERNAL(e.g., library) functions
GOTO, and computed
IFand arithmetic (three-way)
ENDFILEstatements for sequential I/O
FORMATstatements, and as actual arguments to procedures
END IFstatements, with optional
ELSE IFclauses, to provide improved language support for structured programming
INQUIREstatements for improved I/O capability
CHARACTERdata type, with vastly expanded facilities for character input and output and processing of character-based data
PARAMETERstatement for specifying constants
SAVEstatement for persistent local variables
LGE, LGT, LLE, LLT) for lexical comparison of strings, based upon the ASCII collating sequence.
In this revision of the standard, a number of features were removed or altered in a manner that might invalidate previously standard-conforming programs. (Removal was the only allowable alternative to X3J3 at that time, since the concept of "deprecation" was not yet available for ANSI standards.) While most of the 24 items in the conflict list (see Appendix A2 of X3.9-1978) addressed loopholes or pathological cases permitted by the previous standard but rarely used, a small number of specific capabilities were deliberately removed, such as:
An important practical extension to FORTRAN 77 was the release of MIL-STD-1753 in 1978. This specification, developed by the U. S. Department of Defense, standardized a number of features implemented by most FORTRAN 77 compilers but not included in the ANSI FORTRAN 77 standard. These features would eventually be incorporated into the Fortran 90 standard.
IMPLICIT NONEvariant of the
The IEEE 1003.9 POSIX Standard, released in 1991, provided a simple means for Fortran-77 programmers to issue POSIX system calls. Over 100 calls were defined in the document — allowing access to POSIX-compatible process control, signal handling, file system control, device control, procedure pointing, and stream I/O in a portable manner.
The development of a revised standard to succeed FORTRAN 77 would be repeatedly delayed as the standardization process struggled to keep up with rapid changes in computing and programming practice. In the meantime, as the "Standard FORTRAN" for nearly fifteen years, FORTRAN 77 would become the historically most important dialect.
Control Data Corporation computers had another version of FORTRAN 77, called Minnesota FORTRAN, with variations in output constructs, special uses of COMMONs and DATA statements, optimizations code levels for compiling, and detailed error listings, extensive warning messages, and debugs.
WHEREstatement for selective array assignment
ALLOCATABLEattribute and the
POINTERattribute, pointer assignment, and
NULLIFYstatement to facilitate the creation and manipulation of dynamic data structures
END DOstatement for loop termination, and
CYCLEstatements for "breaking out" of normal
DOloop iterations in an orderly way
SELECT. . .
CASEconstruct for multi-way selection
A small set of features were identified as "obsolescent" and expected to be removed in a future standard.
|Obsolescent feature||Example||Status / 95|
|Arithmetic IF-statement|| |
|Non-integer DO parameters or control variables|| ||Deleted|
| Shared DO-loop termination or |
termination with a statement
other than END DO or CONTINUE
| Branching to END IF |
from outside a block
|Alternate return|| |
|PAUSE statement|| ||Deleted|
| ASSIGN statement |
and assigned GO TO statement
|Assigned FORMAT specifiers|| ||Deleted|
|H edit descriptors|| ||Deleted|
|Computed GO TO statement|| ||(Obso.)|
|Statement functions|| ||(Obso.)|
| DATA statements |
among executable statements
|CHARACTER* form of CHARACTER declaration|| ||(Obso.)|
|Assumed character length functions|| |
|Fixed form source code|| * Column 1 contains * or ! or C for comments.|
C Column 6 for continuation.
WHEREconstructs to aid vectorization
A number of intrinsic functions were extended (for example a
dim argument was added to the
Several features noted in Fortran 90 to be deprecated were removed from Fortran 95:
An important supplement to Fortran 95 was the ISO technical report TR-15581: Enhanced Data Type Facilities, informally known as the Allocatable TR. This specification defined enhanced use of
ALLOCATABLE arrays, prior to the availability of fully Fortran 2003-compliant Fortran compilers. Such uses include
ALLOCATABLE arrays as derived type components, in procedure dummy argument lists, and as function return values. (
ALLOCATABLE arrays are preferable to
POINTER-based arrays because
ALLOCATABLE arrays are guaranteed by Fortran 95 to be deallocated automatically when they go out of scope, eliminating the possibility of memory leakage. In addition, aliasing is not an issue for optimization of array references, allowing compilers to generate faster code than in the case of pointers.)
Another important supplement to Fortran 95 was the ISO technical report TR-15580: Floating-point exception handling, informally known as the IEEE TR. This specification defined support for IEEE floating-point arithmetic and floating point exception handling.
which, together, comprise the multi-part International Standard (ISO/IEC 1539).
According to the standards developers, "the optional parts describe self-contained features which have been requested by a substantial body of users and/or implementors, but which are not deemed to be of sufficient generality for them to be required in all standard-conforming Fortran compilers." Nevertheless, if a standard-conforming Fortran does provide such options, then they "must be provided in accordance with the description of those facilities in the appropriate Part of the Standard."
From that article, the major enhancements for this revision include:
VOLATILEattribute, explicit type specification in array constructors and allocate statements, pointer enhancements, extended initialization expressions, and enhanced intrinsic procedures.
FLUSHstatement, regularization of keywords, and access to error messages.
An important supplement to Fortran 2003 was the ISO technical report TR-19767: Enhanced module facilities in Fortran. This report provided submodules, which make Fortran modules more similar to Modula-2 modules. They are similar to Ada private child subunits. This allows the specification and implementation of a module to be expressed in separate program units, which improves packaging of large libraries, allows preservation of trade secrets while publishing definitive interfaces, and prevents compilation cascades.
In August 2007, the BIT data type was removed. In February 2008, Coarrays were scaled back: Parallel I/O and teams were removed.
The complete original work plan is available at http://j3-fortran.org/doc/year/07/07-010.html.
Incompatible extensions were not the only portability problem. For numerical calculations, it is important to take account of the characteristics of the arithmetic. This was addressed by Fox et al. in the context of the 1966 standard by the PORT library. The ideas therein became widely used, and were eventually incorporated into the 1990 standard by way of intrinsic inquiry functions. The widespread (now almost universal) adoption of the IEEE 754 standard for binary floating-point arithmetic has essentially removed this problem.
Access to the computing environment (e.g. the program's command line, environment variables, textual explanation of error conditions) remained a problem until it was addressed by the 2003 standard.
Large collections of "library" software that could be described as being loosely-related to engineering and scientific calculations, such as graphics libraries, have been written in C, and therefore access to them presented a portability problem. This has been addressed by incorporation of C interoperability into the 2003 standard.
It is now possible (and relatively easy) to write an entirely portable program in Fortran, even without recourse to a preprocessor.
Object-Oriented Fortran was an object-oriented extension of Fortran, in which data items can be grouped into objects, which can be instantiated and executed in parallel. It was available for Sun, Iris, iPSC, and nCUBE, but is no longer supported.
Such machine-specific extensions have either disappeared over time or have had elements incorporated into the main standards; the major remaining extension is OpenMP, which is a cross-platform extension for shared memory programming. One new extension, CoArray Fortran, is intended to support parallel programming.
The FORTRAN system was designed for a more complex machine than the 650, and consequently some of the 32 statements found in the FORTRAN Programmer's Reference Manual are not acceptable to the FOR TRANSIT system. In addition, certain restrictions to the FORTRAN language have been added. However, none of these restrictions make a source program written for FOR TRANSIT incompatible with the FORTRAN system for the 704.
The permissible statements were:
FOR TRANSIT statements were limited to columns 7 thru 56, only. Punched cards were used for input and output on the IBM 650. Three passes were required to translate source code to the "IT" language, then to compile the IT statements into SOAP assembly language, and finally to produce the object program, which could then be loaded into the machine to run the program (using punched cards for data input, and outputting results onto punched cards.)
Two versions existed for the 650s with a 2000 word memory drum: FOR TRANSIT I (S) and FOR TRANSIT II, the latter for machines equipped with indexing registers and automatic floating point decimal (bi-quinary) arithmetic. Appendix A of the manual included wiring diagrams for the IBM 533 control panel.
The Fortran-95 Standard includes an optional Part 3 which defines an optional conditional compilation capability. This capability is often referred to as "CoCo".
Many Fortran compilers have integrated subsets of the C preprocessor into their systems.
SIMSCRIPT is an application specific Fortran preprocessor for modeling and simulating large discrete systems.
F (programming language) was designed to be a clean subset of Fortran 95 that attempted to remove the redundant, unstructured, and deprecated features of Fortran, such as the
EQUIVALENCE statement. F retains the array features added in Fortran 90, and removes control statements that were obsoleted by structured programming constructs added both Fortran 77 and Fortran 90. F is described by its creators as "a compiled, structured, array programming language especially well suited to education and scientific computing." F Programming Language Homepage). .
.forextension (for FORTRAN 66 or FORTRAN 77 fixed-form source, although the FORTRAN 66 dialect may have to be selected specifically with a command-line option) or
.f95extension (for Fortran 90/95 free-form source, respectively).
GO TO JAILwas encountered. The message is from a Chance card in Monopoly.
Among the "PRO" arguments was the assertion that this would also promote structured programming, by making it impossible to use the notorious
GO TO statement as before.
FORMAT statements would be eliminated, as well.)
The sole "CON" argument conceded that "this might invalidate some existing programs" but noted that most of these "probably were non-conforming, anyway".
* * * * * * * * * *
Open source compilers
Non-open source compilers
Integrated Development Environment