Software Development Resources
Create account | Log in | Log in with OpenID | Help


From DocForge

Fortran (previously FORTRAN[1]) is a general-purpose[2], procedural,[3] 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 climate modeling, computational fluid dynamics (CFD), computational physics, financial computing, and computational chemistry.

Fortran (a portmanteau derived from The IBM Mathematical Formula Translating System) encompasses a lineage of versions, each of which evolved to add extensions to the language while 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).


[edit] History

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. 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.

[edit] FORTRAN

The initial release of FORTRAN for the IBM 704 contained 32 statements, including:

  • DIMENSION and EQUIVALENCE statements
  • Assignment statements
  • Three-way arithmetic IF statement. [4]
  • IF statements for checking exceptions (ACCUMULATOR OVERFLOW, QUOTIENT OVERFLOW, and DIVIDE CHECK); and IF statements for manipulating sense switches and sense lights
  • GOTO, computed GOTO, ASSIGN, and assigned GOTO
  • DO loops
  • FREQUENCY statement (for providing optimization hints to the compiler) [5]


IBM's FORTRAN II appeared in 1958. The main enhancement was to support procedural programming by allowing user-written subroutines and functions. Six new statements were introduced:


Over the next few years, FORTRAN II would also add support for the DOUBLE PRECISION and COMPLEX data types.

[edit] Simple Fortran II program

This program has one data card input, with simple zero-data edit check. If one of the input values is zero, then the program will end with an error code of "STOP 1" in the job control card listing following the execution of the program. Normal output will be one line printed with A, B, C, and AREA on the "report" page following the compilation with no specific units are stated; and with a normal "STOP" in the job card listing.

      READ(5,501) A,B,C
  501 FORMAT(3I5)
      IF(A.EQ.0 .OR. B.EQ.0 .OR. C.EQ.0) STOP 1
      S = (A + B + C) / 2.0
      AREA = SQRT( S * (S - A) * (S - B) * (S - C) / 2.0)
      WRITE(6,601) A,B,C,AREA
  601 FORMAT(4H A= ,I5,5H  B= ,I5,5H  C= ,I5,8H  AREA= ,F10.2,12HSQUARE UNITS)


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.


Starting in 1961, as a result of customer demands, IBM began development of a FORTRAN IV that removed the machine-dependent features of FORTRAN II (such as READ INPUT TAPE), while adding new features such as a LOGICAL data 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.[6]

"Invalid settings file in fdeolr\where\the\file\is\located.rmskin".Could someone please help me with this so i can change my win$hit look to something more better? :)Thanks allready :)

[edit] FORTRAN 77

After the release of the FORTRAN 66 standard, compiler vendors introduced a number of extensions to "Standard Fortran", prompting ANSI in 1969 to begin work on revising the 1966 standard. Final drafts of this revised standard circulated in 1977, leading to formal approval of the new FORTRAN standard in April 1978. The new standard, known as FORTRAN 77, added a number of significant features to address many of the shortcomings of FORTRAN 66:

  • Block IF and END IF statements, with optional ELSE and ELSE IF clauses, to provide improved language support for structured programming
  • DO loop extensions, including parameter expressions, negative increments, and zero trip counts
  • OPEN, CLOSE, and INQUIRE statements for improved I/O capability
  • Direct-access file I/O
  • IMPLICIT statement
  • CHARACTER data type, with vastly expanded facilities for character input and output and processing of character-based data
  • PARAMETER statement for specifying constants
  • SAVE statement for persistent local variables
  • Generic names for intrinsic functions
  • A set of intrinsics (LGE, LGT, LLE, LLT) for lexical comparison of strings, based upon the ASCII collating sequence.
(ASCII functions were demanded by the U. S. Department of Defense, in their conditional approval vote.)

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:

  • Hollerith constants and Hollerith data, such as:
  • Reading into a H edit (Hollerith field) descriptor in a FORMAT specification.
  • Overindexing of array bounds by subscripts.
Y= A(11,1)
  • Transfer of control into the range of a DO loop (also known as "Extended Range").

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.

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 verison 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.[7]

[edit] Fortran 90

The much delayed successor to FORTRAN 77, informally known as Fortran 90, was finally released as an ANSI Standard in 1992. This major revision added many new features to reflect the significant changes in programming practice that had evolved since the 1978 standard:

  • Free-form source input, also with lowercase Fortran keywords
  • Identifiers up to 31 characters in length
  • Inline comments
  • Ability to operate on arrays (or array sections) as a whole, thus greatly simplifying math and engineering computations.
    • whole, partial and masked array assignment statements and array expressions, such as   X(1:N)=R(1:N)*COS(A(1:N)))
    • WHERE statement for selective array assignment)
    • array-valued constants and expressions,
    • user-defined array-valued functions and array constructors.
  • RECURSIVE procedures
  • Modules, to group related procedures and data together, and make them available to other program units, including the capability to limit the accessibility to only specific parts of the module.
  • A vastly improved argument-passing mechanism, allowing interfaces to be checked at compile time
  • User-written interfaces for generic procedures
  • Operator overloading
  • Derived/abstract data types
  • New data type declaration syntax, to specify the data type and other attributes of variables
  • Dynamic memory allocation by means of the ALLOCATABLE attribute and the ALLOCATE and DEALLOCATE statements
  • POINTER attribute, pointer assignment, and NULLIFY statement to facilitate the creation and manipulation of dynamic data structures
  • Structured looping constructs, with an END DO statement for loop termination, and EXIT and CYCLE statements for "breaking out" of normal DO loop iterations in an orderly way
  • SELECT . . . CASE construct for multi-way selection
  • Portable specification of numerical precision under the user's control
  • New and enhanced intrinsic procedures.
[edit] Obsolescence & Deletions

Unlike the previous revision, Fortran 90 did not delete any features. (Appendix B.1 says, "The list of deleted features in this standard is empty.") Any standard-conforming FORTRAN 77 program is also standard-conforming under Fortran 90, and either standard should be usable to define its behavior.

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     IF (X) 10, 20, 30
Non-integer DO parameters or control variables     DO 9, X= 1.7, 1.6, -0.1 Deleted
Shared DO-loop termination or
termination with a statement
other than END DO or CONTINUE  
    DO 9, J= 1, 10

        DO 9, K= 1, 10
9   L= J + K

Branching to END IF

from outside a block

66  GO TO 77 ; . . .

    IF (E) THEN ;     . . .
77  END IF

Alternate return     CALL SUBR( X, Y *100, *200 )
PAUSE statement     PAUSE 600 Deleted
ASSIGN statement
  and assigned GO TO statement
100  . . .

    ASSIGN 100 TO H
    . . .
    GO TO H . . .

Assigned FORMAT specifiers     ASSIGN F TO 606 Deleted
H edit descriptors 606 FORMAT ( 9H1GOODBYE. ) Deleted
Computed GO TO statement     GO TO (10, 20, 30, 40) index (Obso.)
Statement functions     FOIL( X, Y )= X**2 + X*Y + Y**2 (Obso.)
DATA statements
  among executable statements
    X= 27.3

    DATA A, B, C / 5.0, 12.0. 13.0 /     . . .

CHARACTER* form of CHARACTER declaration     CHARACTER*8 STRING   ! Use CHARACTER(8) (Obso.)
Assumed character length functions
Fixed form source code * Column 1 contains * or ! or C for comments.
C       Column 6 for continuation.

[edit] Fortran 95

Fortran 95 was a minor revision, mostly to resolve some outstanding issues from the Fortran 90 standard. Nevertheless, Fortran 95 also added a number of extensions, notably from the High Performance Fortran specification:

  • FOR ALL and nested WHERE constructs to aid vectorization
  • User-defined PURE and ELEMENTAL procedures

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.

[edit] Conditional Compilation and Varying length strings

In addition to the mandatory "Base language" (defined in ISO/IEC 1539-1 : 1997), the Fortran 95 language also includes two optional modules:

  • Varying character strings (ISO/IEC 1539-2 : 2000)
  • Conditional compilation (ISO/IEC 1539-3 : 1998)

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."

[edit] Fortran 2003

The most recent standard, Fortran 2003, is a major revision introducing many new features. A comprehensive summary of the new features of Fortran 2003 is available at the ISO Fortran Working Group (WG5) official Web site, and may be downloaded directly as a PDF file (PDF) or gzipped PostScript file.

From that article, the major enhancements for this revision include:

  • Derived type enhancements: parameterized derived types, improved control of accessibility, improved structure constructors, and finalizers.
  • Object oriented programming support: type extension and inheritance, polymorphism, dynamic type allocation, and type-bound procedures.
  • Data manipulation enhancements: allocatable components (incorporating TR 15581), deferred type parameters, VOLATILE attribute, explicit type specification in array constructors and allocate statements, pointer enhancements, extended initialization expressions, and enhanced intrinsic procedures.
  • Input/output enhancements: asynchronous transfer, stream access, user specified transfer operations for derived types, user specified control of rounding during format conversions, named constants for preconnected units, the FLUSH statement, regularization of keywords, and access to error messages.
  • Procedure pointers.
  • Support for IEEE floating-point arithmetic and floating point exception handling (incorporating TR 15580).
  • Interoperability with the C programming language.
  • Support for international usage: access to ISO 10646 4-byte characters and choice of decimal or comma in numeric formatted input/output.
  • Enhanced integration with the host operating system: access to command line arguments, environment variables, and processor error messages.

[edit] Fortran 2008

Efforts are underway to develop a revision to Fortran 2003, tentatively called Fortran 2008. As with Fortran 95, this is intended to be a minor upgrade, incorporating clarifications and corrections to Fortran 2003, as well as introducing a select few new capabilities. Proposed new capabilities include

A full list is in the report "The language features that have been chosen for Fortran 2008" PDF file (PDF 24.2 KiB).

[edit] The legacy of FORTRAN

Since Fortran has been in use for nearly fifty years, there is a vast body of Fortran in daily use throughout the scientific and engineering communities. It is the primary language for some of the most intensive supercomputing tasks, such as weather and climate modeling, computational fluid dynamics, computational chemistry, quantum chromodynamics, simulations of long-term solar system dynamics, high-fidelity evolution artificial satellite orbits, and simulation of automobile crash dynamics. Indeed, one finds that even today, half a century later, floating-point benchmarks to gauge the performance of new computer processors are still written in Fortran (e.g., CFP2000, the floating-point component of the SPEC CPU2000 benchmarks).

[edit] Language features

The Fortran language features described are intended to be a fairly comprehensive overview of the Fortran language; full details may be found in any of several Fortran textbooks. Only those features widely used in new programs are described, as few of the historic features are used in modern programs. Still, most have been retained in the language to maintain backward compatibility.

For additional details, see Fortran language features.

[edit] Portability

Portability was a problem in the early days because there was no agreed standard - not even IBM's reference manual - and computer companies vied to differentiate their offerings from others by providing incompatible features. Standards have improved portability. The 1966 standard provided a reference syntax and semantics, but vendors continued to provide incompatible extensions. Although careful programmers were coming to realize that use of incompatible extensions caused expensive portability problems, and were therefore using programs such as The PFORT Verifier, it was not until after the 1977 standard, when the National Bureau of Standards (now NIST) published FIPS PUB 69, that processors purchased by the U.S. Government were required to diagnose extensions of the standard. Rather than offer two processors, essentially every compiler eventually had at least an option to diagnose extensions.

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.

[edit] Variants of Fortran

I was one of the original IBM Customer Engineers that ilslanted 704 serial 13 at Lockheed Aircraft in Marietta, GA in May 1956. When Fortran was released in April 1957 we were one of the first customers to run it. We soon ran into troubles where compiler would print out the message Machine error on the 716 printer. To solve this problem we needed a source listing of the compiler. It took the Branch Manager several days to get one for us and it was on a roll of 35 mm microfilm. This had to be under IBM control at all times and when we finished the bug it was sent back to the Branch Office. I don't know what happend to that roll but I just wanted to point out that a listing did exist in that form at that time.If you are interested send me an email address and I will send you a two page Word document from my memoirs describing this period.Van GardnerSmyrna, Ga.

[edit] Fortran-based languages

Prior to FORTRAN 77, a number of preprocessors were commonly used to provide a friendlier language, with the advantage that the preprocessed code could be compiled on any machine with a standard FORTRAN compiler. Popular preprocessors included FLECS, MORTRAN, Ratfor, and Ratfiv. (Ratfor and Ratfiv, for example, implemented a remarkably C-like language, outputting preprocessed code in standard FORTRAN 66.[8])

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 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.

[edit] Code examples

The sample programs can be compiled and run with any standard Fortran compiler (see the end of this article for lists of compilers). Most modern Fortran compilers expect a file with a .f or .for extension (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 .f90/.f95 extension (for Fortran 90/95 free-form source, respectively).

For additional details, see Fortran code examples.

[edit] FORTRAN quotations

For a programming language with a half-century legacy, FORTRAN not surprisingly has accumulated its share of jokes and folklore.

[edit] From the historical record

  • God is Real, unless declared Integer.[1] J.Allan Toogood, FORTRAN programmer. In FORTRAN, undeclared variables are typed according to their first letter, so "God" would be a real number.
  • FORTRAN, the infantile disorder, by now nearly 20 years old, is hopelessly inadequate for whatever computer application you have in mind today: it is now too clumsy, too risky, and too expensive to use.Edsger Dijkstra, circa 1970.
  • "The sooner the world forgets that FORTRAN ever existed, the better." (imputed to Joseph Weizenbaum)
  • "95 percent of the people who programmed in the early years would never have done it without Fortran." - Ken Thompson, circa 2005 [9]
  • "The primary purpose of the DATA statement is to give names to constants; instead of referring to pi as 3.141592653589793 at every appearance, the variable PI can be given that value with a DATA statement and used instead of the longer form of the constant. This also simplifies modifying the program, should the value of pi change." —Early FORTRAN manual for Xerox Computers[10]
  • "Consistently separating words by spaces became a general custom about the tenth century A.D., and lasted until about 1957, when FORTRAN abandoned the practice."Sun FORTRAN Reference Manual
  • "People are very flexible and learn to adjust to strange surroundings — they can become accustomed to read Lisp and Fortran programs, for example."Art of PROLOG, Leon Sterling and Ehud Shapiro, MIT Press
  • "Warning: Go directly to Jail. Do not pass GO. Do not collect $200." - Easter egg in the SDS/Xerox Sigma 7 FORTRAN compiler, when the statement GO TO JAIL was encountered. The message is from a Chance card in Monopoly.

[edit] References in popular culture

  • In the pilot episode of the Futurama series, the robot Bender drinks a bottle of Olde FORTRAN Malt Liquor (alluding to "Olde English" malt liquor)
  • Computer folklore has incorrectly attributed the loss of the Mariner I space probe to a typographical error in a Fortran program. For example, "Recall the first American space probe to Venus, reportedly lost because Fortran cannot recognize a missing comma in a DO statement ..." [11].
  • In 1982, 10,000 Maniacs released a song named "Planned Obsolescence" that includes the repeated line - "Science [is] truth for life, in Fortran tongue the answer".

[edit] FORTRAN Anecdotes

[edit] FORTRAN II on the IBM 1401 and 1460

The IBM 1401 computer, introduced in 1959, supported Fortran by the middle 1960s although the 1401 was intended for decimal business computation and as a primitive printer "server" that would print the contents of magnetic tapes, prepared on much larger systems such as the IBM 7090.

The absolute minimum configuration was supported, for example, at Roosevelt University in Chicago until 1974 (cf. Edward G. Nilges, "Build Your Own .Net Language and Compiler", Apress 2004). This configuration was 8K of 6-bit bytes for RAM and a card reader and punch (cf. Nilges, "Anecdotes", IEEE Transactions on the History of Software, Spring/Summer 1999).

The compiler, as described below, was a series of about 100 small overlay phases (cf. John A. N. Lee, "The Anatomy of a Compiler", Van Nostrand Rheinhold 1968), where a miniature monitor stayed resident in memory to load each phase. These phases were loaded from a card deck of more than 2,000 punched cards (more than two feet long) or from a tape drive (which wasn't available at the Roosevelt University installation).

These overlays would scan and parse a "squozed" (blank-removed: run length encoded) form of the source code to produce statements in an interpretive language at the end of available memory (since the end of memory could not be sensed, it had to be spelled out on a "control card"). The final phase was responsible for interpreting the code.

Despite the primitive Fortran II compiler, which had no strings, the rather complex and flexible FORMAT statement was supported. In addition, another "control" card could specify how many decimals would be supported in floating point format; this feature looked forward to a vastly more flexible feature in today's Mathematica system.

However, for a number of years, the installation at Roosevelt University was deprived of Fortran despite the availability of the compiler "deck". At some point in time in 1970, an IBM customer engineer had "fixed" a bug, thought to result from the absence of special-purpose multiply/divide hardware (for which 1401 customers had to pay extra) by overlaying memory with a jump to a subroutine for multiplication and division.

Unfortunately, on the minimal configuration, this destroyed instructions and never worked for this reason. Roosevelt was paying for multiply and divide, so, when in 1972 the customer engineer's patch was removed, the compiler then worked. It was used for administration, teaching and research until about 1977.

The IBM 1460 (similar to the 1401) also had a Fortran II compiler that resided on tape. It required only that tape drive, a card reader/punch and a printer, i.e. no "work" devices.

The compiler for the 1401 and 1460 was in the form of a multitude of tiny phases, or segments, that were passed over the source program which was held in storage throughout the compile. The first phase read the program from the card reader, numbered the statements, and produced a source listing. The next phases might be something like "copy (and reverse) the program from low storage to high storage, assigning and replacing the names with tokens." The appearance was that the system tape containing the compiler would "blip", the computer would hum for a bit, then the tape would "blip" again and another part of the listing would appear on the printer. The end result was an object deck on the punch, and the program was left in storage and ready to go.

The effect was quite unusual, and was designed to be able to compile the largest possible program with the fewest peripheral devices.

[edit] Letter O considered harmful

During the same Fortran Standards Committee meeting at which the name "FORTRAN 77" was chosen, a technical proposal was somehow smuggled into the official distribution, bearing the title, "Letter O considered harmful". This deceptively simple proposal purported to address the confusion that sometimes arises between the letter "O" and the numeral zero, by eliminating the letter from allowable variable names. However, the method proposed was to eliminate the letter from the character set entirely (thereby retaining 48 as the number of lexical characters, which the colon had increased to 49).

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. (Troublesome 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".

[edit] References

[edit] Textbooks

  • Etter, D. M. (1990). Structured FORTRAN 77 for Engineers and Scientists, 3nd ed., The Benjamin/Cummings Publishing Company, Inc.. ISBN 0-8053-0051-1. 
  • Chapman, Stephen J. (2007). Fortran 95/2003 for Scientists and Engineers, 3nd ed., McGraw-Hill. ISBN 978-0-07-319157-7. 
  • Chapman, Stephen J. (2003). Fortran 90/95 for Scientists and Engineers, 2nd ed., McGraw-Hill. ISBN 0-07-282575-8. 
  • Chivers, Ian; Jane Sleightholme (2006). Introduction to Programming with Fortran, 1st ed., Springer. ISBN 1-84628-053-2. 
  • Ellis, T. M. R.; Ivor R. Phillips, Thomas M. Lahey (1994). Fortran 90 Programming, 1st ed., Addison Wesley. ISBN 0-201-54446-6. 
  • McCracken, Daniel D. (1961). A Guide to Fortran Programming. Wiley. 
  • McCracken, Daniel D. (1965). A Guide to Fortran IV Programming. Wiley. 
  • Metcalf, Michael; John Reid, Malcolm Cohen (2004). Fortran 95/2003 Explained. Oxford University Press. ISBN 0-19-852693-8. 
  • Nyhoff, Larry; Sanford Leestma (1995). FORTRAN 77 for Engineers and Scientists with an Introduction to Fortran 90, 4th ed., Prentice Hall. ISBN 0-13-363003-X. 
  • Martínez Baena, Javier; Ignario Requena Ramos, Nicolás Marín Ruiz (2006). Programación estructurada con Fortran 90/95. Universidad de Granada. ISBN 84-338-3923-3. 

[edit] "Core" language standards

  • ANSI X3.9-1966. USA Standard FORTRAN, informally known as FORTRAN 66, American National Standards Institute. 
  • ANSI X3.9-1978. American National Standard – Programming Language FORTRAN, also known as ISO 1539-1980, informally known as FORTRAN 77, American National Standards Institute. 
  • ANSI X3.198-1992 (R1997). American National Standard – Programming Language Fortran Extended, informally known as Fortran 90, American National Standards Institute. 
  • ISO/IEC 1539-1:1997. Information technology – Programming languages – Fortran – Part 1: Base language, informally known as Fortran 95. There are a further two parts to this standard. Part 1 has been formally adopted by ANSI. 
  • ISO/IEC 1539-1:2004. Information technology – Programming languages – Fortran – Part 1: Base language, informally known as Fortran 2003. 

[edit] Related standards

[edit] Notes

  1. The names of earlier versions of the language through FORTRAN 77 were conventionally spelled in all-caps (FORTRAN 77 was the version in which the use of lowercase letters in keywords was strictly nonstandard). The capitalization has been dropped in referring to newer versions beginning with Fortran 90. The official language standards now refer to the language as "Fortran." Because the capitalization (or lack thereof) of the word FORTRAN was never 100% consistent in actual usage, and because many hold impassioned beliefs on the issue, this article, rather than attempt to be normative, adopts the convention of using the all-caps FORTRAN in referring to versions of FORTRAN through FORTRAN 77 and the title-caps Fortran in referring to versions of Fortran from Fortran 90 onward. This convention is reflected in the capitalization of FORTRAN in the ANSI X3.9-1966 (FORTRAN 66) and ANSI X3.9-1978 (FORTRAN 77) standards and the title caps Fortran in the ANSI X3.198-1992 (Fortran 90) standard.
  2. Since FORTRAN 77, which introduced the CHARACTER data type.
  3. Since FORTRAN II (1958).
  4. Note: It is commonly believed that this statement corresponded to a three-way branch instruction on the IBM 704. This is not true, the 704 branch instructions all contained only one destination address (e.g., TZE - Transfer AC Zero, TNZ - Transfer AC Not Zero, TPL - Transfer AC Plus, TMI - Transfer AC Minus). The machine (and its successors in the 700/7000 series) did have a three-way skip instruction (CAS - Compare AC with Storage), which was probably the origin of this belief, but using this instruction to implement the IF would consume 4 instruction words, require the constant Zero in a word of storage, and take 3 machine cycles to execute; using the Transfer instructions to implement the IF could be done in 1 to 3 instruction words, required no constants in storage, and take 1 to 3 machine cycles to execute. An optimizing compiler like FORTRAN would most likely select the more compact and usually faster Transfers instead of the Compare (use of Transfers also allowed the FREQUENCY statement to optimize IFs, which could not be done using the Compare). Also the Compare considered -0 and +0 to be different values while the Transfer Zero and Transfer Not Zero considered them to be the same.
  5. The FREQUENCY statement in FORTRAN was used originally and optionally to give branch probabilities for the three branch cases of the Arithmetic IF statement to bias the way code was generated and order of the basic blocks of code generated, in the global optimisation sense, were arranged in memory for optimality. The first FORTRAN compiler used this weighting to do a Monte Carlo simulation of the run-time generated code at compile time. It was very sophisticated for its time. This technique is documented in the original article in 1957 on the first FORTRAN compiler implementation by J. Backus, et al. Many years later, the FREQUENCY statement had no effect on the code, and was treated as a comment statement, since the compilers no longer did this kind of compile-time simulation. Below is a part of the 1957 paper, "The FORTRAN Automatic Coding System" by Backus, et al., with this snippet on the FREQUENCY statement and its use in a compile-time Monte Carlo simulation of the run-time to optimise the code generated. Quoting ...
    The fundamental unit of program is the basic block; a basic block is a stretch of program which has a single entry point and a single exit point. The purpose of section 4 is to prepare for section 5 a table of predecessors (PRED table) which enumerates the basic blocks and lists for every basic block each of the basic blocks which can be its immediate predecessor in flow, together with the absolute frequency of each such basic block link. This table is obtained by an actual "execution" of the program in Monte-Carlo fashion, in which the outcome of conditional transfers arising out of IF-type statements and computed GO TO'S is determined by a random number generator suitably weighted according to whatever FREQUENCY statements have been provided.
  6. McCraken, Daniel D. (1965(3rd printing 1968)). A Guide to FORTRAN IV Programming. John Wiley & Sons, Inc., New York. LCCCN 65-26848.  Preface p. v
  7. Chilton Computing with FORTRAN
  8. This is not altogether surprising, as Brian Kernighan, one of the co-creators of Ratfor, is also co-author of The C Programming Language.
  9. Lohr, Steve. "John W. Backus, 82, Fortran Developer, Dies", 2007-03-19. Retrieved on 2007-03-20. 
  10. Prior to FORTRAN 77, which introduced the PARAMETER statement (the preferred method of defining constants), the DATA statement was the conventional way to define constants, although this statement merely specified initial values and did not prevent the corresponding variables from being modified (as by regular assignment statements).
  11. Hoare, C. A. R.. Hints on Programming Language Design.  in (October 1973) Sigact/Sigplan Symposium on Principles of Programming Languages. , reprinted in Horowitz. Programming Languages, A Grand Tour, 3rd ed. . See (and for what really happened)

[edit] External links





Code repositories

Open source compilers

  • GFortran - The GNU Fortran 95 compiler, part of GCC. Distributed as part of GCC as of GCC 4.0. Replaced g77.
  • g95 - Free, open source Fortran 95 compiler and runtime libraries
  • Open64 - Open Research Compiler. Suite of optimizing compiler development tools for Intel Itanium (Linux)
  • Open Watcom - A joint effort between SciTech Software Inc, Sybase and the Open Source development community to maintain Fortran cross compilers and tools

Non-open source compilers

  • Intel Fortran Compiler
  • Absoft Fortran 95/90/77 and C/C++ compilers for Windows, Mac OS 9 and OS X, Linux IA32 and AMD Opteron and AMD Athlon 64-bit processors
  • IBM Fortran 95 compilers for AIX, Blue Gene, and Linux
  • Lahey/Fujitsu - Fortran 95 compilers for Linux and Windows
  • NAGWare Fortran 95 compiler with 2003 features for Linux, Windows, and Unix on many platforms
  • Qlogic Pathscale - Fortran 95, C, and C++ compilers for Linux on AMD Opteron and Intel 64-bit and 32-bit x86 CPUs
  • PGI Fortran 95, C and C++ Compilers for 32-bit and 64-bit AMD64 and IA32 processor-based Linux and Windows systems
  • Silverfrost (was Salford) - Personal edition (Windows)
  • Sun Studio Fortran 95 - From Sun Microsystems; compiles optimized and parallelized code for the Solaris OS on SPARC and x86/x64 platforms, and Linux on x86/x64 platforms

Graphical libraries/GUI

  • f90gl - Public domain implementation of the official Fortran 90 bindings for OpenGL (Linux, Mac OS X, Solaris, UNIX, Windows)
  • ftcl - A Fortran–Tcl/TK interface
  • g2 graphical library - Portable and 2D graphics library (Linux, Mac OS X, OpenVMS, Solaris, UNIX, Windows)GNU LGPL
  • GrWin Graphics Library - Free graphics routine library for Fortran (Windows)
  • pilib - Platform Independent Library for Fortran 90/95 (Linux, Mac OS X, UNIX, Windows) GNU LGPL
  • PLplot - A Scientific Plotting Library (Linux, Mac OS X, MS-DOS, Unix, Windows) GNU LGPL

Testing Frameworks

  • FUnit - a unit testing framework.


Additional copyright notice: Some content of this page is a derivative work of a Wikipedia article under the CC-BY-SA License and/or GNU FDL. The original article and author information can be found at