Automatic Preparation of Flow Chart Listings
Journal of the ACM (JACM)
Improving the quality of compiler construction with object-oriented techniques
ACM SIGPLAN Notices
Chronology of Computing Devices
IEEE Transactions on Computers
Universal programming languages and processors: a brief survey and new concepts
AFIPS '65 (Fall, part I) Proceedings of the November 30--December 1, 1965, fall joint computer conference, part I
Programming systems and languages: a historical survey
AFIPS '64 (Spring) Proceedings of the April 21-23, 1964, spring joint computer conference
A technological review of the FORTRAN I compiler
AFIPS '82 Proceedings of the June 7-10, 1982, national computer conference
AFIPS '82 Proceedings of the June 7-10, 1982, national computer conference
Improved optimization of FORTRAN object programs
IBM Journal of Research and Development
Objects and values: the basis of a storage model for procedural languages
IBM Journal of Research and Development
History of IBM's technical contributions to high level programming languages
IBM Journal of Research and Development
The history of language processor technology in IBM
IBM Journal of Research and Development
On revival of Algol-concepts in modern programming and specification languages
Formal methods and hybrid real-time systems
Agent-oriented programming: from prolog to guarded definite clauses
Agent-oriented programming: from prolog to guarded definite clauses
Staged computation with staged lexical scope
ESOP'12 Proceedings of the 21st European conference on Programming Languages and Systems
A quantitative model for software engineering trends
Information Sciences: an International Journal
The quest for runware: on compositional, executable and intuitive models
Software and Systems Modeling (SoSyM)
Hi-index | 0.03 |
The FORTRAN project was begun in the summer of 1954. Its purpose was to reduce by a large factor the task of preparing scientific problems for IBM's next large computer, the 704. If it were possible for the 704 to code problems for itself and produce as good programs as human coders (but without the errors), it was clear that large benefits could be achieved. For it was known that about two-thirds of the cost of solving most scientific and engineering problems on large computers was that of problem preparation. Furthermore, more than 90 per cent of the elapsed time for a problem was usually devoted to planning, writing, and debugging the program. In many cases the development of a general plan for solving a problem was a small job in comparison to the task of devising and coding machine procedures to carry out the plan. The goal of the FORTRAN project was to enable the programmer to specify a numerical procedure using a concise language like that of mathematics and obtain automatically from this specification an efficient 704 program to carry out the procedure. It was expected that such a system would reduce the coding and debugging task to less than one-fifth of the job it had been.