View source for Fortran

{{Short description|General-purpose programming language}}
{{Infobox programming language
| logo = 
| logo size = 
| logo caption = 
| paradigm = Multi-paradigm: [[Structured programming|structured]], [[Imperative programming|imperative]] ([[Procedural programming|procedural]], [[Object-oriented programming|object-oriented]]), [[Generic programming|generic]], [[Array programming|array]]
| year = {{Start date and age|1957}}
| designer = [[Biography:John Backus|John Backus]]
| developer = [[Biography:John Backus|John Backus]] and [[Company:IBM|IBM]]
| latest release version = Fortran 2023 (ISO/IEC 1539:2023)
| latest release date = {{Start date and age|2023|11|17}}
| typing = [[Strong and weak typing|strong]], [[Type system|static]], [[Manifest typing|manifest]]
| implementations = [[Company:Absoft Fortran Compilers|Absoft]], [[Company:Cray|Cray]], [[Software:GNU Fortran|GFortran]], [[Software:G95|G95]], [[Company:IBM|IBM]] XL Fortran, [[Software:Intel Fortran Compiler|Intel]], [[Company:Hitachi|Hitachi]], Lahey/Fujitsu, [[Company:Numerical Algorithms Group|Numerical Algorithms Group]], Open Watcom, [[Software:PathScale|PathScale]], PGI, [[Software:Silverfrost FTN95|Silverfrost]], Oracle Solaris Studio, others
| dialects = 
| influenced_by = [[Speedcoding]]
| influenced = [[ALGOL 58]], [[BASIC]], [[C (programming language)|C]], [[Chapel (programming language)|Chapel]],<ref name="chplspec">{{cite web|title=Chapel spec (Acknowledgements)|url=http://chapel.cray.com/spec/spec-0.98.pdf |archive-url=https://web.archive.org/web/20160205114946/http://chapel.cray.com/spec/spec-0.98.pdf |archive-date=February 5, 2016 |url-status=live|date=October 1, 2015|access-date=January 14, 2016|publisher=Cray Inc}}</ref> [[CMS-2 (programming language)|CMS-2]], [[DOPE (Dartmouth Oversimplified Programming Experiment)|DOPE]], [[Fortress (programming language)|Fortress]], PL/I, PACT I, [[MUMPS]], [[IDL (programming language)|IDL]], [[Ratfor]]
| operating_system = 
| license = 
| file_ext = {{code|.f90}}, {{code|.f}}, {{code|.for}}
| website = 
}}

'''Fortran''' ({{IPAc-en|ˈ|f|ɔr|t|r|æ|n}}; formerly '''FORTRAN''') is a general-purpose, [[Compiled language|compiled]] [[Imperative programming|imperative]] [[Programming language|programming language]] that is especially suited to [[Numerical analysis|numeric computation]] and [[Computational science|scientific computing]].

Fortran was originally developed by [[Company:IBM|IBM]]<ref name="Where">{{cite web |url= http://www.softwarepreservation.org/projects/FORTRAN/paper/p25-backus.pdf |archive-url=https://web.archive.org/web/20070726192224/http://www.softwarepreservation.org/projects/FORTRAN/paper/p25-backus.pdf |archive-date=July 26, 2007 |url-status=live |author=John Backus |title=The history of FORTRAN I, II and III |publisher= Softwarepreservation.org |access-date=November 19, 2014}}</ref> in the 1950s for scientific and engineering applications, and subsequently came to dominate scientific computing. It has been in use for over seven decades in computationally intensive areas such as [[Earth:Numerical weather prediction|numerical weather prediction]], [[Finite element method|finite element analysis]], [[Computational fluid dynamics|computational fluid dynamics]], [[Physics:Geophysics|geophysics]], [[Physics:Computational physics|computational physics]], [[Physics:Crystallography|crystallography]] and [[Chemistry:Computational chemistry|computational chemistry]]. It is a popular language for [[High-performance computing|high-performance computing]]<ref name="hpc">{{cite journal |url= http://queue.acm.org/detail.cfm?id=1820518 |author=Eugene Loh |title=The Ideal HPC Programming Language |journal=Queue |date=June 18, 2010 |volume=8 |issue=6}}</ref> and is used for programs that benchmark and rank the world's [[TOP500|fastest supercomputers]].<ref>{{cite web|title = HPL – <!--ndash ok here as substitute for hyphen?--> A Portable Implementation of the High-Performance Linpack Benchmark for Distributed-Memory Computers | access-date = February 21, 2015 | url = http://www.netlib.org/benchmark/hpl}}</ref><ref>{{cite web|title = Q13. What are the benchmarks? | work = Overview – CPU 2017 | publisher = SPEC | access-date = November 13, 2019 | url = http://www.spec.org/cpu2017/Docs/overview.html#benchmarks}}</ref>

[[File:IBM Blue Gene P supercomputer.jpg|thumb|The [[Engineering:IBM Blue Gene|IBM Blue Gene/P]] supercomputer installation in 2007 at the Argonne Leadership Angela Yang Computing Facility located in the Argonne National Laboratory, in Lemont, Illinois, {{wipe|United States}}]]

Fortran's design was the basis for many other programming languages, especially [[BASIC]] and [[ALGOL]]. But Fortran has itself evolved through numerous versions and dialects, adding extensions while largely retaining compatibility with preceding versions. Successive versions have added support for [[Structured programming|structured programming]] and processing of character-based data (FORTRAN 77), [[Array programming|array programming]], [[Modular programming|modular programming]] and [[Generic programming|generic programming]] (Fortran 90), [[High Performance Fortran]] (Fortran 95), [[Object-oriented programming|object-oriented programming]] (Fortran 2003), concurrent programming (Fortran 2008), and native [[Parallel computing|parallel computing]] capabilities (Coarray Fortran 2008/2018).

[[File:Algol&Fortran family-by-Borkowski.svg|thumb|upright=1.2|FORTRAN and COBOL genealogy tree]]

Since August 2021, Fortran has ranked among the top fifteen languages in the [[TIOBE index]], a measure of the popularity of programming languages.<ref>{{cite web|url=https://www.tiobe.com/tiobe-index/|title=TIOBE Index|author=TIOBE Software BV|date=September 2022|website=TIOBE.com|publisher=[[TIOBE index|TIOBE]]|access-date=September 23, 2022}}</ref>

==Naming==
The first manual for FORTRAN describes it as a ''Formula Translating System'', and printed the name with small caps, {{smallcaps|Fortran}}.<ref name="Sayre_1956"/>{{rp|p.2}}<ref name="history-fortran-i-ii-333"/>  Other sources suggest the name stands for ''Formula Translator,''<ref>{{cite web |url=https://www.ibm.com/ibm/history/ibm100/us/en/icons/fortran/ |title=FORTRAN: The Pioneering Programming Language |website= [[Company:IBM|IBM]]|date=March 7, 2012 |publisher= |access-date=July 19, 2017 |quote=}}</ref> or ''Formula Translation''.<ref>{{cite encyclopedia |title=FORTRAN |encyclopedia=Encyclopedia Britannica |date=June 14, 2021 |publisher= |location= |id= |url=https://www.britannica.com/technology/FORTRAN |access-date=July 19, 2021 }}</ref> Early IBM computers did not support lower case letters and the names of versions of the language through FORTRAN&nbsp;77 were usually spelled in all-uppercase<ref>{{cite book|last=Chapman|first=Stephen J.|date=2018|title=Fortran for Scientists and Engineers|url=https://www.mheducation.com/highered/product/fortran-scientists-engineers-chapman/M9780073385891.html|edition=Fourth|location={{wipe|New York City}}|publisher=McGraw-Hill Education|page=13|isbn=978-0-07-338589-1}}</ref> (FORTRAN&nbsp;77 was the last version in which the Fortran character set included only uppercase letters<ref>The "Fortran character set" defined by the FORTRAN&nbsp;77 standard was the minimal character set that standard-compliant compilers were required to support; in practice, many FORTRAN&nbsp;77 compilers supported the full [[ASCII]] character set.</ref>).  The official language [[International standard|standards]] for Fortran have referred to the language as "Fortran" with initial caps since Fortran 90.

==Origins==
[[File:John Backus 2.jpg|thumb|upright|John Backus (1924–2007) proposed the FORTRAN project in December 1953 and received the A.M. Turing Award in 1977.]]

In late 1953, [[Biography:John Backus|John W. Backus]] submitted a proposal to his superiors at [[Company:IBM|IBM]] to develop a more practical alternative to [[Assembly language|assembly language]] for programming their IBM 704 [[Mainframe computer|mainframe computer]].<ref name="history-fortran-i-ii-333">{{cite journal |date=October–December 1998 |title=The History of Fortran I, II, and III |url=http://www.softwarepreservation.org/projects/FORTRAN/paper/p165-backus.pdf |url-status=live |journal=[[IEEE Annals of the History of Computing]] |volume=20 |issue=4 |pages=68–78 |doi=10.1109/85.728232 |archive-url=https://web.archive.org/web/20160303230833/http://www.softwarepreservation.org/projects/FORTRAN/paper/p165-backus.pdf |archive-date=March 3, 2016 |access-date=June 17, 2020 |author-first=John |author-last=Backus}} [https://archive.org/details/history-of-fortran][https://archive.org/details/history-of-fortran]</ref>{{rp|69}} Backus' historic FORTRAN team consisted of programmers Richard Goldberg, Sheldon F. Best, Harlan Herrick, Peter Sheridan, Roy Nutt, Robert Nelson, Irving Ziller, Harold Stern, [[Biography:Lois Haibt|Lois Haibt]], and [[Biography:David Sayre|David Sayre]].<ref name="Backus57">{{cite conference|url=http://www.softwarepreservation.org/projects/FORTRAN/paper/BackusEtAl-FortranAutomaticCodingSystem-1957.pdf|title=The FORTRAN Automatic Coding System|conference=Western Joint Computer Conference|pages=188–198|date=February 1957|doi=10.1145/1455567.1455599|author1=J. W. Backus|author-link1=John Backus|author2=R. J. Beeber|author3=S. Best|author4=R. Goldberg|author5=L. M. Haibt|author-link5=Lois Haibt|author6=H. L. Herrick|author7=R. A. Nelson|author8=D. Sayre|author-link8=David Sayre|author9=P. B. Sheridan|author10=H. Stern|author11=L. Ziller|author12=R. A. Hughes|author13=R. Nutt|author-link13=Roy Nutt}}</ref> Its concepts included easier entry of equations into a computer, an idea developed by [[Biography:J. Halcombe Laning|J. Halcombe Laning]] and demonstrated in the [[Laning and Zierler system]] of 1952.<ref>{{cite book |last=Mindell |first=David |title=Digital Apollo |publisher=MIT Press |location=Cambridge, MA |year=2008 |page=99 | isbn=978-0-262-13497-2 | oclc=228031739 |jstor=j.ctt5hhn02}}</ref>

[[File:Fortran acs cover.jpeg|thumb|upright|''The Fortran Automatic Coding System for the IBM 704'' (October 15, 1956), the first programmer's reference manual for Fortran<ref name="Sayre_1956" />]]

A draft specification for ''The IBM Mathematical Formula Translating System'' was completed by November 1954.<ref name="history-fortran-i-ii-333"/>{{rp|71}} The first manual for FORTRAN appeared in October 1956,<ref name="Sayre_1956"/><ref name="history-fortran-i-ii-333"/>{{rp|72}} with the first FORTRAN [[Compiler|compiler]] delivered in April 1957.<ref name="history-fortran-i-ii-333"/>{{rp|75}} This was the first [[Optimizing compiler|optimizing compiler]], because customers were reluctant to use a [[High-level programming language|high-level programming language]] unless its compiler could generate code with performance approaching that of hand-coded assembly language.<ref>{{cite journal |title=The Fortran I Compiler |author-first=David |author-last=Padua |journal=Computing in Science & Engineering |date=January–February 2000 |volume=2 |issue=1 |pages=70–75 |doi=10.1109/5992.814661 |bibcode=2000CSE.....2a..70P |url=http://polaris.cs.uiuc.edu/publications/c1070.pdf |archive-url=https://web.archive.org/web/20200617113640/http://polaris.cs.uiuc.edu/publications/c1070.pdf |archive-date=June 17, 2020 |quote=The Fortran I compiler was the first major project in code optimization. It tackled problems of crucial importance whose general solution was an important research focus in compiler technology for several decades. Many classical techniques for compiler analysis and optimization can trace their origins and inspiration to the Fortran I compiler.}}</ref>

While the community was skeptical that this new method could possibly outperform hand-coding, it reduced the number of programming statements necessary to operate a machine by a factor of 20, and quickly gained acceptance.  John Backus said 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, writing programs for computing missile trajectories, I started work on a programming system to make it easier to write programs."<ref>{{cite news|url=http://www.nbcnews.com/id/17704662/ns/technology_and_science-tech_and_gadgets/t/fortran-creator-john-backus-dies|title=Fortran creator John Backus dies|publisher=MSNBC|author=Brian Bergstein|date=May 20, 2007|access-date=October 29, 2018}}</ref>

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 data type|complex number data type]] in the language made Fortran especially suited to technical applications such as electrical engineering.<ref>{{cite web | title=FORTRAN – The First Programming Language for Numeric Calculations | website=SciHi Blog | date=October 15, 2019 | url=http://scihi.org/fortran-programming/}}</ref>

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 [[Cross-platform software|cross-platform]] programming language.{{Citation needed|date=October 2023|reason=that's an interesting claim,  so one that should be backed up with a secondary ref}}

FORTRAN was provided for the IBM 1401 computer by an innovative 63-phase compiler that ran entirely in its [[Magnetic-core memory|core memory]] of only 8000 (six-bit) characters.  The compiler could be run from tape, or from a 2200-card deck; it used no further tape or disk storage.  It kept the program in memory and loaded [[Overlay (programming)|overlays]] that gradually transformed it, in place, into executable form, as described by Haines.<ref>{{cite journal
| first = L. H.
| last = Haines
| title = Serial compilation and the 1401 FORTRAN compiler
| journal = IBM Systems Journal
| volume = 4
| issue = 1
| year = 1965
| pages = 73–80
| doi = 10.1147/sj.41.0073
}}</ref>
This article was reprinted, edited, in both editions of ''Anatomy of a Compiler''<ref>{{cite book | first = John A. N. | last = Lee | title = Anatomy of a Compiler | publisher = Van Nostrand Reinhold | date = 1967}}</ref> and in the IBM manual "Fortran Specifications and Operating Procedures, IBM 1401".<ref>{{cite manual|title=Fortran Specifications and Operating Procedures, IBM 1401|url=http://bitsavers.org/pdf/ibm/1401/C24-1455-2_Fortran_Specifications_and_Operating_Procedures_Apr65.pdf |archive-url=https://web.archive.org/web/20170923222402/http://www.bitsavers.org/pdf/ibm/1401/C24-1455-2_Fortran_Specifications_and_Operating_Procedures_Apr65.pdf |archive-date=September 23, 2017 |url-status=live|publisher=IBM|id=C24-1455-2}}</ref>  The executable form was not entirely machine language; rather, floating-point arithmetic, sub-scripting, input/output, and function references were interpreted, preceding [[UCSD Pascal]] [[P-code machine#UCSD p-Machine|P-code]] by two decades. GOTRAN, a simplified, interpreted version of FORTRAN I (with only 12 statements not 32) for "load and go" operation was available (at least for the early IBM 1620 computer).<ref>{{cite web |url=http://hissa.nist.gov/mlists/ibm1620/199901/19990128-2.html  |title=Subject: GOTRAN ON THE IBM 1316 DISK STORAGE PACK (Serial No. K7402) |access-date=2006-03-03 |url-status=dead |archive-url=https://web.archive.org/web/20060221192243/http://hissa.nist.gov/mlists/ibm1620/199901/19990128-2.html |archive-date=2006-02-21 }}</ref> Modern Fortran, and almost all later versions, are fully compiled, as done for other high-performance languages.

The development of Fortran paralleled the early evolution of compiler technology, and many advances in the theory and design of [[Compiler|compiler]]s were specifically motivated by the need to generate efficient code for Fortran programs.

===FORTRAN===
The initial release of FORTRAN for the IBM 704<ref name="Sayre_1956"/> contained 32 statements, including:
* {{code|DIMENSION}} and {{code|EQUIVALENCE}} statements
* Assignment statements
* Three-way [[Arithmetic IF|''arithmetic'' {{code|IF}}]] statement, which passed control to one of three locations in the program depending on whether the result of the arithmetic statement was negative, zero, or positive
* {{code|IF}} statements for checking exceptions ({{code|ACCUMULATOR OVERFLOW}}, {{code|QUOTIENT OVERFLOW}}, and {{code|DIVIDE CHECK}}); and {{code|IF}} statements for manipulating [[Engineering:Front panel|sense switches and sense lights]]
* {{code|GO TO}}, computed {{code|GO TO}}, {{code|ASSIGN}}, and assigned {{code|GO TO}}
* {{code|DO}} loops
* Formatted I/O: {{code|FORMAT}}, {{code|READ}}, {{code|READ INPUT TAPE}}, {{code|WRITE}}, {{code|WRITE OUTPUT TAPE}}, {{code|PRINT}}, and {{code|PUNCH}}
* Unformatted I/O: {{code|READ TAPE}}, {{code|READ DRUM}}, {{code|WRITE TAPE}}, and {{code|WRITE DRUM}}
* Other I/O: {{code|END FILE}}, {{code|REWIND}}, and {{code|BACKSPACE}}
* {{code|PAUSE}}, {{code|STOP}}, and {{code|CONTINUE}}
* {{code|FREQUENCY}} statement (for providing optimization hints to the compiler).

The arithmetic {{code|IF}} statement was reminiscent of (but not readily implementable by) a three-way comparison instruction (CAS—Compare Accumulator with Storage) available on the 704. The statement provided the only way to compare numbers—by testing their difference, with an attendant risk of overflow. This deficiency was later overcome by "logical" facilities introduced in FORTRAN IV.

The {{code|FREQUENCY}} statement was used originally (and optionally) to give branch probabilities for the three branch cases of the arithmetic {{code|IF}} statement. The first FORTRAN compiler used this weighting to perform ''at compile time'' a [[Monte Carlo method|Monte Carlo simulation]] of the generated code, the results of which were used to optimize the placement of basic blocks in memory—a very sophisticated optimization for its time. The Monte Carlo technique is documented in Backus et al.'s paper on this original implementation, ''The FORTRAN Automatic Coding System'':

<blockquote>
The fundamental unit of program is the [[Basic block|basic block]]; a basic block is a stretch of program which has one entry point and one 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 running the program once 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.<ref name="Backus57" /></blockquote>

The first FORTRAN compiler reported diagnostic information by halting the program when an error was found and outputting an error code on its console. That code could be looked up by the programmer in an error messages table in the operator's manual, providing them with a brief description of the problem.<ref name="Sayre_1956" />{{rp|p.19–20}}<ref>{{cite book |publisher=Programming Research Department, International Business Machines Corporation |title=The FORTRAN Automatic Coding System for the IBM 704 EDPM : Preliminary Operator's Manual |date=April 8, 1957 |pages=6–37 |url=http://www.softwarepreservation.org/projects/FORTRAN/manual/Prelim_Oper_Man-1957_04_07.pdf |archive-url=https://web.archive.org/web/20140226151253/http://www.softwarepreservation.org/projects/FORTRAN/manual/Prelim_Oper_Man-1957_04_07.pdf |archive-date=February 26, 2014 |url-status=live }}</ref> Later, an error-handling subroutine to handle user errors such as division by zero, developed by NASA,<ref>{{cite web|first=Betty Jo |last=Armstead|date=January 21, 2015|url=https://spaceodyssey.dmns.org/media/62497/myyearsatnasa-_bettyjoarmstead.pdf|title=My Years at NASA|website=Denver Museum of Nature & Science|access-date=June 15, 2019|archive-date=December 24, 2019|archive-url=https://web.archive.org/web/20191224083647/https://spaceodyssey.dmns.org/media/62497/myyearsatnasa-_bettyjoarmstead.pdf |url-status=dead}}</ref> was incorporated, informing users of which line of code contained the error.

====Fixed layout and punched cards====
[[File:FortranCardPROJ039.agr.jpg|thumb|FORTRAN code on a punched card, showing the specialized uses of columns 1–5, 6 and 73–80]]
[[File:FortranCodingForm.png|thumb|A reproduction of a FORTRAN coding form, printed on paper and intended to be used by programmers to prepare programs for punching onto cards by keypunch operators. Now obsolete.]]

Before the development of disk files, text editors and terminals, programs were most often entered on a [[Engineering:Keypunch|keypunch]] keyboard onto 80-column [[Engineering:Punched card|punched card]]s, one line to a card. The resulting deck of cards would be fed into a card reader to be compiled. Punched card codes included no lower-case letters or many special characters, and special versions of the IBM 026 [[Engineering:Keypunch|keypunch]] were offered that would correctly print the re-purposed special characters used in FORTRAN.

Reflecting punched card input practice, Fortran programs were originally written in a fixed-column format, with the first 72 columns read into twelve 36-bit words.

A letter "C" in column 1 caused the entire card to be treated as a comment and ignored by the compiler. Otherwise, the columns of the card were divided into four fields:
* 1 to 5 were the label field: a sequence of digits here was taken as a label for use in DO or control statements such as GO TO and IF, or to identify a FORMAT statement referred to in a WRITE or READ statement. Leading zeros are ignored and 0 is not a valid label number.
* 6 was a continuation field: a character other than a blank or a zero here caused the card to be taken as a continuation of the statement on the prior card. The continuation cards were usually numbered 1, 2, ''etc.'' and the starting card might therefore have zero in its continuation column—which is not a continuation of its preceding card.
* 7 to 72 served as the statement field.
* 73 to 80 were ignored (the IBM 704's [[Engineering:IBM 711|card reader]] only used 72 columns).<ref>{{cite manual |url=http://www.bitsavers.org/pdf/ibm/7090/22-6528-4_7090Manual.pdf |archive-url=https://web.archive.org/web/20081201175757/http://bitsavers.org/pdf/ibm/7090/22-6528-4_7090Manual.pdf |archive-date=December 1, 2008 |url-status=live |title=Reference Manual, IBM 7090 Data Processing System |date=1961 |id=A22-6528-3}}</ref>

Columns 73 to 80 could therefore be used for identification information, such as punching a sequence number or text, which could be used to re-order cards if a stack of cards was dropped; though in practice this was reserved for stable, production programs. An IBM 519 could be used to copy a program deck and add sequence numbers. Some early compilers, e.g., the IBM 650's, had additional restrictions due to limitations on their card readers.<ref>{{cite manual |url= http://www.bitsavers.org/pdf/ibm/fortran/F28-8074-3_FORTRANII_GenInf.pdf |archive-url=https://web.archive.org/web/20050426055632/http://www.bitsavers.org/pdf/ibm/fortran/F28-8074-3_FORTRANII_GenInf.pdf |archive-date=April 26, 2005 |url-status=live  |title=Fortran II General Information Manual |date=1963 |access-date=November 19, 2014 }}</ref> [[Engineering:Keypunch|Keypunch]]es could be programmed to tab to column 7 and skip out after column 72. Later compilers relaxed most fixed-format restrictions, and the requirement was eliminated in the Fortran 90 standard.

Within the statement field, [[Whitespace character|whitespace character]]s (blanks) were ignored outside a text literal. This allowed omitting spaces between tokens for brevity or including spaces within identifiers for clarity. For example, {{code|AVG OF X}} was a valid identifier, equivalent to {{code|AVGOFX}}, and <source lang="fortran" inline>101010DO101I=1,101</source> was a valid statement, equivalent to <source lang="fortranfixed" inline>10101    DO 101   I = 1, 101</source> because the zero in column 6 is treated as if it were a space (!), while <source lang="fortran" inline>101010DO101I=1.101</source> was instead <source lang="fortranfixed" inline>10101    DO101I = 1.101</source>, the assignment of 1.101 to a variable called <source lang="fortran" inline>DO101I</source>. Note the slight visual difference between a comma and a period.

[[Hollerith constant|Hollerith strings]], originally allowed only in FORMAT and DATA statements, were prefixed by a character count and the letter H (e.g., {{code|26HTHIS IS ALPHANUMERIC DATA.}}), allowing blanks to be retained within the character string. Miscounts were a problem.

==Evolution==
{| class="wikitable floatright" style="margin-left: 1.5em;"
|+Timeline of Fortran language
|-
! Year
! Informal name
! ANSI Standard 
! ISO/IEC Standard
|-
| 1957
| FORTRAN
| {{n/a}}
| {{n/a}}
|-
| 1958
| FORTRAN II
| {{n/a}}
| {{n/a}}
|-
| 1958
| FORTRAN III
| {{n/a}}
| {{n/a}}
|-
| 1961
| FORTRAN IV
| {{n/a}}
| {{n/a}}
|-
| 1966
| FORTRAN 66
|  X3.9-1966
| {{n/a}}
|-
| 1978
| FORTRAN 77
| X3.9-1978
| {{n/a}}
|-
| 1991
| Fortran 90
| X3.198-1992
| 1539:1991
|-
| 1997
| Fortran 95
| {{n/a}}
| 1539-1:1997
|-
| 2004
| Fortran 2003
| {{n/a}}
| 1539-1:2004
|-
| 2010
| Fortran 2008
| {{n/a}}
| 1539-1:2010
|-
| 2018
| Fortran 2018
| {{n/a}}
| 1539-1:2018
|-
| 2023
| Fortran 2023
| {{n/a}}
| 1539-1:2023
|}
===FORTRAN II===
IBM's ''FORTRAN II'' appeared in 1958.  The main enhancement was to support [[Procedural programming|procedural programming]] by allowing user-written subroutines and functions which returned values with parameters passed by reference.  The COMMON statement provided a way for subroutines to access common (or [[Global variable|global]]) variables. Six new statements were introduced:<ref>{{cite manual|url=http://bitsavers.org/pdf/ibm/704/C28-6000-2_704_FORTRANII.pdf |archive-url=https://web.archive.org/web/20051030200524/http://www.bitsavers.org/pdf/ibm/704/C28-6000-2_704_FORTRANII.pdf |archive-date=October 30, 2005 |url-status=live|title=Reference Manual, FORTRAN II for the IBM 704 Data Processing System|year=1958|id=C28-6000-2}}</ref>
* {{code|SUBROUTINE}}, {{code|FUNCTION}}, and {{code|END}}
* {{code|CALL}} and {{code|RETURN}}
* {{code|COMMON}}

Over the next few years, FORTRAN II added support for the {{code|DOUBLE PRECISION}} and {{code|COMPLEX}} data types.

Early FORTRAN compilers supported no [[Recursion (computer science)|recursion]] in subroutines. Early computer architectures supported no concept of a stack, and when they did directly support subroutine calls, the return location was often stored in one fixed location adjacent to the subroutine code (e.g. the [[Engineering:IBM 1130|IBM 1130]]) or a specific machine register (IBM 360 ''et seq''), which only allows recursion if a stack is maintained by software and the return address is stored on the stack before the call is made and restored after the call returns. Although not specified in FORTRAN 77, many F77 compilers supported recursion as an option, and the [[Burroughs large systems|Burroughs mainframes]], designed with recursion built-in, did so by default. It became a standard in Fortran 90 via the new keyword RECURSIVE.<ref>{{cite web |url= http://www.ibiblio.org/pub/languages/fortran/ch1-12.html |title=Ibibilio.org |publisher=Ibiblio.org |access-date=September 15, 2014}}</ref>

====Simple FORTRAN II program====
This program, for [[Heron's formula]], reads data on a tape reel containing three 5-digit integers A, B, and C as input. There are no "type" declarations available: variables whose name starts with I, J, K, L, M, or N are "fixed-point" (i.e. integers), otherwise floating-point. Since integers are to be processed in this example, the names of the variables start with the letter "I". The name of a variable must start with a letter and can continue with both letters and digits, up to a limit of six characters in FORTRAN II.  If A, B, and C cannot represent the sides of a triangle in plane geometry, then the program's execution will end with an error code of "STOP 1".  Otherwise, an output line will be printed showing the input values for A, B, and C, followed by the computed AREA of the triangle as a floating-point number occupying ten spaces along the line of output and showing 2 digits after the decimal point, the .2 in F10.2 of the FORMAT statement with label 601.

<source lang="fortranfixed">
C AREA OF A TRIANGLE WITH A STANDARD SQUARE ROOT FUNCTION
C INPUT - TAPE READER UNIT 5, INTEGER INPUT
C OUTPUT - LINE PRINTER UNIT 6, REAL OUTPUT
C INPUT ERROR DISPLAY ERROR OUTPUT CODE 1 IN JOB CONTROL LISTING
      READ INPUT TAPE 5, 501, IA, IB, IC
  501 FORMAT (3I5)
C IA, IB, AND IC MAY NOT BE NEGATIVE OR ZERO
C FURTHERMORE, THE SUM OF TWO SIDES OF A TRIANGLE
C MUST BE GREATER THAN THE THIRD SIDE, SO WE CHECK FOR THAT, TOO
      IF (IA) 777, 777, 701
  701 IF (IB) 777, 777, 702
  702 IF (IC) 777, 777, 703
  703 IF (IA+IB-IC) 777, 777, 704
  704 IF (IA+IC-IB) 777, 777, 705
  705 IF (IB+IC-IA) 777, 777, 799
  777 STOP 1
C USING HERON'S FORMULA WE CALCULATE THE
C AREA OF THE TRIANGLE
  799 S = FLOATF (IA + IB + IC) / 2.0
      AREA = SQRTF( S * (S - FLOATF(IA)) * (S - FLOATF(IB)) *
     +     (S - FLOATF(IC)))
      WRITE OUTPUT TAPE 6, 601, IA, IB, IC, AREA
  601 FORMAT (4H A= ,I5,5H  B= ,I5,5H  C= ,I5,8H  AREA= ,F10.2,
     +        13H SQUARE UNITS)
      STOP
      END
</source>

===FORTRAN III===
IBM also developed a ''FORTRAN III'' in 1958 that allowed for [[Inline assembler|inline assembly]] 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.<ref name="history-fortran-i-ii-333"/>{{rp|76}}  Early versions of FORTRAN provided by other vendors suffered from the same disadvantage.

===FORTRAN IV===
IBM began development of FORTRAN IV starting in 1961, as a result of customer demands. ''FORTRAN IV'' removed the machine-dependent features of FORTRAN II (such as {{code|READ INPUT TAPE}}), while adding new features such as a [[Boolean data type|{{code|LOGICAL}} data type]], logical [[Boolean expression]]s 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, IBM 7094, and later for the IBM 1401 in 1966.<ref>{{cite manual|title=Fortran IV Language Specifications, Program Specifications, and Operating Procedures, IBM 1401, 1440, and 1460|url=http://bitsavers.org/pdf/ibm/1401/C24-3322-2_Fortran_IV_Language_Specifications_IBM_1401_1440_1460_Apr66.pdf |archive-url=https://web.archive.org/web/20170923222805/http://www.bitsavers.org/pdf/ibm/1401/C24-3322-2_Fortran_IV_Language_Specifications_IBM_1401_1440_1460_Apr66.pdf |archive-date=September 23, 2017 |url-status=live|date=April 1966|publisher=IBM|id=C24-3322-2}}</ref>

By 1965, FORTRAN IV was supposed to be compliant with the ''standard'' being developed by the American Standards Association X3.4.3 FORTRAN Working Group.<ref name="McCracken">{{cite book|last=McCracken|first=Daniel D.|title=A Guide to FORTRAN IV Programming|chapter-url=https://archive.org/details/guidetofortraniv00mccr|chapter-url-access=registration|year=1965|publisher=Wiley|location=New York|isbn=978-0-471-58281-6|page=v|chapter=Preface}}</ref>

Between 1966 and 1968, IBM offered several FORTRAN IV compilers for its System/360, each named by letters that indicated the minimum amount of memory the compiler needed to run.
<ref>{{cite web
| url = http://www.fortran.bcs.org/2007/jubilee/implementations.php
| title = List of FORTRAN Implementations 1957 – 1967
| publisher = IEEE Annals
| year = 2017
| access-date = October 17, 2017
}}</ref>
The letters (F, G, H) matched the codes used with System/360 model numbers to indicate memory size, each letter increment being a factor of two larger:<ref>{{cite manual|url=http://www.bitsavers.org/pdf/ibm/360/functional_characteristics/A22-6898-1_360-50_funcChar_1967.pdf |archive-url=https://web.archive.org/web/20211029211006/http://bitsavers.org/pdf/ibm/360/functional_characteristics/A22-6898-1_360-50_funcChar_1967.pdf |archive-date=October 29, 2021 |url-status=live|title=IBM System/360 Model 50 Functional Characteristics|publisher=IBM|year=1967|id=A22-6898-1}}</ref>{{rp|p. 5}}
* 1966 : FORTRAN IV F for DOS/360 (64K bytes)
* 1966 : FORTRAN IV G for OS/360 (128K bytes)
* 1968 : FORTRAN IV H for OS/360 (256K bytes)

[[Company:Digital Equipment Corporation|Digital Equipment Corporation]] maintained DECSYSTEM-10 Fortran IV (F40) for [[Engineering:PDP-10|PDP-10]] from 1967 to 1975.<ref name=":0">{{cite web |last1=Digital Equipment Corp |title=DECSYSTEM-10 FORTRAN IV (F40) Programmers Reference Manual |url=https://github.com/PDP-10/f40/blob/master/doc/DEC-10-LFLMA-B-D%20FORTRAN%20IV%20(F40)%20Programmer's%20Reference%20Manual.pdf |website=Github |publisher=Digital Equipment Corporation |access-date=April 15, 2022}}</ref> Compilers were also available for the UNIVAC 1100 series and the [[Company:Control Data Corporation|Control Data]] [[Engineering:CDC 6000 series|6000 series]] and [[CDC 7600|7000 series]] systems.<ref name=":1">{{Cite web |title=FORTRAN IV {{!}} WorldCat.org |url=https://search.worldcat.org/title/20673993 |access-date=2023-12-10 |website=search.worldcat.org |language=en}}</ref>

At about this time FORTRAN IV had started to become an important educational tool and implementations such as the University of Waterloo's WATFOR and [[WATFIV]] were created to simplify the complex compile and link processes of earlier compilers.

==== Overview of FORTRAN IV Programming and compilers====
In the FORTRAN IV programming environment of the era, except for that used on Control Data Corporation (CDC) systems, only one instruction was placed per line. The CDC version allowed for multiple instructions per line if separated by a $ (dollar) character. The FORTRAN [[Engineering:Punched card|sheet]] was divided into four zones:

* Reference: Columns 1 to 5
* Continuation: Column 6
* Variable field: Columns 7 to 72
* Identification: Columns 73 to 80

Order numbers ranging from 1 to 99,999 could be assigned in columns 1 to 5 to identify specific instructions, typically in the case of loops or sequence breaks. Any blanks within these columns were disregarded. Column 1 could also contain a "C," denoting that the entire content of columns 1 to 80 was a comment, reproduced verbatim during compilation without resulting in any real instruction. These were known as "comment cards."

The "continuation column" (Column 6) could hold a digit between 1 and 9 (excluding 0) to indicate that the formula or declaration started on a previous card continued on the current one. Up to 19 continuation cards could be used, and the digits on these cards could be in any order.

In the variable field (Columns 7 to 72), the symbolic instructions of the program were written, with the option to space instructions using blanks, which were ignored by the compiler. To avoid confusion between the letter O and the number zero, the number ZERO was represented by a single 0, and the letter O by a barred O (Ø).

The identification zone, ignored by the compiler, was used for short comments or for numbering program cards. This was particularly useful if the natural order of the cards was accidentally disrupted.

Two compilers of the time, IBM "G" and UNIVAC, allowed comments to be written on the same line as instructions, separated by a special character: "master space": V (perforations 7 and 8) for UNIVAC and perforations 12/11/0/7/8/9 (hexadecimal FF) for IBM. These comments were not to be inserted in the middle of continuation cards.<ref name=":0" /><ref name=":1" />

===FORTRAN 66===
Perhaps the most significant development in the early history of FORTRAN was the decision by the ''American Standards Association'' (now American National Standards Institute (ANSI)) to form a committee sponsored by the Business Equipment Manufacturers Association (BEMA) to develop an ''American Standard Fortran''.  The resulting two standards, approved in March 1966, defined two languages, ''FORTRAN'' (based on FORTRAN IV, which had served as a de facto standard), and ''Basic FORTRAN'' (based on FORTRAN II, but stripped of its machine-dependent features).  The FORTRAN defined by the first standard, officially denoted X3.9-1966, became known as ''FORTRAN 66'' (although many continued to term it FORTRAN IV, the language on which the standard was largely based).  FORTRAN 66 effectively became the first industry-standard version of FORTRAN. FORTRAN 66 included:
* Main program, {{code|SUBROUTINE}}, {{code|FUNCTION}}, and {{code|BLOCK DATA}} program units
* {{code|INTEGER}}, {{code|REAL}}, {{code|DOUBLE PRECISION}}, {{code|COMPLEX}}, and {{code|LOGICAL}} [[Data type|data type]]s
* {{code|COMMON}}, {{code|DIMENSION}}, and {{code|EQUIVALENCE}} statements
* {{code|DATA}} statement for specifying initial values
* [[Intrinsic function|Intrinsic]] and {{code|EXTERNAL}} (e.g., library) functions
* Assignment statement
* {{code|GO TO}}, computed {{code|GO TO}}, assigned {{code|GO TO}}, and {{code|ASSIGN}} statements
* Logical {{code|IF}} and arithmetic (three-way) {{code|IF}} statements
* {{code|DO}} loop statement
* {{code|READ}}, {{code|WRITE}}, {{code|BACKSPACE}}, {{code|REWIND}}, and {{code|ENDFILE}} statements for sequential I/O
* {{code|FORMAT}} statement and assigned format
* {{code|CALL}}, {{code|RETURN}}, {{code|PAUSE}}, and {{code|STOP}} statements
* [[Hollerith constant]]s in {{code|DATA}} and {{code|FORMAT}} statements, and as arguments to procedures
* Identifiers of up to six characters in length
* Comment lines
* {{code|END}} line

===FORTRAN 77===
[[File:Ftn-elim-1240x1709.jpg|thumb|upright|FORTRAN-77 program with compiler output, written on a [[Company:Control Data Corporation|CDC]] [[CDC Cyber|175]] at RWTH Aachen University, Germany, in 1987]]
[[File:4.3 BSD UWisc VAX Emulation f77 Manual.png|thumb|4.3 BSD for the Digital Equipment Corporation (DEC) [[VAX|VAX]], displaying the [[Man page|manual]] for FORTRAN 77 (f77) compiler]]

After the release of the FORTRAN 66 standard, compiler vendors introduced several extensions to ''Standard Fortran'', prompting ANSI committee X3J3 in 1969 to begin work on revising the 1966 standard, under sponsorship of CBEMA, the Computer Business Equipment Manufacturers Association (formerly BEMA).  Final drafts of this revised standard circulated in 1977, leading to formal approval of the new FORTRAN standard in April 1978.  The new standard, called ''FORTRAN 77'' and officially denoted X3.9-1978, added a number of significant features to address many of the shortcomings of FORTRAN 66:

* Block {{code|IF}} and {{code|END IF}} statements, with optional {{code|ELSE}} and {{code|ELSE IF}} clauses, to provide improved language support for [[Structured programming|structured programming]]
* {{code|DO}} loop extensions, including parameter expressions, negative increments, and zero trip counts
* {{code|OPEN}}, {{code|CLOSE}}, and {{code|INQUIRE}} statements for improved I/O capability
* Direct-access file I/O
* {{code|IMPLICIT}} statement, to override implicit conventions that undeclared variables are INTEGER if their name begins with I, J, K, L, M, or N (and REAL otherwise)
* {{code|CHARACTER}} data type, replacing Hollerith strings with vastly expanded facilities for character input and output and processing of character-based data
* {{code|PARAMETER}} statement for specifying constants
* {{code|SAVE}} statement for persistent local variables
* Generic names for intrinsic functions (e.g. {{code|SQRT}} also accepts arguments of other types, such as {{code|COMPLEX}} or {{code|REAL*16}}).
* A set of intrinsics ({{code|LGE, LGT, LLE, LLT}}) for <U>lexical</U> comparison of strings, based upon the [[ASCII]] collating sequence. (These ASCII functions were demanded by the U.S. Department of Defense, in their conditional approval vote.{{Citation needed|date=October 2011}})

In this revision of the standard, a number of features were removed or altered in a manner that might invalidate formerly standard-conforming programs.
''(Removal was the only allowable alternative to X3J3 at that time, since the concept of "[[Deprecation|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 prior standard but rarely used, a small number of specific capabilities were deliberately removed, such as:

* [[Hollerith constant]]s and [[Biography:Herman Hollerith|Hollerith]] data, such as <source lang="fortran" inline>      GREET = 12HHELLO THERE!</source>
* Reading into an H edit (Hollerith field) descriptor in a FORMAT specification
* Overindexing of array bounds by subscripts <source lang="fortranfixed">
      DIMENSION A(10,5)
      Y = A(11,1)
</source>
* Transfer of control out of and back into the range of a DO loop (also known as "Extended Range")

===Transition to ANSI Standard Fortran===
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.

An important practical extension to FORTRAN 77 was the release of MIL-STD-1753 in 1978.<ref>{{cite book
  | last = Mil-std-1753
  | title = DoD Supplement to X3.9-1978
  | publisher = United States Government Printing Office
  | url = http://www.fortran.com/fortran/mil_std_1753.html
  | access-date = December 13, 2007
| archive-url = https://web.archive.org/web/20071109170658/http://www.fortran.com/fortran/mil_std_1753.html
  | archive-date = November 9, 2007
| url-status = dead
  }}</ref> 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.

* {{code|DO WHILE}}, {{code|EXIT}}, {{code|CYCLE}}, and {{code|END DO}} statements
* {{code|INCLUDE}} statement
* {{code|IMPLICIT NONE}} variant of the {{code|IMPLICIT}} statement
* [[Bit manipulation]] intrinsic functions, based on similar functions included in [[Industrial Real-Time Fortran|Industrial Real-Time Fortran (ANSI/ISA S61.1 (1976))]]

The [[Organization:Institute of Electrical and Electronics Engineers|IEEE]] 1003.9 [[POSIX]] Standard, released in 1991, provided a simple means for FORTRAN 77 programmers to issue POSIX system calls.<ref>{{cite book
 |title        = IEEE 1003.9-1992 – IEEE Standard for InformationTechnology – POSIX(R) FORTRAN 77 Language Interfaces – Part 1: Binding for System Application Program Interface (API)
 |url          = https://standards.ieee.org/standard/1003_9-1992.html
 |publisher    = IEEE
 |access-date  = November 24, 2018
}}</ref> Over 100 calls were defined in the document{{snd}} allowing access to POSIX-compatible process control, signal handling, file system control, device control, procedure pointing, and stream I/O in a portable manner.

===Fortran 90===
The much-delayed successor to FORTRAN 77, informally known as ''Fortran 90'' (and prior to that, ''Fortran 8X''), was finally released as ISO/IEC standard 1539:1991 in 1991 and an ANSI Standard in 1992.  In addition to changing the official spelling from FORTRAN to Fortran, this major revision added many new features to reflect the significant changes in programming practice that had evolved since the 1978 standard:

* [[Free-form language|Free-form source input]] removed the need to skip the first six character positions before entering statements.
* Lowercase Fortran keywords
* Identifiers up to 31 characters in length (In the previous standard, it was only six characters).
* 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 <source lang="fortran" inline>X(1:N)=R(1:N)*COS(A(1:N))</source>
** {{code|WHERE}} statement for selective array assignment
** array-valued constants and expressions,
** user-defined array-valued functions and array constructors.
* [[Recursion (computer science)|{{code|RECURSIVE}}]] procedures
* [[Modular programming|Modules]], to group related [[Subroutine|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 [[Type signature|interfaces]] to be checked at compile time
* User-written interfaces for generic procedures
* [[Operator overloading]]
* Derived (structured) data types
* New data type declaration syntax, to specify the data type and other attributes of variables
* [[Dynamic memory allocation]] by means of the {{code|ALLOCATABLE}} attribute and the {{code|ALLOCATE}} and {{code|DEALLOCATE}} statements
* [[Pointer (computer programming)|{{code|POINTER}}]] attribute, pointer assignment, and {{code|NULLIFY}} statement to facilitate the creation and manipulation of dynamic [[Data structure|data structure]]s
* Structured looping constructs, with an {{code|END DO}} statement for loop termination, and {{code|EXIT}} and {{code|CYCLE}} statements for terminating normal {{code|DO}} loop iterations in an orderly way
* {{code|SELECT}} . . . {{code|CASE}} construct for multi-way selection
* Portable specification of numerical precision under the user's control
* New and enhanced intrinsic procedures.

====Obsolescence and deletions====
Unlike the prior revision, Fortran 90 removed no features.<ref>Appendix B.1</ref> Any standard-conforming FORTRAN 77 program was also standard-conforming under Fortran 90, and either standard should have been usable to define its behavior.

A small set of features were identified as "obsolescent" and were expected to be removed in a future standard.  All of the functionalities of these early-version features can be performed by newer Fortran features.  Some are kept to simplify porting of old programs but many were deleted in Fortran 95.
{| class="wikitable sortable"
|+ Obsolescence and deletions
|-
! Obsolescent feature
! Current Status
|-
| Arithmetic IF-statement
| Deleted
|-
| Non-integer DO parameters or control variables
| Deleted
|-
| Shared DO-loop termination or termination with a statement other than END DO or CONTINUE &nbsp;
| Deleted
|-
| Branching to END IF from outside a block
| Deleted
|-
| Alternate return
| Obsolescent
|-
|    PAUSE statement
| Deleted
|-
|    ASSIGN statement and assigned GO TO statement
| Deleted
|-
| Assigned statement numbers and FORMAT specifiers
| Deleted
|-
| H edit descriptors
| Deleted
|-
| Computed GO TO statement
| Obsolescent
|-
| Statement functions
| Obsolescent
|-
| DATA statements among executable statements
| Obsolescent
|-
| CHARACTER* form of CHARACTER declaration
| Obsolescent
|-
| Assumed character length functions
| Obsolescent
|-
| Fixed form source code
| Obsolescent
|}

===="Hello, World!" example====
<source lang="fortran">
program helloworld
     print *, "Hello, World!"
end program helloworld
</source>

===Fortran 95===
''Fortran 95'', published officially as ISO/IEC 1539-1:1997, 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:

* {{code|FORALL}} and nested {{code|WHERE}} constructs to aid vectorization
* User-defined {{code|PURE}} and {{code|ELEMENTAL}} procedures
* Default initialization of derived type components, including pointer initialization
* Expanded the ability to use initialization expressions for data objects
* Initialization of pointers to {{code|NULL()}}
* Clearly defined that {{code|ALLOCATABLE}} arrays are automatically deallocated when they go out of scope.

A number of intrinsic functions were extended (for example a {{code|dim}} argument was added to the {{code|maxloc}} intrinsic).

Several features noted in Fortran 90 to be "obsolescent" were removed from Fortran 95:

* {{code|DO}} statements using {{code|REAL}} and {{code|DOUBLE PRECISION}} index variables
* Branching to an {{code|END IF}} statement from outside its block
* {{code|PAUSE}} statement
* {{code|ASSIGN}} and assigned {{code|GO TO}} statement, and assigned format specifiers
* {{code|H}} Hollerith edit descriptor.

An important supplement to Fortran 95 was the [[Organization:International Organization for Standardization|ISO technical report]] ''TR-15581: Enhanced Data Type Facilities'', informally known as the ''Allocatable TR.''  This specification defined enhanced use of {{code|ALLOCATABLE}} arrays, prior to the availability of fully Fortran 2003-compliant Fortran compilers.  Such uses include {{code|ALLOCATABLE}} arrays as derived type components, in procedure dummy argument lists, and as function return values.  ({{code|ALLOCATABLE}} arrays are preferable to {{code|POINTER}}-based arrays because {{code|ALLOCATABLE}} arrays are guaranteed by Fortran 95 to be deallocated automatically when they go out of scope, eliminating the possibility of [[Memory leak|memory leak]]age.  In addition, elements of allocatable arrays are contiguous, and [[Aliasing (computing)|aliasing]] is not an issue for optimization of array references, allowing compilers to generate faster code than in the case of pointers.<ref>{{cite web|title=Fortran 95 Reference|url=https://gcc.gnu.org/onlinedocs/gcc-4.1.0/gfortran/|publisher=Gnu.Org|access-date=May 10, 2014}}</ref>)

Another important supplement to Fortran 95 was the [[Organization:International Organization for Standardization|ISO]] technical report ''TR-15580: Floating-point exception handling'', informally known as the ''IEEE TR.''  This specification defined support for [[IEEE 754-2008|IEEE floating-point arithmetic]] and [[Floating-point arithmetic|floating-point]] [[Exception handling|exception handling]].

====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 length character strings (ISO/IEC 1539-2 : 2000)
* Conditional compilation (ISO/IEC 1539-3 : 1998)
which, together, compose 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".

==Modern Fortran==

The language defined by the twenty-first century standards, in particular because of its incorporation of [[Object-oriented programming]] support and subsequently [[Coarray Fortran]], is often referred to as 'Modern Fortran', and the term is increasingly used in the literature.<ref>{{cite web |last1=Lionel |first1=Steve |title=Doctor Fortran in "It's a Modern Fortran World" |url=https://stevelionel.com/drfortran/2013/12/30/doctor-fortran-in-its-a-modern-fortran-world/ |website=Intel (was DEC) Fortran forum discussion group |date=December 30, 2013 |publisher=Intel |access-date=April 11, 2022}}</ref>

===Fortran 2003===
''Fortran 2003,'' officially published as ISO/IEC 1539-1:2004, is a major revision introducing many new features.<ref>{{cite web|title=Fortran 2003– Last Working Draft|url=http://www.j3-fortran.org/doc/year/04/04-007.txt|publisher=Gnu.Org|access-date=May 10, 2014}}</ref> A comprehensive summary of the new features of Fortran 2003 is available at the Fortran Working Group (ISO/IEC JTC1/SC22/WG5) official Web site.<ref>{{cite web |title=WG5 Completes Processing Fortran 2003 and the TR |website=nag.co.uk |date=May 14, 2004 |url=http://www.nag.co.uk/sc22wg5/ |archive-url=https://web.archive.org/web/20040805025908/http://www.nag.co.uk/sc22wg5/ |archive-date=August 5, 2004 |access-date=April 3, 2023 }}. It may also be downloaded as a PDF file at {{cite web |title=The New Features of Fortran 2003 |url=https://wg5-fortran.org/N1551-N1600/N1579.pdf |archive-url=https://web.archive.org/web/20180115012047/https://wg5-fortran.org/N1551-N1600/N1579.pdf |archive-date=January 15, 2018 |url-status=live |access-date=April 3, 2023 }}</ref>

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 (object-oriented programming)|inheritance]], polymorphism, dynamic type allocation, and type-bound procedures, providing complete support for [[Abstract data type|abstract data type]]s
* Data manipulation enhancements: allocatable components (incorporating TR 15581), deferred type parameters, {{code|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 {{code|FLUSH}} statement, regularization of keywords, and access to error messages
* [[Function pointer|Procedure pointers]]
* Support for [[IEEE 754-2008|IEEE floating-point arithmetic]] and [[Floating-point arithmetic|floating-point]] [[Exception handling|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 interface|command-line]] arguments, [[Environment variable|environment variable]]s, and processor error messages

An important supplement to Fortran 2003 was the [[Organization:International Organization for Standardization|ISO technical report]] ''TR-19767: Enhanced module facilities in Fortran.''  This report provided ''sub-modules,'' which make Fortran modules more similar to [[Modula-2]] modules.  They are similar to [[Ada (programming language)|Ada]] private child sub-units.  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.

===Fortran 2008===
ISO/IEC 1539-1:2010, informally known as Fortran 2008, was approved in September 2010.<ref>{{cite web|title=N1836, Summary of Voting/Table of Replies on ISO/IEC FDIS 1539-1, Information technology – Programming languages – Fortran – Part 1: Base language|url=https://wg5-fortran.org/N1801-N1850/N1836.pdf |archive-url=https://web.archive.org/web/20180115003040/https://wg5-fortran.org/N1801-N1850/N1836.pdf |archive-date=January 15, 2018 |url-status=live}}</ref><ref>{{cite web|title=Fortran 2008 – Last Working Draft|url=http://www.j3-fortran.org/doc/year/10/10-007.pdf |archive-url=https://web.archive.org/web/20140512222210/http://www.j3-fortran.org/doc/year/10/10-007.pdf |archive-date=May 12, 2014 |url-status=live|publisher=Gnu.Org|access-date=May 10, 2014}}</ref> As with Fortran 95, this is a minor upgrade, incorporating clarifications and corrections to Fortran 2003, as well as introducing some new capabilities.  The new capabilities include:

* Sub-modules – additional structuring facilities for modules; supersedes ISO/IEC TR 19767:2005
* [[Coarray Fortran]] – a parallel execution model
* The [[Scalable parallelism|DO CONCURRENT]] construct – for loop iterations with no interdependencies
* The CONTIGUOUS attribute – to specify storage layout restrictions
* The BLOCK construct – can contain declarations of objects with construct scope
* [[Recursive data type|Recursive allocatable components]] – as an alternative to recursive pointers in derived types

The Final Draft international Standard (FDIS) is available as document N1830.<ref>N1830, Information technology – Programming languages – Fortran – Part 1: Base language [ftp://ftp.nag.co.uk/sc22wg5/N1801-N1850/N1830.pdf]{{dead link|date=January 2016}}</ref>

A supplement to Fortran 2008 is the [[Organization:International Organization for Standardization|International Organization for Standardization]] (ISO) Technical Specification (TS) 29113 on ''Further Interoperability of Fortran with C'',<ref>{{cite ISO standard |csnumber=45136 |title=ISO/IEC TS 29113:2012 – Information technology – Further interoperability of Fortran with C}}</ref><ref>{{cite web|url=https://wg5-fortran.org/N1901-N1950/N1917.pdf |archive-url=https://web.archive.org/web/20180115013236/https://wg5-fortran.org/N1901-N1950/N1917.pdf |archive-date=January 15, 2018 |url-status=live|title=Draft of the Technical Specification (TS) 29113|website=wg5-fortran.org}}</ref> which has been submitted to ISO in May 2012 for approval. The specification adds support for accessing the array descriptor from C and allows ignoring the type and rank of arguments.

===Fortran 2018===
The latest revision of the language (Fortran 2018) was earlier referred to as Fortran 2015.<ref name="Fortran2018name">{{cite web|url=https://software.intel.com/en-us/blogs/2017/11/20/doctor-fortran-in-eighteen-is-the-new-fifteen|title=Doctor Fortran in "Eighteen is the new Fifteen"|publisher=Software.intel.com|access-date=November 20, 2017}}</ref> It is a significant revision and was released on November 28, 2018.<ref name="F2018">{{cite web|url=https://wg5-fortran.org/f2018.html|publisher=ISO|title=Fortran 2018|access-date=November 30, 2018}}</ref>

Fortran 2018 incorporates two previously published Technical Specifications:

* ISO/IEC TS 29113:2012 Further Interoperability with C<ref name="TS29113">{{cite web|url=https://wg5-fortran.org/N1901-N1950/N1942.pdf |archive-url=https://web.archive.org/web/20171201033143/https://wg5-fortran.org/N1901-N1950/N1942.pdf |archive-date=December 1, 2017 |url-status=live|title=Further Interoperability with C|publisher=ISO|access-date=November 20, 2017}}</ref>
* ISO/IEC TS 18508:2015 Additional Parallel Features in Fortran<ref name="TS18508">{{cite web|url=http://isotc.iso.org/livelink/livelink?func=ll&objId=17288706&objAction=Open|title=Additional Parallel Features in Fortran|publisher=ISO|access-date=November 20, 2017}}</ref>

Additional changes and new features include support for ISO/IEC/IEEE 60559:2011 (the version of the [[IEEE 754|IEEE floating-point standard]] before the latest minor revision IEEE {{not a typo|754–2019}}), hexadecimal input/output, IMPLICIT NONE enhancements and other changes.<ref name="F2015newfeat">{{cite web|url=http://isotc.iso.org/livelink/livelink?func=ll&objId=19044944&objAction=Open|publisher=ISO|title=The New Features of Fortran 2015|access-date=June 23, 2017}}</ref><ref name="Fortran2015Closes">{{cite web|url=https://software.intel.com/en-us/blogs/2015/09/04/doctor-fortran-in-one-door-closes|title=Doctor Fortran in "One Door Closes"|publisher=Software.intel.com|access-date=September 21, 2015}}</ref><ref name="Fortran2015">{{cite web|url=http://software.intel.com/en-us/blogs/2013/08/08/doctor-fortran-goes-dutch-fortran-2015|title=Doctor Fortran Goes Dutch: Fortran 2015|publisher=Software.intel.com|access-date=November 19, 2014}}</ref><ref>{{cite manual |url=http://j3-fortran.org/doc/year/18/18-007r1.pdf |title=Fortran 2018 Interpretation Document |date=October 9, 2018}}</ref>

===Fortran 2023===
Fortran 2023 (ISO/IEC 1539-1:2023) was published in November 2023, and can be purchased from the ISO.<ref>{{cite web |title=Fortran 2023 |url=https://wg5-fortran.org/f2023.html |website=wg5-fortran.org |access-date=November 30, 2023}}</ref>

==Language features==
<!--Just link to Fortran 95 language features due to the excessive length of the current article-->

A full description of the Fortran language features brought by Fortran 95 is covered in the related article, ''Fortran 95 language features''. The language versions defined by later standards are often referred to collectively as 'Modern Fortran' and are described in the literature.

==Science and engineering==
[[File:General relativistic magnetohydrodynamic simulation of black hole accretion.jpg|thumb|General relativistic magnetohydrodynamic Fortran simulation of black hole accretion using the BHAC code with cartesian adaptive mesh]]
[[File:Cylinder flow.gif|thumb|Flow around a cylinder computed in Fortran with OpenCL (University of Bristol, UK)]]
[[File:Velocity and sea surface temperature in the oceans.png|thumb|upright|Velocity and sea surface temperature in the oceans, computed with the NEMO Fortran code (Nucleus for European Modeling of the Ocean, https://www.nemo-ocean.eu) in the [[Organization:Barcelona Supercomputing Center|Barcelona Supercomputing Center]] (2020)]]

Although a 1968 journal article by the authors of [[BASIC]] already described FORTRAN as "old-fashioned",<ref name="dtss196810">{{cite journal | url=http://dtss.dartmouth.edu/sciencearticle/index.html | title=Dartmouth Time-Sharing |author1=Kemeny, John G. |author2=Kurtz, Thomas E. | journal=Science | date=October 11, 1968 | volume=162 | issue=3850 | pages=223–228| doi=10.1126/science.162.3850.223 | pmid=5675464 | bibcode=1968Sci...162..223K }}</ref> programs have been written in Fortran for many decades and there is a vast body of Fortran software in daily use throughout the scientific and engineering communities.<ref>{{cite web|last=Phillips|first=Lee|title=Scientific computing's future: Can any coding language top a 1950s behemoth?|url=https://arstechnica.com/science/2014/05/scientific-computings-future-can-any-coding-language-top-a-1950s-behemoth/|website=Ars Technica|date=May 8, 2014 |access-date=May 8, 2014}}</ref> Jay Pasachoff wrote in 1984 that "physics and astronomy students simply have to learn FORTRAN.  So much exists in FORTRAN that it seems unlikely that scientists will change to [[Pascal (programming language)|Pascal]], [[Modula-2]], or whatever."<ref name="pasachoff198404">{{cite news | url=https://archive.org/stream/byte-magazine-1984-04/1984_04_BYTE_09-04_Real-World_Interfacing#page/n403/mode/2up | title=Scientists: FORTRAN vs. Modula-2 | work=BYTE | date=April 1984 | access-date=February 6, 2015 | author=Pasachoff, Jay M. |  pages=404 | type=letter}}</ref> In 1993, Cecil E. Leith called FORTRAN the "mother tongue of scientific computing", adding that its replacement by any other possible language "may remain a forlorn hope".<ref name="Galperin">{{cite book|last=Galperin|first=Boris|title=Large Eddy Simulation of Complex Engineering and Geophysical Flows|year=1993|publisher=Cambridgey|location=London|isbn=978-0-521-43009-8|page=573|chapter=26}}</ref>

It is the primary language for some of the most intensive [[Supercomputer|super-computing]] tasks, such as in [[Astronomy:Astronomy|astronomy]], [[Earth:Climate model|climate model]]ing, computational chemistry, [[Finance:Computational economics|computational economics]], [[Computational fluid dynamics|computational fluid dynamics]], [[Physics:Computational physics|computational physics]], data analysis,<ref>{{Cite book |last=Brandt |first=Siegmund |title=Statistical and Computational Methods in Data Analysis |publisher=North-Holland Publishing Company |date=1970 |isbn=0-7204-2033-4 |pages=Preface }}</ref> hydrological modeling, numerical linear algebra and numerical libraries ([[Software:LAPACK|LAPACK]], [[Software:IMSL Numerical Libraries|IMSL]] and [[Software:NAG Numerical Library|NAG]]), optimization, satellite simulation, [[Engineering:Structural engineering|structural engineering]], and [[Earth:Numerical weather prediction|weather prediction]].<ref>{{Cite book |last=Curcic |first=Milan |url=https://books.google.com/books?id=l2IFEAAAQBAJ&dq=%22fortran%22++weather+prediction&pg=PA5 |title=Modern Fortran: Building efficient parallel applications |date=November 24, 2020 |publisher=Simon and Schuster |isbn=978-1-61729-528-7 }}</ref>  Many of the floating-point benchmarks to gauge the performance of new computer processors, such as the floating-point components of the [[Organization:Standard Performance Evaluation Corporation|SPEC]] benchmarks (e.g., [http://www.spec.org/cpu2006/CFP2006/ CFP2006], [http://www.spec.org/cpu2017/Docs/overview.html#benchmarks CFP2017]) are written in Fortran. Math algorithms are well documented in [[Software:Numerical Recipes|Numerical Recipes]].

Apart from this, more modern codes in computational science generally use large program libraries, such as [[METIS]] for graph partitioning, PETSc or [[Software:Trilinos|Trilinos]] for linear algebra capabilities, [[Software:Deal.II|deal.II]] or [[Software:FEniCS Project|FEniCS]] for mesh and finite element support, and other generic libraries.  Since the early 2000s, many of the widely used support libraries have also been implemented in [[C (programming language)|C]] and more recently, in [[C++]]. On the other hand, high-level languages such as the [[Wolfram Language]], [[Software:MATLAB|MATLAB]], [[Python (programming language)|Python]], and [[R (programming language)|R]] have become popular in particular areas of computational science. Consequently, a growing fraction of scientific programs are also written in such higher-level scripting languages. For this reason, [[Foreign function interface|facilities for inter-operation with C]] were added to Fortran 2003 and enhanced by the ISO/IEC technical specification 29113, which was incorporated into Fortran 2018 to allow more flexible interoperation with other programming languages.

Software for NASA probes [[Astronomy:Voyager 1|Voyager 1]] and [[Astronomy:Voyager 2|Voyager 2]] was originally written in FORTRAN 5, and later ported to FORTRAN 77.  {{as of|2013|9|25|df=US}}, some of the software is still written in Fortran and some has been ported to C.<ref>{{Cite magazine| title = Interstellar 8-Track: How Voyager's Vintage Tech Keeps Running| magazine = WIRED| access-date = December 23, 2017| url = https://www.wired.com/2013/09/vintage-voyager-probes/}}</ref>

==Portability==
Portability was a problem in the early days because there was no agreed upon 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 (programming languages)|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,''<ref>{{cite report |title=Methods to ensure the standardization of FORTRAN software
|quote=PFORT ... Library ...|osti=5361454|publisher=Oak Ridge National Laboratory |last1=Gaffney |first1=P W |last2=Wooten |first2=J W |date=May 1, 1980
}}</ref><ref name="PP4">{{cite book |title=A portable mathematical subroutine library
|volume=57
|pages=165–177
|author=P. A. Fox |date=1977
|quote=PORT ... written in (PFORT) .. ANS Fortran|doi=10.1007/3-540-08446-0_42
|chapter=Port — A portable mathematical subroutine library
|series=Lecture Notes in Computer Science
|isbn=978-3-540-08446-4
}}</ref> it was not until after the 1977 standard, when the National Bureau of Standards (now [[Organization:National Institute of Standards and Technology|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.<ref>{{cite journal | last1=Whitten | first1=Douglas E. | last2=Demaine | first2=Paul A. D. | title=A machine and configuration independent Fortran: Portable Fortran {PFortran} | journal=IEEE Transactions on Software Engineering | publisher=Institute of Electrical and Electronics Engineers (IEEE) | volume=SE-1 | issue=1 | year=1975 | issn=0098-5589 | doi=10.1109/tse.1975.6312825 | pages=111–124 | s2cid=16485156}}</ref><ref>{{cite web |title=Portability Issues
|url=https://www.gnu.org/software/sather/docs-1.2/tutorial/fortran-portability.html
|quote=.. discusses .. portability of .. Fortran}}</ref>

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.<ref name=PP4/> 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-2008|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|preprocessor]].

==Obsolete variants==
Until the Fortran 66 standard was developed, each compiler supported its own variant of Fortran.  Some were more divergent from the mainstream than others.

The first Fortran compiler set a high standard of efficiency for compiled code.  This goal made it difficult to create a compiler so it was usually done by the computer manufacturers to support hardware sales. This left an important niche: compilers that were fast and provided good diagnostics for the programmer (often a student).  Examples include Watfor, Watfiv, PUFFT, and on a smaller scale, FORGO, Wits Fortran, and Kingston Fortran 2.

'''Fortran 5''' was marketed by [[Company:Data General|Data General]] Corp in the late 1970s and early 1980s, for the [[Engineering:Data General Nova|Nova]], [[Engineering:Data General Eclipse|Eclipse]], and MV line of computers.  It had an optimizing compiler that was quite good for minicomputers of its time.  The language most closely resembles FORTRAN 66.

'''FORTRAN V''' was distributed by [[Company:Control Data Corporation|Control Data Corporation]] in 1968 for the [[CDC 6600]] series. The language was based upon FORTRAN IV.<ref name="FIV">{{cite web|url=http://hopl.murdoch.edu.au/showlanguage.prx?exp=1092&language=CDC%20Fortran|title=Towards FORTRAN VI|last=Healy|first=MJR|year=1968|work=Advanced scientific Fortran by CDC|publisher=CDC|pages=169–172|access-date=April 10, 2009|archive-url=https://web.archive.org/web/20090705035806/http://hopl.murdoch.edu.au/showlanguage.prx?exp=1092&language=CDC%20Fortran|archive-date=July 5, 2009|url-status=dead}}</ref>

Univac also offered a compiler for the 1100 series known as FORTRAN V.  A spinoff of Univac Fortran V was Athena FORTRAN.

'''Specific variants''' produced by the vendors of high-performance scientific computers (e.g., [[Company:Burroughs Corporation|Burroughs]], [[Company:Control Data Corporation|Control Data Corporation]] (CDC), [[Company:Cray|Cray]], [[Company:Honeywell|Honeywell]], [[Company:IBM|IBM]], [[Company:Texas Instruments|Texas Instruments]], and [[Engineering:UNIVAC|UNIVAC]]) added extensions to Fortran to take advantage of special hardware features such as [[CPU cache|instruction cache]], CPU [[Pipeline (computing)|pipelines]], and vector arrays.  For example, one of IBM's FORTRAN compilers (''H Extended IUP'') had a level of optimization which reordered the [[Machine code|machine code]] instructions to keep multiple internal arithmetic units busy simultaneously.  Another example is ''CFD'', a special variant of FORTRAN designed specifically for the [[ILLIAC IV]] supercomputer, running at [[Organization:NASA|NASA]]'s Ames Research Center.
IBM Research Labs also developed an extended FORTRAN-based language called ''VECTRAN'' for processing vectors and matrices.

[[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, [[Intel iPSC|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 [[Software:OpenMP|OpenMP]], which is a cross-platform extension for shared memory programming.  One new extension, Coarray Fortran, is intended to support parallel programming.

''[[FOR TRANSIT]]'' was the name of a reduced version of the IBM 704 FORTRAN language,
which was implemented for the IBM 650, using a translator program developed
at Carnegie in the late 1950s.<ref>{{cite manual |title=Internal Translator (IT) A Compiler for the IBM 650
|first1=A. J. |last1=Perlis |first2=J. W. |last2=Smith |first3=H. R. |last3=Van Zoeren |publisher=Computation Center, Carnegie Institute of Technology |url=http://bitsavers.trailing-edge.com/pdf/ibm/650/CarnegieInternalTranslator.pdf |archive-url=https://web.archive.org/web/20121002225726/http://bitsavers.trailing-edge.com/pdf/ibm/650/CarnegieInternalTranslator.pdf |archive-date=October 2, 2012 |url-status=live}}
</ref>
The following comment appears in the IBM Reference Manual (''FOR TRANSIT Automatic Coding System'' C28-4038, Copyright 1957, 1959 by IBM):
<blockquote>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.</blockquote>

The permissible statements were:

* Arithmetic assignment statements, e.g., <code>a = b</code>
* {{code|GO to n}}
* <code>GO TO (n<sub>1</sub>, n<sub>2</sub>, ..., n<sub>m</sub>), i</code>
* <code>IF (a) n<sub>1</sub>, n<sub>2</sub>, n<sub>3</sub></code>
* {{code|PAUSE}}
* {{code|STOP}}
* <code>DO n i = m1, m2</code>
* {{code|CONTINUE}}
* {{code|END}}
* {{code|READ n, list}}
* {{code|PUNCH n, list}}
* {{code|DIMENSION V, V, V, ...}}
* {{code|EQUIVALENCE (a,b,c), (d,c), ...}}

Up to ten subroutines could be used in one program.

FOR TRANSIT statements were limited to columns 7 through 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 coded decimal|bi-quinary]]) arithmetic.  Appendix A of the manual included wiring diagrams for the IBM 533 card reader/punch control panel.

===Fortran-based languages===
Prior to FORTRAN 77, a number of [[Preprocessor|preprocessor]]s 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.  These preprocessors would typically support [[Structured programming|structured programming]], variable names longer than six characters, additional data types, [[Conditional compilation|conditional compilation]], and even [[Macro (computer science)|macro]] capabilities.  Popular preprocessors included [[EFL (programming language)|EFL]], FLECS, [[Iftran|iftran]], [[Mortran|MORTRAN]], SFtran, S-Fortran, [[Ratfor]], and [[Ratfiv]].  Ratfor and Ratfiv, for example, implemented a [[C (programming language)|C]]-like language, outputting preprocessed code in standard FORTRAN 66.  Despite advances in the Fortran language, preprocessors continue to be used for conditional compilation and macro substitution.

One of the earliest versions of FORTRAN, introduced in the '60s, was popularly used in colleges and universities.  Developed, supported, and distributed by the University of Waterloo, [[WATFIV|WATFOR]] was based largely on FORTRAN IV.  A student using WATFOR could submit their batch FORTRAN job and, if there were no syntax errors, the program would move straight to execution.  This simplification allowed students to concentrate on their program's syntax and semantics, or execution logic flow, rather than dealing with submission [[Job Control Language]] (JCL), the compile/link-edit/execution successive process(es), or other complexities of the mainframe/minicomputer environment.  A down side to this simplified environment was that WATFOR was not a good choice for programmers needing the expanded abilities of their host processor(s), e.g., WATFOR typically had very limited access to I/O devices. WATFOR was succeeded by [[WATFIV]] and its later versions.

{{sxhl|2=fortran|1=program; s=0 i=1,n; s=s+1; stop i; s='s'  Stop}}  (line programming)

LRLTRAN was developed at the [[Organization:Lawrence Radiation Laboratory|Lawrence Radiation Laboratory]] to provide support for vector arithmetic and dynamic storage, among other extensions to support systems programming.  The distribution included the LTSS operating system.

The Fortran-95 Standard includes an optional ''Part 3'' which defines an optional [[Conditional compilation|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.

The [[F (programming language)|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 {{code|EQUIVALENCE}} statement.  F retains the array features added in Fortran 90, and removes control statements that were made obsolete by structured programming constructs added to 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".<ref>{{cite web|url=http://www.fortran.com/F/index.html|title=F Programming Language Homepage|publisher=Fortran.com|access-date=November 19, 2014|archive-date=January 9, 2015|archive-url=https://web.archive.org/web/20150109130310/http://www.fortran.com/F/index.html|url-status=dead}}</ref> Essential Lahey Fortran 90 (ELF90) was a similar subset.

Lahey and Fujitsu teamed up to create Fortran for the Microsoft .NET Framework.<ref>{{cite web | url=http://www.lahey.com/lf71/lfnet.htm | title=Fortran for .NET Language System | url-status=dead | archive-url=https://web.archive.org/web/20141018201259/http://www.lahey.com/lf71/lfnet.htm | archive-date=October 18, 2014}}</ref> Silverfrost FTN95 is also capable of creating .NET code.<ref>{{cite web | url=http://www.silverfrost.com/11/ftn95_overview.aspx | title=FTN95: Fortran 95 for Windows|publisher=Silverfrost.com|access-date=November 19, 2014}}</ref>

==Code examples==
The following program illustrates dynamic memory allocation and array-based operations, two features introduced with Fortran 90.  Particularly noteworthy is the absence of {{code|DO}} loops and {{code|IF}}/{{code|THEN}} statements in manipulating the array; mathematical operations are applied to the array as a whole.  Also apparent is the use of descriptive variable names and general code formatting that conform with contemporary programming style.  This example computes an average over data entered interactively.

<source lang="fortran">
program average

  ! Read in some numbers and take the average
  ! As written, if there are no data points, an average of zero is returned
  ! While this may not be desired behavior, it keeps this example simple

  implicit none

  real, dimension(:), allocatable :: points
  integer                         :: number_of_points
  real                            :: average_points, positive_average, negative_average
  average_points   = 0.0
  positive_average = 0.0
  negative_average = 0.0
  write (*,*) "Input number of points to average:"
  read  (*,*) number_of_points

  allocate (points(number_of_points))

  write (*,*) "Enter the points to average:"
  read  (*,*) points

  ! Take the average by summing points and dividing by number_of_points
  if (number_of_points > 0) average_points = sum(points) / number_of_points

  ! Now form average over positive and negative points only
  if (count(points > 0.) > 0) positive_average = sum(points, points > 0.) / count(points > 0.)
  if (count(points < 0.) > 0) negative_average = sum(points, points < 0.) / count(points < 0.)

  ! Print result to terminal stdout unit 6
  write (*,'(a,g12.4)') 'Average = ', average_points
  write (*,'(a,g12.4)') 'Average of positive points = ', positive_average
  write (*,'(a,g12.4)') 'Average of negative points = ', negative_average
  deallocate (points) ! free memory
end program average
</source>

==Humor==
During the same FORTRAN standards committee meeting at which the name "FORTRAN 77" was chosen, a satirical technical proposal was incorporated into the official distribution bearing the title "Letter O [[Considered harmful|Considered Harmful]]".  This 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).  This was considered beneficial in that it would promote structured programming, by making it impossible to use the notorious {{code|GO TO}} statement as before. (Troublesome {{code|FORMAT}} statements would also be eliminated.) It was noted that this "might invalidate some existing programs" but that most of these "probably were non-conforming, anyway".<ref>X3J3 post-meeting distribution for meeting held at Brookhaven National Laboratory in November 1976.</ref>{{unreliable source?|date=August 2014}}<ref>{{cite magazine |title=The obliteration of O |magazine=Computer Weekly |date=March 3, 1977}}</ref>

When X3J3 debated whether the minimum trip count for a DO loop should be zero or one in Fortran 77, Loren Meissner suggested a minimum trip count of two—reasoning ''(tongue-in-cheek)'' that if it was less than two then there would be no reason for a loop!

When assumed-length arrays were being added, there was a dispute as to the appropriate character to separate upper and lower bounds. In a comment examining these arguments, Walt Brainerd penned an article entitled "Astronomy vs. Gastroenterology" because some proponents had suggested using the star or asterisk ("*"), while others favored the colon (":").{{Citation needed|date=July 2016}}

Variable names beginning with the letters I–N have a default type of integer, while variables starting with any other letters defaulted to real, although programmers could override the defaults with an explicit declaration.<ref>{{Cite manual|url=http://docs.oracle.com/cd/E19957-01/805-4939/z40007365fbc/index.html|title=Rules for Data Typing (FORTRAN 77 Language Reference)|access-date=September 29, 2016}}</ref> This led to the joke: "In FORTRAN, GOD is REAL (unless declared INTEGER)."

==See also==

* {{Annotated link |f2c}}
* {{Annotated link |NumPy#F2PY|F2PY}}
* {{Annotated link |FORMAC}}
* {{Annotated link |List of compilers#Fortran compilers|List of Fortran compilers}}
* {{Annotated link |List of numerical libraries#Fortran|List of Fortran numerical libraries}}
* {{Annotated link |List of programming languages}}
* {{Annotated link |Matrix representation}}
* {{Annotated link |Spaghetti code}}

==References==
{{Reflist|refs=
<ref name="Sayre_1956">{{cite book |title=The FORTRAN Automatic Coding System for the IBM 704 EDPM: Programmer's Reference Manual |publisher=Applied Science Division and Programming Research Department, International Business Machines Corporation |location=New York, USA |date=October 15, 1956 |editor-first=David |editor-last=Sayre |author-first1=John Warner |author-last1=Backus |author-first2=R. J. |author-last2=Beeber |author-first3=Sheldon F. |author-last3=Best |author-first4=Richard |author-last4=Goldberg |author-link4=Richard Goldberg |author-first5=Harlan L. |author-last5=Herrick |author-first6=R. A. |author-last6=Hughes |author-first7=L. B. |author-last7=Mitchell |author-first8=Robert A. |author-last8=Nelson |author-first9=Roy |author-last9=Nutt |author-link9=Roy Nutt |author-first10=David |author-last10=Sayre |author-link10=David Sayre |author-first11=Peter B. |author-last11=Sheridan |author-first12=Harold |author-last12=Stern |author-first13=Irving |author-last13=Ziller |pages=2, 19–20 |url=http://archive.computerhistory.org/resources/text/Fortran/102649787.05.01.acc.pdf |access-date=July 4, 2022 |url-status=live |archive-url=https://web.archive.org/web/20220704193549/http://archive.computerhistory.org/resources/text/Fortran/102649787.05.01.acc.pdf |archive-date=July 4, 2022}} (2+51+1 pages)</ref>
}}

==Further reading==
<!--List sections in rough order of "authoritativeness":  Language standards, then related standards, then other reference material, then books, then articles, then all others-->
;Language standards
* {{Cite book
  | last = ANSI x3.9-1966
  | title = USA Standard FORTRAN
  | publisher = American National Standards Institute
  | url = http://www.fh-jena.de/~kleine/history/languages/ansi-x3dot9-1966-Fortran66.pdf
  | access-date = May 5, 2010
| archive-date = May 15, 2011
| archive-url = https://web.archive.org/web/20110515143149/http://www.fh-jena.de/~kleine/history/languages/ansi-x3dot9-1966-Fortran66.pdf
  | url-status = dead
  }} Informally known as FORTRAN 66.
* {{Cite book
  | last = ANSI x3.9-1978
  | title = American National Standard – Programming Language FORTRAN
  | publisher = American National Standards Institute
  | url = http://www.fortran.com/fortran/F77_std/rjcnf.html
  | access-date = December 11, 2007
| archive-url = https://web.archive.org/web/20131029134137/http://www.fortran.com/fortran/F77_std/rjcnf.html
  | archive-date = October 29, 2013
| url-status = dead
  }} Also known as [[Organization:International Organization for Standardization|ISO]] 1539–1980, informally known as FORTRAN 77.
* {{Cite book
  | last = ANSI X3.198-1992 (R1997) / ISO/IEC 1539:1991
  | title = American National Standard – Programming Language Fortran Extended
  | publisher = American National Standards Institute / ISO/IEC
  | url = http://www.iso.org/iso/en/CatalogueDetailPage.CatalogueDetail?CSNUMBER=17366
  | archive-url = https://web.archive.org/web/20020501111055/http://www.iso.org/iso/en/CatalogueDetailPage.CatalogueDetail?CSNUMBER=17366
  | url-status = dead
  | archive-date = May 1, 2002
}} Informally known as Fortran 90.
* {{Cite book
 |last         = ISO/IEC 1539-1:1997
 |title        = Information technology – Programming languages – Fortran – Part 1: Base language
 |url          = http://j3-fortran.org/doc/standing/archive/007/97-007r2/pdf/97-007r2.pdf
 |access-date  = December 13, 2007
|archive-url  = https://web.archive.org/web/20110818190618/http://j3-fortran.org/doc/standing/archive/007/97-007r2/pdf/97-007r2.pdf
 |archive-date = August 18, 2011
|url-status     = dead
}} Informally known as Fortran 95.  There are a further two parts to this standard.  Part 1 has been formally adopted by ANSI.
* {{Cite book
  | last = ISO/IEC 1539-1:2004
  | title = Information technology – Programming languages – Fortran – Part 1: Base language
  | url = http://www.dkuug.dk/jtc1/sc22/open/n3661.pdf
  }} Informally known as Fortran 2003.
* {{Cite book
  | last = ISO/IEC 1539-1:2010 (Final Draft International Standard)
  | title = Information technology – Programming languages – Fortran – Part 1: Base language
  | url = ftp://ftp.nag.co.uk/sc22wg5/N1801-N1850/N1830.pdf
 }} Informally known as Fortran 2008.

;Related standards
* {{Cite journal
  | last = Kneis
  | first = Wilfried
  | title = Draft standard Industrial Real-Time FORTRAN
  | journal = ACM SIGPLAN Notices
  | issn = 0362-1340
  |date=October 1981
  | volume = 16
  | issue = 7
  | pages = 45–60
  | doi = 10.1145/947864.947868
  | title-link = Industrial Real-Time Fortran
  | s2cid = 8662381
 | doi-access = free
  }}
* {{Cite book|title=ISO 8651-1:1988 Information processing systems – Computer graphics – Graphical Kernel System (GKS) language bindings – Part 1: FORTRAN|url=http://www.iso.org/iso/catalogue_detail?csnumber=16024|year=1988|publisher=[[Organization:International Organization for Standardization|ISO]]|location=Geneva, Switzerland}}

;Other reference material
* {{cite book |url=http://www.ecma-international.org/publications/files/ECMA-ST-WITHDRAWN/ECMA-9,%201st%20Edition,%20April%201965.pdf |archive-url=https://web.archive.org/web/20080510103257/http://www.ecma-international.org/publications/files/ECMA-ST-WITHDRAWN/ECMA-9,%201st%20Edition,%20April%201965.pdf |archive-date=May 10, 2008 |url-status=live |title=ECMA Standard on FORTRAN |publisher=European Computer Manufacturers Association |date=April 1965 |access-date=November 17, 2014}}
* {{cite book |url=http://wwwcdf.pd.infn.it/localdoc/f77_sun.pdf |title=FORTRAN 77 4.0 Reference Manual |publisher=Sun Microsystems, Inc. |year=1995 |access-date=November 17, 2014 |archive-date=January 5, 2012 |archive-url=https://web.archive.org/web/20120105170048/http://wwwcdf.pd.infn.it/localdoc/f77_sun.pdf |url-status=dead }}
* {{cite web |url=http://www.atkielski.com/PDF/data/fortran.pdf |title=FORTRAN Coding Form |publisher=[[Company:IBM|IBM]] |access-date=November 17, 2014 |url-status=dead |archive-url=https://web.archive.org/web/20150608095341/http://www.atkielski.com/PDF/data/fortran.pdf |archive-date=June 8, 2015}}
* {{cite book |url=http://www.fh-jena.de/~kleine/history/languages/GC28-6515-10-FORTRAN-IV-Language.pdf |title=IBM System/360 and System/370 Fortran IV Language |publisher=[[Company:IBM|IBM]] |date=May 1974 |access-date=November 17, 2014 |archive-date=April 6, 2011 |archive-url=https://web.archive.org/web/20110406115810/http://www.fh-jena.de/~kleine/history/languages/GC28-6515-10-FORTRAN-IV-Language.pdf |url-status=dead }}
* {{cite web |url=http://michaelgoerz.net/refcards/fortran_refcard_a4.pdf |archive-url=https://web.archive.org/web/20141214225742/http://michaelgoerz.net/refcards/fortran_refcard_a4.pdf |archive-date=December 14, 2014 |url-status=live |title=Modern Fortran Reference Card |last=Goerz |first=Michael |date=2014 |access-date=December 14, 2014}}

;Books
* {{Cite book
  | first1 = Jeanne C.
  | first2 = Walter S.
  | last2  = Brainerd
  | first3 = Richard A.
  | last3  = Hendrickson
  | first4 = Richard E.
  | last4  = Maine
  | first5 = Jeanne T.
  | last5  = Martin
  | first6 =  Brian T.
  | last6  = Smith
  | year = 2009
  | title = The Fortran 2003 Handbook
  | edition = 1st
  | publisher = [[Company:Springer Science+Business Media|Springer]]
  | isbn = 978-1-84628-378-9}}
* {{cite book | last=Akin | first=J. E. | title=Object-oriented programming via Fortran 90/95 | publisher=Cambridge University Press | publication-place=Cambridge, New York | year=2003 | isbn=978-0-521-52408-7 | oclc=49906306}}
* Arjen, Markus (2012), "Modern Fortran in Practice", Cambridge Univ. Press, ISBN 978-1-13908479-6.
* {{cite book | last1=Brainerd | first1=W.S. | last2=Goldberg | first2=C.H. | last3=Adams | first3=J.C. | title=Programmer's Guide to Fortran 90 | publisher=Springer | year=1996 | isbn=978-0-387-94570-5 | edition=3rd}}
* {{cite book | last=Brainerd | first=Walter | title=Guide to Fortran 2008 programming | publisher=Springer | publication-place=London | year=2015 | isbn=978-1-4471-6758-7 | oclc=920530344}}
* {{cite book
  | last      = Chapman
  | first     = Stephen J.
  | date      = 2018
  | title     = Fortran for Scientists and Engineers
  | url       = https://www.mheducation.com/highered/product/fortran-scientists-engineers-chapman/M9780073385891.html
  | edition   = Fourth
  | location  = {{wipe|New York City}}
  | publisher = McGraw-Hill Education
  | pages     = xxiv + 1024
  | isbn      = 978-0-07-338589-1
  }}
* {{Cite book
  | first1 = Ian
  | last1 = Chivers
  | first2 = Jane
  | last2=Sleightholme
  | year = 2018
  | title = Introduction to Programming with Fortran
  | edition = 4th
  | publisher = Springer
  | isbn =  978-3-319-75501-4}}
* {{cite book | last=Clerman | first=Norman | title=Modern Fortran : style and usage | publisher=Cambridge University Press | publication-place=New York | year=2012 | isbn=978-0-521-51453-8 | oclc=776162717}}
* {{cite book | last=Curcic | first=Milan | title=Modern Fortran: building efficient parallel applications | publisher=Manning Publications Company | publication-place=Shelter Island, NY | year=2020 | isbn=978-1-61729-528-7 | oclc=1256806439}}
*{{Cite book
  | first1 = T. M. R.
  | last1 = Ellis
  | first2 = Ivor R.
  | last2 = Phillips
  | first3=Thomas M.
  | last3 = Lahey
  | year = 1994
  | title = Fortran 90 Programming
  | edition = 1st
  | publisher = Addison Wesley
  | isbn = 978-0-201-54446-6}}
* {{Cite book
  | first = D. M.
  | last = Etter
  | year = 1990
  | title = Structured FORTRAN 77 for Engineers and Scientists
  | edition = 3rd
  | publisher = The Benjamin/Cummings Publishing Company, Inc.
  | isbn = 978-0-8053-0051-2
  | url-access = registration
  | url = https://archive.org/details/structuredfortra00ette_0
  }}
* {{Cite book
  | first = J. F.
  | last = Kerrigan
  | year = 1993
  | title = Migrating to Fortran 90
  | edition = 1st
  | publisher = O'Reilly & Associates, Inc.
  | isbn = 1-56592-049-X}}
* {{Cite book
  | first = Michael
  | last = Kupferschmid
  | year = 2002
  | title = Classical Fortran: Programming for Engineering and Scientific Applications
  | publisher = Marcel Dekker (CRC Press)
  | isbn = 978-0-8247-0802-3}}
* {{Cite book|title=Abstracting Away the Machine: The History of the FORTRAN Programming Language (FORmula TRANslation)|last=Lorenzo|first=Mark Jones|publisher=Independently published|year=2019|isbn=978-1082395949}}
* {{Cite book
  | first = Mike
  | last = Loukides
  | year = 1990
  | title = Unix for FORTRAN Programmers
  | publisher = O'Reilly & Associates, Inc
  | location = Sebastopol, CA 95472
  | isbn = 0-937175-51-X}}
* {{Cite book
  | first = Daniel D.
  | last = McCracken
  | year = 1961
  | title = A Guide to FORTRAN Programming
  | url = https://archive.org/details/guidetofortranpr00mccr
  | url-access = registration
  | publisher = Wiley
  | location = New York
  | lccn = 61016618}}
* {{cite book
 | last1=Metcalf
 | first1=Michael
 | last2=Reid
 | first2=John
 | last3=Cohen
 | first3=Malcolm
 | last4=Bader
 | first4=Reinhold
 | title=Modern Fortran explained : incorporating Fortran 2023 | publication-place=Oxford England | year=2023 | isbn=978-0-19-887657-1 | oclc=2023946356}}
* {{Cite book
  | first = Larry
  | last = Nyhoff
  |author2=Sanford Leestma
  | year = 1995
  | title = FORTRAN 77 for Engineers and Scientists with an Introduction to Fortran 90
  | edition = 4th
  | publisher = Prentice Hall
  | isbn = 978-0-13-363003-9}}
* {{Cite book|last=Page|first=Clive G.|title=Professional Programmer's Guide to Fortran77|url=http://www.star.le.ac.uk/~cgp/prof77.html|access-date=May 4, 2010|edition=June 7, 2005|year=1988|publisher=Pitman|location=London|isbn=978-0-273-02856-7}}
* {{Cite book|last=Press|first=William H.|title=Numerical Recipes in Fortran 90: The Art of Parallel Scientific Computing|url=http://www.nrbook.com/a/bookf90pdf.php|year=1996|publisher=Cambridge University Press|location=Cambridge, UK|isbn=978-0-521-57439-6}}
* {{Cite book
  | first1 = Gregory
  | last1  = Ruetsch
  | first2 = Massimiliano
  | last2  = Fatica
  | year = 2013
  | title = CUDA Fortran for Scientists and Engineers
  | edition = 1st
  | publisher = [[Company:Elsevier|Elsevier]]

  | pages = 338
  | isbn = 9780124169708}}
* {{Cite book|last1=Sleighthome|first1=Jane|last2=Chivers|first2=Ian David|title=Interactive Fortran 77: A Hands-On Approach|url=http://www.fortranplus.co.uk/fortran_books.html|edition=2nd|series=Computers and their applications|year=1990|publisher=E. Horwood|location=Chichester|isbn=978-0-13-466764-5|access-date=March 12, 2014|archive-url=https://web.archive.org/web/20140312213359/http://www.fortranplus.co.uk/fortran_books.html|archive-date=March 12, 2014|url-status=dead}}

;Articles
* {{Cite journal|last=Allen|first=F.E.|s2cid=14149353|date=September 1981|title=A History of Language Processor Technology in IBM|journal=IBM Journal of Research and Development|volume=25|issue=5|pages=535–548| doi = 10.1147/rd.255.0535 }}
* {{cite conference|url=http://www.softwarepreservation.org/projects/FORTRAN/paper/BackusEtAl-FortranAutomaticCodingSystem-1957.pdf|title=The FORTRAN Automatic Coding System|conference=Western Joint Computer Conference|pages=188–198|date=February 1957|doi=10.1145/1455567.1455599|author1=J. W. Backus|author2=R. J. Beeber|author3=S. Best|author4=R. Goldberg|author5=L. M. Haibt|author-link5=Lois Haibt|author6=H. L. Herrick|author7=R. A. Nelson|author8=D. Sayre|author-link8=David Sayre|author9=P. B. Sheridan|author10=H. Stern|author11=L. Ziller|author12=R. A. Hughes|author13=R. Nutt|author-link13=Roy Nutt}}
* {{Cite journal|last1=Chivers|first1=Ian D.|first2=Jane|last2=Sleightholme|year=2020|title=Compiler support for Fortran 2008 & 2018 standards| url=https://www.fortranplus.co.uk/fortran-information/}}
* {{Cite journal|year=2011|title=The Seven Ages of Fortran|journal=Journal of Computer Science & Technology|volume=11|issue=1|pages=1–8|url=https://journal.info.unlp.edu.ar/JCST/article/view/681/210|last=Metcalf |first=Michael}}
* {{cite encyclopedia|url=http://hopl.murdoch.edu.au/showlanguage.prx?exp=8&language=FORTRAN |title=FORTRAN – Backus et al high-level compiler (Computer Language) |last=Pigott |first=Diarmuid |year=2006 |encyclopedia=The Encyclopedia of Computer Languages |publisher=Murdoch University |access-date=May 5, 2010 |url-status=dead |archive-url=https://web.archive.org/web/20091008230959/http://hopl.murdoch.edu.au/showlanguage.prx?exp=8&language=FORTRAN |archive-date=October 8, 2009}}
* {{Cite journal|year=1985|title=Design Considerations for IBM Personal Computer Professional FORTRAN, an Optimizing Compiler|journal=IBM Systems Journal|volume=24|issue=1|pages=49–60|last1=Roberts |first1=Mark L. |last2=Griffiths |first2=Peter D. |doi=10.1147/sj.241.0049}}

==External links==
* [https://wg5-fortran.org/ ISO/IEC JTC1/SC22/WG5]—the official home of Fortran standards
* [https://gcc.gnu.org/wiki/GFortranStandards Fortran Standards Documents]—GFortran standards
* [https://fortran-lang.org/ fortran-lang.org] (2020).
* [http://www.softwarepreservation.org/projects/FORTRAN/ History of FORTRAN and Fortran II]—Computer History Museum
* Valmer Norrod, et al.: [https://ntrs.nasa.gov/archive/nasa/casi.ntrs.nasa.gov/19700015982.pdf  ''A self-study course in FORTRAN programing—Volume I—textbook''], Computer Science Corporation El Segundo, California (April 1970). NASA (N70-25287).
* Valmer Norrod, Sheldom Blecher, and Martha Horton: [https://ntrs.nasa.gov/archive/nasa/casi.ntrs.nasa.gov/19700015983.pdf  ''A self-study course in FORTRAN programing—Volume II—workbook''], NASA CR-1478 (April 1970), NASA (N70-25288).
* [https://doku.lrz.de/dyn/Doku_Kurse/Fortran/basics/Fortran_3days.pdf ''An introduction to the Fortran programming language'', by Reinhold Bader, Nisarg Patel, Leibniz Supercomputing Centre].
* [https://github.com/tkoenig1/coarray-tutorial/blob/main/tutorial.md A coarray tutorial]
* [https://fortranwiki.org/fortran/show/Object-oriented+programming Fortran Wiki : Object-oriented programming]
* [https://web.corral.tacc.utexas.edu/CompEdu/pdf/isp/EijkhoutIntroSciProgramming-book.pdf Victor Eijkhout : Introduction to Scientific Programming in C++17/Fortran2008, The Art of HPC, volume 3 (PDF)]

{{Programming languages}}

[[Category:Fortran programming language family| ]]
[[Category:American inventions]]
[[Category:Array programming languages]]
[[Category:Computer standards]]
[[Category:Numerical programming languages]]
[[Category:Object-oriented programming languages]]
[[Category:Procedural programming languages]]
[[Category:High-level programming languages]]
[[Category:Programming languages with an ISO standard]]
[[Category:Statically typed programming languages]]

{{Sourceattribution|Fortran}}