A Common Programming Language for the Depart Final Ment of Defenses-Background and Technical January -December 1975 1 Requirements «

Total Page:16

File Type:pdf, Size:1020Kb

A Common Programming Language for the Depart Final Ment of Defenses-Background and Technical January -December 1975 1 Requirements « Approved for public release; distribution unlimited I 1 PAPER P-1191 A COMMON PROGRAMMING LANGUAGE 1 FOR THE DEPARTMENT OF DEFENSE - - I BACKGROUND AND TECHNICAL REQUIREMENTS I I D. A. Fisher June 1976 I 1 I I I I INSTITUTE FOR DEFENSE ANALYSES I SCIENCE AND TECHNOLOGY DIVISION I I IDA Log No. HQ 76-18215 I Cop-)*- > . -JJ . of 155. cop I ess Approved for public release; distribution unlimited I I I I The work reported in this document was conducted under contract DAHC15 73 C 0200 for the Department of Defense. The publication I of this IDA Paper does not indicate endorsement by the Department of Defense, nor should the contents be construed as reflecting the official position of that agency. I I I I This document has been approved for public release, distribution is unlimited. I I 1 1 1 I I I Copyright IDA/Scanned June 2007 I 1 Approved for public release; distribution unlimited UNCLASSIFIED - ©; ; ; : ;" -; .©, . 1 SECURITY CLASSIFICATION OF THIS PAGE CWnen DM* Entered; READ INSTRUCTIONS REPORT DOCUMENTATION PAGE BEFORE COMPLETING FORM ). RECIPIENT©S CATALOG NUMBER 1 Paper P-J.191. 4. TITLE fend Subtitle.) 5. TYPE Of REPORT e PERIOD COVERED A Common Programming Language for the Depart Final ment of Defenses-Background and Technical January -December 1975 1 Requirements «. PERFORMING ORG. REPORT NUMBER P-1191 I. CONTRACT OR GRANT NUMBERflJ 1 DAHC15 73 C 0200 D.A, Fisher 10. PROGRAM ELEMENT. PROJECT TASK 1 INSTITUTE FOR DEFENSE ANALYSES AREA * WORK UNIT NUMBERS 400 Army-Navy Drive Task T-36 Arlington. Virginia 22202 11. CONTROLLING OFFICE NAME AND ADDRESS 12. REPORT DATE I Defense Advanced Research. Projects Agency June 1976 1400 Wilson Boulevard 0. NUMBER OF PAGES Arlington, Virginia 22209 158 I 14. MONITORING AGENCY NAME * AODRESSfll dilferenl Iron Contralllnt Ollirf) 15. SECURITY CLASS, (ol Ihli report; ODDR&E, Electronics & Physical Sciences UNCLASSIFIED <Se. OE CLASSIFICATION DOWNGRADING I SCHEDULE N/A 16. DISTRIBUTION STATEMENT (ol ffiie R.porl) 1 Approved for public release; distribution unlimited. 1 17. DISTRIBUTION STATEMENT (ol the mbttrmct entered In Block 30. II dl/lerenl from Ripen) None 18. SUPPLEMENTARY NOTES 1 N/A 1». KEY WORDS (-Continue on reverse eide tl neceoery «"d ©dentllx by Woe* number; Embedded Computer Systems (Common), Programming Languages, Software 1 Commonality, Real time, Compilers, Software tools, -Data types, Machine representations, Translators, Control Structures, Syntax, Programming 1 Language Semantics, Programming Language Design Criteria 20. ABSTRACT (Continue on reveree elde II n.c...«ry end Idenlilr b, block number; This paper presents the set of characteristics needed for a ^common programming language of embedded computer systems applications iri the 1 DoD. In addition, it describes the background, purpose, and organization of the DoD Common Programming Language Efforts. It reviews the issues considered in developing the needed language characteristics, explains 1 how certain trade-offs and potential conflicts were resolved, and dis cusses, the criteria used to ensure that any language satisfying the DO , jA*"M7i 1473 "©T© * or © NOV " © o«<»-eTe UNCLASSIFIED 1 SfCURITTcLASSIFICATlON OF THIS PAGE (Ifhen Dele emer.tf) 1 Approved for public release; distribution unlimited UNCLASSIFIED SECURITY CLASSIFICATION OF THIS PAGEfHfian Dmtm Enl*r*d) 20. criteria will be suitable for embedded computer applications, will not aggravate existing software problems, and will be suitable for stan dardization. UNCLASSIFIED SECURITY CLASSIFICATION OF THIS PAGEflWiwi D.f. En(«r.c« 1 Approved for public release; distribution unlimited 1 I Jj PAPER P-1191 | A COMMON PROGRAMMING LANGUAGE FOR THE DEPARTMENT OF DEFENSE - - | BACKGROUND AND TECHNICAL REQUIREMENTS I ft D. A. Fisher I June 1976 t I I I I INSTITUTE FOR DEFENSE ANALYSES SCIENCE AND TECHNOLOGY DIVISION I 400 Army-Navy Drive, Arlington, Virginia 22202 V Contract DAHC15 73 C 0200 Task T-36 I I 1 Approved for public release; distribution unlimited I i i I ABSTRACT This paper presents the set of characteristics needed for i a common programming language of embedded computer systems applications in the DoD. In addition, it describes the back i ground, purpose, and organization of the .DoD Common Programming Language efforts. It reviews the issues considered in developing the needed language characteristics, explains how certain i trade-offs and potential conflicts were resolved, and discusses the criteria used to ensure that any language satisfying the i criteria will be .suitable for embedded computer applications, will not aggravate existing software problems, and will be suitr- t able for standardization. i i i i I i t ill i I Approved for public release; distribution unlimited I I I ACKNOWLEDGMENT The author is pleased to acknowledge the many valuable con tributions and comments from individuals and organizations in i side and outside the Department of Defense. A list of contribu ting organizations and individuals is given as the Appendix, with I apologies to those whose names may have been inadvertently omit ted. Special thanks are deserved by those who took opposing po i sitions and, thereby, exposed fundamental issues. The author is also indebted to Thomas A. Standish and John B, § Goodenough for their reviews and many valuable comments and sug i gestions on this paper. t i i i I i i v t Approved for public release; distribution unlimited f I I- PREFACE This paper was prepared for the Office of the Director of I Defense Research and Engineering (Electronics and Physical Sciences) as Part 1, Software Research and Development, of A Task T-36 (revised), "Evaluations of Options in Electronic Technology". Task T-36 provides independent evaluations of selected areas of electronic technology where the Services are f pursuing different technical approaches to similar problems. Portions of this document have appeared in "Programming I Language Commonality in the Department of Defense", by D. A. Fisher, Defense Management Journal^ Vol. 11, No. 4, (October I (1975), pp. 29-33. I I I I I i vii I I Approved for public release; distribution unlimited f I I CONTENTS I Abstract ill I Acknowledgment v Preface vli Summary 1 A. Background 2 1. The DoD Software Problem 2 2. Character of the DoD Software Environment 3 i 3. Programming Languages in the DoD 6 B. The Common Programming Language Effort of the DoD 7 1. Background 7 i 2. Organization and Method 9 C. Findings . 11 t I. Introduction 17 A. The Problem 18 1. Software Costs 18 i 2. Programming Language 20 3. Lack of Commonality 20 4. Common Language 23 5. Morse Code Experiment . 24 B. Purpose of the Common Programming Language 27 Effort 1. A Common Programming Language 28 f 2. High-Order vs. Low-Level Programming 29 Language C. Other Issues . 33 i 1. Scope 33 2. Application-Oriented Languages 33 3. Effect on Software Expenditures 34 4. Effect on Software and Programming 36 Language R&D 5. Direct Costs of Common-Language Effort 36 6. Standardization 37 i 7. A New Language 38 8. Size 39 9. Priorities , 40 i 10. Consistency 40 11. Committee Design 40 12. Nontechnical Needs .© 4l i ix i Approved for public release; distribution unlimited II. Major Conflicts in Criteria and Needed 43 Characteristics A. Simplicity vs. Specialization 43 B. Programming Ease vs. Safety from Programming © 45 Errors C. Object Efficiency vs. Program Clarity and 46 Correctness D. Machine Independence vs. Machine Dependence 47 E. Generality vs. Specificity 49 III. The Most Pressing Software Problems 51 A. Responsiveness 52 B. Reliability © 52 C. Flexibility/Maintainability 53 D. Excessive Cost 54 E. Timeliness 55 F. Transferability 55 G. Efficiency 56 IV. Language Design Criteria 59 A. Criteria to Satisfy Specialized Application 60 Requirements 1. Flexibility in Software Design Criteria 60 2. Fault-Tolerant Programs 60 3. Machine-Dependent Programs 6l 4. Real-Time Capability 61 5. System-Programming Capability 61 6. Data Base Handling Capability 62 7. Numeric Processing Capability 62 B. Criteria Addressing Existing Software Problems 62 1. Simple Source Language 62 2. Readable/Understandable Programs 64 3- Correct Translator 64 4. Error-Intolerant Translator 64 5. Efficient Object Code - 66 C. Criteria to Assure a Common Programming 67 Language Product 1. Complete Source Language 67 2. Wide Applicability 68 3. Implementable 68 4. Static Design 68 5. Reusability 70 6. A Pedagogical Language 70 V. The Needed Characteristics 71 A. Data and Types 72 B. Operations 76 C. Expressions and Parameters 8l D. Variables, Literals, and Constants . 86 E. Definition Facilities © 91 x i Approved for public release; distribution unlimited I P. Scopes and Libraries , 95 1I G. Control Structures v 99 H. Syntax and Comment Conventions 106 I. Default3^ Conditional Compilation, and 113 , Language Restrictions I J. Efficient Object Representations and 117 ^ Machine Dependencies ^ VI. Characteristics Needed for Other Aspects.of the 123 Common-Language Effort || A. Program Environment 124 B. Translators 12? C. Language Definition, Standards, and Control 132 I References 13?( I Appendix A-l I 1 I I I I i i i i xi i Approved for public release; distribution unlimited I SUMMARY This document, which reports the work of the author in sup port of the DoD Higher Order Language Working Group, is intended to provide the Services with the necessary technical guidelines to achieve their goal of programming language commonality for embedded computer applications in the Department of Defense.* It provides background on the software and programming language 1 problems in the DoD, presents the language design/selection criteria used to guide evaluation of technical characteristics, and identifies the .characteristics needed for the common language. The IDA effort provided the background, analysis, and evalu I ations necessary to reconcile the diverse and sometimes conflict ing perceived needs. It included examination of the purpose and 1 expectations for the Higher Order language effort, review of sev eral technical and managerial issues in selecting a common pro 1 gramming language, and analysis of some important trade-offs in the design/selection criteria and in the choice of language char I acteristics.
Recommended publications
  • Software Tools: a Building Block Approach
    SOFTWARE TOOLS: A BUILDING BLOCK APPROACH NBS Special Publication 500-14 U.S. DEPARTMENT OF COMMERCE National Bureau of Standards ] NATIONAL BUREAU OF STANDARDS The National Bureau of Standards^ was established by an act of Congress March 3, 1901. The Bureau's overall goal is to strengthen and advance the Nation's science and technology and facilitate their effective application for public benefit. To this end, the Bureau conducts research and provides: (1) a basis for the Nation's physical measurement system, (2) scientific and technological services for industry and government, (3) a technical basis for equity in trade, and (4) technical services to pro- mote public safety. The Bureau consists of the Institute for Basic Standards, the Institute for Materials Research, the Institute for Applied Technology, the Institute for Computer Sciences and Technology, the Office for Information Programs, and the ! Office of Experimental Technology Incentives Program. THE INSTITUTE FOR BASIC STANDARDS provides the central basis within the United States of a complete and consist- ent system of physical measurement; coordinates that system with measurement systems of other nations; and furnishes essen- tial services leading to accurate and uniform physical measurements throughout the Nation's scientific community, industry, and commerce. The Institute consists of the Office of Measurement Services, and the following center and divisions: Applied Mathematics — Electricity — Mechanics — Heat — Optical Physics — Center for Radiation Research — Lab- oratory Astrophysics^ — Cryogenics^ — Electromagnetics^ — Time and Frequency*. THE INSTITUTE FOR MATERIALS RESEARCH conducts materials research leading to improved methods of measure- ment, standards, and data on the properties of well-characterized materials needed by industry, commerce, educational insti- tutions, and Government; provides advisory and research services to other Government agencies; and develops, produces, and distributes standard reference materials.
    [Show full text]
  • Edsger W. Dijkstra: a Commemoration
    Edsger W. Dijkstra: a Commemoration Krzysztof R. Apt1 and Tony Hoare2 (editors) 1 CWI, Amsterdam, The Netherlands and MIMUW, University of Warsaw, Poland 2 Department of Computer Science and Technology, University of Cambridge and Microsoft Research Ltd, Cambridge, UK Abstract This article is a multiauthored portrait of Edsger Wybe Dijkstra that consists of testimo- nials written by several friends, colleagues, and students of his. It provides unique insights into his personality, working style and habits, and his influence on other computer scientists, as a researcher, teacher, and mentor. Contents Preface 3 Tony Hoare 4 Donald Knuth 9 Christian Lengauer 11 K. Mani Chandy 13 Eric C.R. Hehner 15 Mark Scheevel 17 Krzysztof R. Apt 18 arXiv:2104.03392v1 [cs.GL] 7 Apr 2021 Niklaus Wirth 20 Lex Bijlsma 23 Manfred Broy 24 David Gries 26 Ted Herman 28 Alain J. Martin 29 J Strother Moore 31 Vladimir Lifschitz 33 Wim H. Hesselink 34 1 Hamilton Richards 36 Ken Calvert 38 David Naumann 40 David Turner 42 J.R. Rao 44 Jayadev Misra 47 Rajeev Joshi 50 Maarten van Emden 52 Two Tuesday Afternoon Clubs 54 2 Preface Edsger Dijkstra was perhaps the best known, and certainly the most discussed, computer scientist of the seventies and eighties. We both knew Dijkstra |though each of us in different ways| and we both were aware that his influence on computer science was not limited to his pioneering software projects and research articles. He interacted with his colleagues by way of numerous discussions, extensive letter correspondence, and hundreds of so-called EWD reports that he used to send to a select group of researchers.
    [Show full text]
  • User's Manual for the ALCR-ILLINIS-7090 ALGL-60
    •::../. ; '-> v.- V. -V.' skss Hi *lSn i'-fh B£H*wffi H HI BBfiffli? •LN. fln WW* WSMmm Ml H II B RAI^Y OF THE UN IVLRSITY Of ILLINOIS SlO.84 XSibus 1964 The person charging this material is re- sponsible for its return on or before the Latest Date stamped below. Theft, mutilation, and underlining of books are reasons for disciplinary action and may result in dismissal from the University. University of Illinois Library i 1970 LI61— O-10Q6 Digitized by the Internet Archive in 2013 http://archive.org/details/usersmanualforalOOuniv »" DIGITAL COMPUTER LABORATORY GRADUATE COLLEGE UNIVERSITY OF ILLINOIS User's Manual for the ALCpR-ILLIN0IS-7O9O ALG0L-6O Translator University of Illinois 2nd Edition Manual Written and Revised by R. Bayer E. Murphree, Jr. D. Gries September 28, I96U . : Preface In June, 19^2, by arrangement between the University of Illinois and the ALCOR group in Europe, Dr. Manfred Paul, Johannes Gutenberg Universitat, Mainz, and Dr. Rudiger Wiehle, Munchen Technische Hochschule, Munich, began the design of the ALC0R-ILLIN0IS-7O9O ALGOL-60 Translator, the use of which is described in this Manual. They were joined in July, I962, by David Gries and the writer and later by Michael Rossin, Theresa Wang and Rudolf Bayer, all graduate students at the University of Illinois This manual is an effort to explain the differences which exist between publication ALGOL-60 as it is defined by the Revised Report on the Algorithmic Language ALGOL-60 (as published in the January I963 issue of Communications of the Association for Computing Machinery) and as it actually has been implemented by the group named above, Relatively few features of ALGOL-60 have not been implemented, so this manual consists mostly of an explanation of the "hardware" representation of true ALGOL rather than deviations from it.
    [Show full text]
  • A Static Analysis Framework for Security Properties in Mobile and Cryptographic Systems
    A Static Analysis Framework for Security Properties in Mobile and Cryptographic Systems Benyamin Y. Y. Aziz, M.Sc. School of Computing, Dublin City University A thesis presented in fulfillment of the requirements for the degree of Doctor of Philosophy Supervisor: Dr Geoff Hamilton September 2003 “Start by doing what’s necessary; then do what’s possible; and suddenly you are doing the impossible” St. Francis of Assisi To Yowell, Olivia and Clotilde Declaration I hereby certify that this material, which I now submit for assessment on the programme of study leading to the award of the degree of Doctor of Philosophy (Ph.D.) is entirely my own work and has not been taken from the work of others save and to the extent that such work has been cited and acknowledged within the text of my work. Signed: I.D. No.: Date: Acknowledgements I would like to thank all those people who were true sources of inspiration, knowledge, guidance and help to myself throughout the period of my doctoral research. In particular, I would like to thank my supervisor, Dr. Geoff Hamilton, without whom this work would not have seen the light. I would also like to thank Dr. David Gray, with whom I had many informative conversations, and my colleagues, Thomas Hack and Fr´ed´ericOehl, for their advice and guidance. Finally, I would like to mention that the work of this thesis was partially funded by project IMPROVE (Enterprise Ireland Strategic Grant ST/2000/94). Benyamin Aziz Abstract We introduce a static analysis framework for detecting instances of security breaches in infinite mobile and cryptographic systems specified using the languages of the π-calculus and its cryptographic extension, the spi calculus.
    [Show full text]
  • Education in Programming David Gries Dr. Rer. Nat., Munich Institute
    Education in Programming David Gries Dr. rer. nat., Munich Institute of Technology, 1966 Computer Science, Cornell University, Ithaca, NY 1 1 A Glimerick of Hope David Gries, 1995 Abstract Well I got my degree at that place The world is turning to C, And my ancestors came from that race Though at best it is taught awkwardly, Though Great New York C But we don’t have to mope, Was the Birthplace of me There’s a glimmer of hope, And CS at Cornell is my base. In the methods of formality President Mary of Eire So I don't have a real PhD. Was supposed to come to regale ya. It's the Dr. Rer. Nat. that's for me. But matters of State And it's from MIT Made her cancel that date --On your side of the sea So you’re stuck with this guy from Bavaria Munich Inst. of Technolology 2 2 In 1962–63, in Illinois writing the ALCOR-ILLINOIS 7090 ALGOL Compiler I came to Munich to get a PhD (and finish the compiler) Manfred Paul Rudiger Wiehle Elaine and David Gries 3 3 Instrumental in the development of programming languages and their implementation A early as 1952, Bauer: Keller principle Influential in development of Algol 60 Educate the next generation of computer scientists 1968 and 1969 NATO Conferences on Software Engineering (Garmisch and Rome) 4 4 1968 and 1969 NATO Conferences Software Engineering (Garmisch and Rome) 5 5 1968 and 1969 NATO Conferences Software Engineering (Garmisch and Rome) 6 6 Instrumental in the development of programming languages and their implementation Educate the next generation of computer scientists 1968 and 1969 NATO Conferences on Software Engineering (Garmisch and Rome) The Marktoberdorf Summer Schools now led ably by Manfred Broy 7 7 The teaching of programming simplicity elegance perfection intellectual honesty Edsger W.
    [Show full text]
  • Introduction to the Literature on Programming Language Design Gary T
    Computer Science Technical Reports Computer Science 7-1999 Introduction to the Literature On Programming Language Design Gary T. Leavens Iowa State University Follow this and additional works at: http://lib.dr.iastate.edu/cs_techreports Part of the Programming Languages and Compilers Commons Recommended Citation Leavens, Gary T., "Introduction to the Literature On Programming Language Design" (1999). Computer Science Technical Reports. 59. http://lib.dr.iastate.edu/cs_techreports/59 This Article is brought to you for free and open access by the Computer Science at Iowa State University Digital Repository. It has been accepted for inclusion in Computer Science Technical Reports by an authorized administrator of Iowa State University Digital Repository. For more information, please contact [email protected]. Introduction to the Literature On Programming Language Design Abstract This is an introduction to the literature on programming language design and related topics. It is intended to cite the most important work, and to provide a place for students to start a literature search. Keywords programming languages, semantics, type systems, polymorphism, type theory, data abstraction, functional programming, object-oriented programming, logic programming, declarative programming, parallel and distributed programming languages Disciplines Programming Languages and Compilers This article is available at Iowa State University Digital Repository: http://lib.dr.iastate.edu/cs_techreports/59 Intro duction to the Literature On Programming Language Design Gary T. Leavens TR 93-01c Jan. 1993, revised Jan. 1994, Feb. 1996, and July 1999 Keywords: programming languages, semantics, typ e systems, p olymorphism, typ e theory, data abstrac- tion, functional programming, ob ject-oriented programming, logic programming, declarative programming, parallel and distributed programming languages.
    [Show full text]
  • David Gries Advisory Board F.L
    Texts and Monographs in Computer Science Editor David Gries Advisory Board F.L. Bauer S.D. Brookes C.E. Leiserson F. B. Schneider M. Sipser Texts and Monographs in Computer Science Suad Alagie Object-oriented Database Programming 1989. XV, 320pages,84 illus. Suad Alagie Relational Database Technology 1986. XI, 259pages, 114ilIus. Suad Alagie and MichaelA. Arbib The Design of Well-Structured and Correct Programs 1978. X, 292pages,68 illus. S. Thomas Alexander Adaptive Signal Processing: Theory and Applications 1986. IX, 179pages,42 illus. MichaelA. Arbib, AJ. Kfoury, and Robert N. Moll A Basis for Theoretical Computer Science 1981. VIII, 220pages,49 iIlus. Friedrich L. Bauer and Hans Wossner Algorithmic Language and Program Development 1982. XVI, 497pages, 109 ilIus. Kaare Christian A Guide to Modula·2 1986. XIX, 436pages,46 ilIus. Edsger W. Dijkstra Selected Writings on Computing: A Personal Perspective 1982. XVII, 362pages, 13 illus. Edsger W. Dijkstra and Carel S. Schoiten Predicate Calculus and Program Semantics 1990. XII, 220pages W.HJ. Feijen,AJ.M. van Gasteren, D. Gries, and J. Misra, Eds. Beauty Is Our Business: A Birthday Salute to Edsger W. Dijkstra 1990. XX, 453pages,21 ilIus. MelvinFitting First-order Logic and Automated Theorem Proving 1990. XIV, 242pages,26 illus. Nissim Francez Fairness 1986. XIII, 295pages, 147illus. continued afterindex Beauty Is Our Business A Birthday Salute to Edsger W. Dijkstra Edited by W.H.J. Feijen A.J.M. van Gasteren D. Gries J. Misra Springer-Verlag New York Berlin Heidelberg London Paris Tokyo Hong Kong W.H.J. Feijen A.J .M. van Gasteren Mathematics and Computer Science Department Department of Computer Science Eindhoven University of Technology University of Utrecht 5600 MB Eindhoven 3508 TB Ut recht The Net herlands The Netherlands D.
    [Show full text]
  • Hartmanis Transcript Final
    A. M. Turing Award Oral History Interview with Juris Hartmanis by David Gries Cornell University, Ithaca, NY May 17, 2018 Gries: Good morning! I’m David Gries, Professor Emeritus of Computer Science at Cornell University, although I’m still teaching. I’m here to interview the other professor of computer science at Cornell, my friend and colleague since 1969 when I came to Cornell, Juris Hartmanis. Juris received the ACM Turing Award in 1993. Let me read the citation to you. “With Richard E. Stearns, in recognition of their seminal paper which established the foundations for the field of computational complexity theory. In their paper ‘On the Computational Complexity of Algorithms’ they provided a precise definition of the complexity measure defined by computation time on Turing machines and developed a theory of complexity classes. The paper sparked the imagination of many computer scientists and led to the establishment of complexity theory as a fundamental part of the discipline.” That’s why we often call Juris “the father of computational complexity.” Juris wears another hat. In 1965, he became the first chair of the newly formed computer science department here at Cornell. He’s largely responsible for its development. It is due to his vision and leadership that it became one of the top five CS departments in the US. Juris is a member of the National Academy of Engineering, the American Academy of Arts and Sciences, the Latvian Academy of Science, and more. He has two honorary doctorates. Two other of his awards, the Bolzano Gold Medal from the Academy of Sciences in the Czech Republic and the CRA Distinguished Service Award, CRA being the Computing Research Association.
    [Show full text]
  • A Bibliography of Publications of Friedrich Ludwig Bauer
    A Bibliography of Publications of Friedrich Ludwig Bauer Nelson H. F. Beebe University of Utah Department of Mathematics, 110 LCB 155 S 1400 E RM 233 Salt Lake City, UT 84112-0090 USA Tel: +1 801 581 5254 FAX: +1 801 581 4148 E-mail: [email protected], [email protected], [email protected] (Internet) WWW URL: http://www.math.utah.edu/~beebe/ 30 January 2021 Version 1.02 Abstract This bibliography records publications of Friedrich Ludwig Bauer (10 June 1924–26 March 2015). Title word cross-reference 2p−1 ≡ 3 π $24.50 [G.70]. 3; ( p−1 ) 1 (mod p ) [Bau88]. e [Bau07c, Bau07c]. g [Bau60b]. π [Bau05a]. π(x) [Bau03d]. πe [Bau07c]. QR [RB68]. -algorithm [Bau60b]. 1 [Bau05c, Bau06d]. 105 [BS62c]. 10th [BS81]. 11 [BGHS79]. 11/27/1978 [BGHS79]. 135 [Sch69]. 153 [Bau63a]. 17-Eck [BH08]. 17-gon [BH08]. 1905 [Bau05c, Bau06d]. 1945 [Bau08b]. 1960 [AGG60]. 1964 [Ghi10]. 1971 [Dij71]. 1972 [BW72a]. 1973 [Bau75a]. 1978 [BGHS79]. 1980 [GB81]. 1988 [Bau89b]. 1989 [Bau91a]. 1990 [Bau90c]. 1991 [BBS93]. 1999 [BS00]. 1 2 2001 [Bau01a]. 2007 [Bau07e]. 20th [BS00]. 22.8.1970 [GB71]. 25.5.1980 [GB81]. 28/29 [BD01]. 292 [Chu51]. 3 [Bau95a, Leh87]. 3-211-82527-4 [Bau95a]. 3-540-13814-5 [Leh87]. 300th [Bau07c, Bau07g]. 310447Theoretische [Bau95a]. 314 [Cul72b].ˇ 367 [Cul72a].ˇ 4 [Bau95a]. 4/21/1909 [BGHS79]. 5 [Leh87]. 50 [Gep66]. 60 [BBG+60, BBG+63c, BBG+63a, BBG+76, Bau61a, BHO+67, Cul72b,ˇ Cul72a,ˇ Gep66, GHL67, NBB+60, NBB+62, NBB+63, NBB+65, NBB+97]. 68 [vWMPK69b, vWMPK69a]. 80 [Ano04, Bod04, Hei68, Kad76].
    [Show full text]
  • Structured Programming - Retrospect and Prospect
    University of Tennessee, Knoxville TRACE: Tennessee Research and Creative Exchange The Harlan D. Mills Collection Science Alliance 11-1986 Structured Programming - Retrospect and Prospect Harlan D. Mills Follow this and additional works at: https://trace.tennessee.edu/utk_harlan Part of the Software Engineering Commons Recommended Citation Mills, Harlan D., "Structured Programming - Retrospect and Prospect" (1986). The Harlan D. Mills Collection. https://trace.tennessee.edu/utk_harlan/20 This Article is brought to you for free and open access by the Science Alliance at TRACE: Tennessee Research and Creative Exchange. It has been accepted for inclusion in The Harlan D. Mills Collection by an authorized administrator of TRACE: Tennessee Research and Creative Exchange. For more information, please contact [email protected]. mJNDAMNTL9JNNEPTS IN SOFTWARE ENGINEERING Structured Programming. Retrospect and Prospect Harlan D. Mills, IBM Corp. Stnuctured program- 2 ' dsger W. Dijkstra's 1969 "Struc- mon wisdom that no sizable program Ste red .tured Programming" articlel could be error-free. After, many sizable ming haxs changed ho w precipitated a decade of intense programs have run a year or more with no programs are written focus on programming techniques that has errors detected. since its introduction fundamentally alteredhumanexpectations and achievements in software devel- Impact of structured programming. two decades ago. opment. These expectations and achievements are However, it still has a Before this decade of intense focus, pro- not universal because of the inertia of lot of potentialfor gramming was regarded as a private, industrial practices. But they are well- lot of fo puzzle-solving activity ofwriting computer enough established to herald fundamental more change.
    [Show full text]
  • Introduction to the Literature on Programming Language Design Gary T
    Computer Science Technical Reports Computer Science 2-1996 Introduction to the Literature on Programming Language Design Gary T. Leavens Iowa State University Follow this and additional works at: http://lib.dr.iastate.edu/cs_techreports Part of the Other Computer Sciences Commons, and the Programming Languages and Compilers Commons Recommended Citation Leavens, Gary T., "Introduction to the Literature on Programming Language Design" (1996). Computer Science Technical Reports. 99. http://lib.dr.iastate.edu/cs_techreports/99 This Article is brought to you for free and open access by the Computer Science at Iowa State University Digital Repository. It has been accepted for inclusion in Computer Science Technical Reports by an authorized administrator of Iowa State University Digital Repository. For more information, please contact [email protected]. Introduction to the Literature on Programming Language Design Abstract This is an introduction to the literature on programming language design and related topics. It is intended to cite the most important work, and to provide a place for students to start a literature search. Keywords programming languages, semantics, type systems, polymorphism, type theory, data abstraction, functional programming, object-oriented programming, logic programming, declarative programming, parallel and distributed programming languages Disciplines Other Computer Sciences | Programming Languages and Compilers Comments © Gary T. Leavens. Permission is granted for you to make copies for educational and scholarly purposes, but not for direct commercial advantage, provided this notice appears on all copies. All other rights reserved. This article is available at Iowa State University Digital Repository: http://lib.dr.iastate.edu/cs_techreports/99 Intro duction to the Literature On Programming Language Design Gary T.
    [Show full text]
  • Differential Equations
    Notices of the American Mathematical Society Special Issue Assistantships and Fellowships in the Mathematical Sciences 1985-1986 December 1984, Issue 238 Volume 31, Number 8, Pages 841-944 Providence, Rhode Island USA ISSN 0002-9920 The Mathematical Heritage of HENRI POINCARE Felix Browder, Editor PART 1 § 1. Geometry Shing-Shen Chern Jun-lchi lgusa John Milnor Ngaiming Mok and Shing-Tung Yau Alan Weinstein §2. Topology J. Frank Adams William P. Thurston §3. Riemann surfaces, discontinuous groups and Lie groups Lipman Bers Wilfried Schmid Dennis Sullivan §4. Several complex variables Michael Beals, Charles Fefferman and Robert Grossman Phillip A. Griffiths Roger Penrose R. 0. Wells, Jr. PART 2 §5. Topological methods in nonlinear problems Raoul Bott Ha"im Brezis Felix Browder L. Nirenberg §6. Mechanics and dynamical systems Jean Leray David Ruelle Steve Smale PROCEEDINGS OF SYMPOSIA § 7. Ergodic theory and recurrence IN PURE MATHEMATICS Volume 39 Harry Furstenberg Y. Katznelson and D. Ornstein PSPUM/39.1: Part 1, x + 439 pages. List $42, Institutional §8. Historical material member $34, Individual member $25 PSPUM/39.2: Part 2, vi + 470 pages. List $42, Institutional P. S. Aleksandrov member $34, Individual member $25 Henri Poincare PSPUM/39: Two volume set. List $79, Institutional member Jacques Hadamard $63, Individual member $47 Lettre de M. Pierre Boutroux a M. Mittag-Leffler Bibliography of Henri Poincare Books and articles about Poincare Shipping/Handling: 1st book $2, each add'l $1, max. $25; by air, 1st book $5, each add'l $3, max. $100 Prepayment is required. Order from American Mathematical Society, P.O. Box 1571, Annex Station, Providence, Rl 02901-1571, or call toll free 800-556-7774 to charge with Visa or MasterCard.
    [Show full text]