Chapter 2. 5 * B => A V 6 7 (subscripts) S 1.n 1.n (data types)

Similar documents
2. Evolution of the Major Programming languages

Chapter 2. Chapter 2

Chapter 2. Pseudocodes: Speedcoding. 2.2 Minimal Hardware Programming: Pseudocodes. Evolution of the Major Programming Languages

Introduction. A. Bellaachia Page: 1

Chapter 2. Evolution of the Major Programming Languages ISBN

Evolution of the Major Programming Languages

Chapter 2 Evolution of the Major Programming Languages Chapter 2 Topics

Chapter 2. Evolution of the Major Programming Languages

Chapter 2. Evolution of the Major Programming Languages ISBN

8/23/18. Programming Language Genealogy The Evolution of Programming Languages. Zuse s Plankalkül. Plankalkül Syntax. Machine Code

Chapter 2. Evolution of the Major Programming Languages

Lecture 09. Ada to Software Engineering. Mr. Mubashir Ali Lecturer (Dept. of Computer Science)

Page # CSCI: 4500/6500 Programming Languages. Programming Paradigm: Imperative. Programming Paradigm: Declarative. First General Purpose Machine

History of Programming Languages

CS508-Modern Programming Solved MCQ(S) From Midterm Papers (1 TO 22 Lectures) BY Arslan

Evolution of PL s. EECS 476, Prog. Lang. Design/ page 1

Language Translation, History. CS152. Chris Pollett. Sep. 3, 2008.

8/27/17. CS-3304 Introduction. What will you learn? Semester Outline. Websites INTRODUCTION TO PROGRAMMING LANGUAGES

Comp 333: Concepts of Programming Languages Fall 2016

Lecture 2. A Historical View

General Concepts. Abstraction Computational Paradigms Implementation Application Domains Influence on Success Influences on Design

Programming Languages, Summary CSC419; Odelia Schwartz

Unit-1. Evaluation of programming languages:

Programming Languages CMSC 4023 Chapter 2

CS 430 Spring History of Programming Languages. Mike Lam, Professor. John McCarthy ( ) Inventor of LISP

Continuations provide a novel way to suspend and reexecute

Chapter 1. Preliminaries

Chapter 5 Names, Binding, Type Checking and Scopes

R13 SET Discuss how producer-consumer problem and Dining philosopher s problem are solved using concurrency in ADA.

Imperative Programming

COSC 2P90 Programming Languages & Object-Orientation

CSCI.4430/6969 Programming Languages Lecture Notes

Chapter 2 Preview. Preview. History of Programming Languages. History of Programming Languages. History of Programming Languages

Programming Paradigms

Why study Programming Language Concepts? Chapter One. Language Evaluation Criteria. Programming Domains. Readability Writability Reliability Cost

Software II: Principles of Programming Languages

Introduction Primitive Data Types Character String Types User-Defined Ordinal Types Array Types. Record Types. Pointer and Reference Types

Programming Languages 1. Introduction. Oscar Nierstrasz

Logic Programming II & Revision

1/14/2014. Introduction to CSE 1325 Object Oriented Programming (Using Java) Introduction (Cont.) Introduction

CSC 326H1F, Fall Programming Languages. What languages do you know? Instructor: Ali Juma. A survey of counted loops: FORTRAN

Chapter 5 Names, Bindings, Type Checking, and Scopes

Languages october 22, 2017 Éric Lévénez < FORTRAN III end-1958 FORTRAN II FORTRAN I october 1956

Concepts of Programming Languages

Topic IV. Parameters. Chapter 5 of Programming languages: Concepts & constructs by R. Sethi (2ND EDITION). Addison-Wesley, 1996.

Chapter 7. - FORTRAN I control statements were based directly on IBM 704 hardware

St. MARTIN S ENGINEERING COLLEGE Dhulapally, Secunderabad

Topic IV. Block-structured procedural languages Algol and Pascal. References:

1. true / false By a compiler we mean a program that translates to code that will run natively on some machine.

Fundamentals of Programming Languages. PL families Lecture 02 sl. dr. ing. Ciprian-Bogdan Chirila

LECTURE 18. Control Flow

PLAGIARISM. Administrivia. Course home page: Introduction to Programming Languages and Compilers

Introduction to Programming Languages and Compilers. CS164 11:00-12:00 MWF 306 Soda

CMSC 331 Final Exam Section 0201 December 18, 2000

Topic I. Introduction and motivation References: Chapter 1 of Concepts in programming languages by J. C. Mitchell. CUP, 2003.

Principles of Programming Languages. Lecture Outline

Introduction to Computers, the Internet and the Web Pearson Education, Inc. All rights reserved.

NOTE: Answer ANY FOUR of the following 6 sections:

Concepts in Programming Languages

Chapter 5. Names, Bindings, and Scopes

Design Issues. Subroutines and Control Abstraction. Subroutines and Control Abstraction. CSC 4101: Programming Languages 1. Textbook, Chapter 8

Chapter 1. Preliminaries

Introduction to Programming

Question No: 1 ( Marks: 1 ) - Please choose one One difference LISP and PROLOG is. AI Puzzle Game All f the given

Organization of Programming Languages (CSE452) Why are there so many programming languages? What makes a language successful?

Computer Fundamentals: Pradeep K. Sinha & Priti Sinha

Low-Level Languages. Computer Programs and Programming Languages

Com S 541. Programming Languages I

Outline. Programming Languages 1/16/18 PROGRAMMING LANGUAGE FOUNDATIONS AND HISTORY. Current

Chapter 1 Preliminaries

Programming Languages 2nd edition Tucker and Noonan"

Concepts of Programming Languages

Imperative Programming Languages (IPL)

DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING

What is a programming language?

Programmiersprachen (Programming Languages)

Concepts of Programming Languages

Programming Languages (CS )

Final-Term Papers Solved MCQS with Reference

Chapter 9. Subprograms

1 A question of semantics

Introduction to Computer Science I

Functional Programming. Big Picture. Design of Programming Languages

Lecture 13: Object orientation. Object oriented programming. Introduction. Object oriented programming. OO and ADT:s. Introduction

Lisp History. Lisp and Prolog Background. Lisp Use. Lisp Availability

Chapter 9. Subprograms

Chapter 1. Preview. Reason for Studying OPL. Language Evaluation Criteria. Programming Domains

Chapter 6. Data Types

Programming Languages A few bits of history

Lecturer: William W.Y. Hsu. Programming Languages

Programming Language Concepts 1982, 1987, Outline. Period

Chapter 11. Categories of languages that support OOP: 1. OOP support is added to an existing language

CS 565: Programming Languages. Spring 2008 Tu, Th: 16:30-17:45 Room LWSN 1106

LECTURE/ STUDY NOTES ON C

Programming Languages FILS Andrei Vasilateanu

Control Structures. Outline. In Text: Chapter 8. Control structures Selection. Iteration. Gotos Guarded statements. One-way Two-way Multi-way

A brief survey of programming languages: motivation and design/ continued. Lecture 3. Even more, Algol, Cobol. Are they really different?

Which of the following is not true of FORTRAN?

Chapter 11 :: Functional Languages

Programming Languages and Program Development Life Cycle Fall Introduction to Information and Communication Technologies CSD 102

Transcription:

1. Plankalkül - 1945 - Never implemented - Advanced data structures - floating point, arrays, records - Invariants - Notation: A(7) := 5 * B(6) 5 * B => A V 6 7 (subscripts) S 1.n 1.n (data types) 2. Pseudocodes - 1949 What was wrong with using machine code? a. Poor readability b. Poor modifiability c. Expression coding was tedious d. Machine deficiencies--no indexing or fl. pt. - Short code; 1949; BINAC; Mauchly - Expressions were coded, left to right - Some operations: 1n => (n+2)nd power 2n => (n+2)nd root 07 => addition Copyright 1998 by Addison Wesley Longman, Inc. 1

2. Pseudocodes (continued) - Speedcoding; 1954; IBM 701, Backus - Pseudo ops for arithmetic and math functions - Conditional and unconditional branching - Autoincrement registers for array access - Slow! - Only 700 words left for user program 3. Laning and Zierler System - 1953 - Implemented on the MIT Whirlwind computer - First "algebraic" compiler system - Subscripted variables, function calls, expression translation - Never ported to any other machine 4. FORTRAN I - 1957 (FORTRAN 0-1954 - not implemented) - Designed for the new IBM 704, which had index registers and floating point hardware - Environment of development: 1. Computers were small and unreliable 2. Applications were scientific 3. No programming methodology or tools 4. Machine efficiency was most important Copyright 1998 by Addison Wesley Longman, Inc. 2

4. FORTRAN I (continued) - Impact of environment on design 1. No need for dynamic storage 2. Need good array handling and counting loops 3. No string handling, decimal arithmetic, or powerful input/output (commercial stuff) - First implemented version of FORTRAN - Names could have up to six characters - Posttest counting loop (DO) - Formatted i/o - User-defined subprograms - Three-way selection statement (arithmetic IF) - No data typing statements - No separate compilation - Compiler released in April 1957, after 18 worker/ years of effort - Programs larger than 400 lines rarely compiled correctly, mainly due to poor reliability of the 704 - Code was very fast - Quickly became widely used 5. FORTRAN II - 1958 - Independent compilation - Fix the bugs Copyright 1998 by Addison Wesley Longman, Inc. 3

6. FORTRAN IV - 1960-62 - Explicit type declarations - Logical selection statement - Subprogram names could be parameters - ANSI standard in 1966 7. FORTRAN 77-1978 - Character string handling - Logical loop control statement - IF-THEN-ELSE statement 8. FORTRAN 90-1990 - Modules - Dynamic arrays - Pointers - Recursion - CASE statement - Parameter type checking FORTRAN Evaluation - Dramatically changed forever the way computers are used Copyright 1998 by Addison Wesley Longman, Inc. 4

9. LISP - 1959 - LISt Processing language (Designed at MIT by McCarthy) - AI research needed a language that: 1. Process data in lists (rather than arrays) 2. Symbolic computation (rather than numeric) - Only two data types: atoms and lists - Syntax is based on lambda calculus - Pioneered functional programming - No need for variables or assignment - Control via recursion and conditional expressions - Still the dominant language for AI - COMMON LISP and Scheme are contemporary dialects of LISP - ML, Miranda, and Haskell are related languages 10. ALGOL 58-1958 - Environment of development: 1. FORTRAN had (barely) arrived for IBM 70x 2. Many other languages were being developed, all for specific machines 3. No portable language; all were machinedependent 4. No universal language for communicating algorithms Copyright 1998 by Addison Wesley Longman, Inc. 5

11. ALGOL 58 (continued) - ACM and GAMM met for four days for design - Goals of the language: 1. Close to mathematical notation 2. Good for describing algorithms 3. Must be translatable to machine code - Language Features: - Concept of type was formalized - Names could have any length - Arrays could have any number of subscripts - Parameters were separated by mode (in & out) - Subscripts were placed in brackets - Compound statements (begin... end) - Semicolon as a statement separator - Assignment operator was := - if had an else-if clause - Comments: - Not meant to be implemented, but variations of it were (MAD, JOVIAL) - Although IBM was initially enthusiastic, all support was dropped by mid-1959 Copyright 1998 by Addison Wesley Longman, Inc. 6

12. ALGOL 60-1960 - Modified ALGOL 58 at 6-day meeting in Paris - New Features: - Block structure (local scope) - Two parameter passing methods - Subprogram recursion - Stack-dynamic arrays - Still no i/o and no string handling - Successes: - It was the standard way to publish algorithms for over 20 years - All subsequent imperative languages are based on it - First machine-independent language - First language whose syntax was formally defined (BNF) - Failure: - Never widely used, especially in U.S. Reasons: 1. No i/o and the character set made programs nonportable 3. Too flexible--hard to implement 4. Intrenchment of FORTRAN 5. Formal syntax description 6. Lack of support of IBM Copyright 1998 by Addison Wesley Longman, Inc. 7

13. COBOL - 1960 - Environment of development: - UNIVAC was beginning to use FLOW-MATIC - USAF was beginning to use AIMACO - IBM was developing COMTRAN - Based on FLOW-MATIC - FLOW-MATIC features: - Names up to 12 characters, with embedded hyphens - English names for arithmetic operators - Data and code were completely separate - Verbs were first word in every statement - First Design Meeting - May 1959 - Design goals: 1. Must look like simple English 2. Must be easy to use, even if that means it will be less powerful 3. Must broaden the base of computer users 4. Must not be biased by current compiler problems - Design committee were all from computer manufacturers and DoD branches - Design Problems: arithmetic expressions? subscripts? Fights among manufacturers Copyright 1998 by Addison Wesley Longman, Inc. 8

13. COBOL (continued) - Contributions: - First macro facility in a high-level language - Hierarchical data structures (records) - Nested selection statements - Long names (up to 30 characters), with hyphens - Data Division - Comments: - First language required by DoD; would have failed without DoD - Still the most widely used business applications language 14. BASIC - 1964 - Designed by Kemeny & Kurtz at Dartmouth - Design Goals: - Easy to learn and use for non-science students - Must be pleasant and friendly" - Fast turnaround for homework - Free and private access - User time is more important than computer time - Current popular dialects: QuickBASIC and Visual BASIC Copyright 1998 by Addison Wesley Longman, Inc. 9

15. PL/I - 1965 - Designed by IBM and SHARE - Computing situation in 1964 (IBM's point of view) 1. Scientific computing - IBM 1620 and 7090 computers - FORTRAN - SHARE user group 2. Business computing - IBM 1401, 7080 computers - COBOL - GUIDE user group - By 1963, however, - Scientific users began to need more elaborate i/o, like COBOL had; Business users began to need fl. pt. and arrays (MIS) - It looked like many shops would begin to need two kinds of computers, languages, and support staff--too costly - The obvious solution: 1. Build a new computer to do both kinds of applications 2. Design a new language to do both kinds of applications Copyright 1998 by Addison Wesley Longman, Inc. 10

15. PL/I (continued) - PL/I contributions: 1. First unit-level concurrency 2. First exception handling 3. Switch-selectable recursion 4. First pointer data type 5. First array cross sections - Comments: - Many new features were poorly designed - Too large and too complex - Was (and still is) actually used for both scientific and business applications 16. Early Dynamic Languages - Characterized by dynamic typing and dynamic storage allocation - APL (A Programming Language) 1962 - Designed as a hardware description language (at IBM by Ken Iverson) - Highly expressive (many operators, for both scalars and arrays of various dimensions) - Programs are very difficult to read Copyright 1998 by Addison Wesley Longman, Inc. 11

- SNOBOL(1964) - Designed as a string manipulation language (at Bell Labs by Farber, Griswold, and Polensky) - Powerful operators for string pattern matching 17. SIMULA 67-1967 - Designed primarily for system simulation (in Norway by Nygaard and Dahl) - Based on ALGOL 60 and SIMULA I - Primary Contribution: - Coroutines - a kind of subprogram - Implemented in a structure called a class - Classes are the basis for data abstraction - Classes are structures that include both local data and functionality 18. ALGOL 68-1968 - From the continued development of ALGOL 60, but it is not a superset of that language - Design is based on the concept of orthogonality - Contributions: 1. User-defined data structures 2. Reference types 3. Dynamic arrays (called flex arrays) Copyright 1998 by Addison Wesley Longman, Inc. 12

18. ALGOL 68 (continued) - Comments: - Had even less usage than ALGOL 60 - Had strong influence on subsequent languages, especially Pascal, C, and Ada 19. Pascal - 1971 - Designed by Wirth, who quit the ALGOL 68 committee (didn't like the direction of that work) - Designed for teaching structured programming - Small, simple, nothing really new - Still the most widely used language for teaching programming in colleges (but use is shrinking) 20. C - 1972 - Designed for systems programming (at Bell Labs by Dennis Richie) - Evolved primarily from B, but also ALGOL 68 - Powerful set of operators, but poor type checking - Initially spread through UNIX 21. Other descendants of ALGOL - Modula-2 (mid-1970s by Niklaus Wirth at ETH) - Pascal plus modules and some low-level features designed for systems programming Copyright 1998 by Addison Wesley Longman, Inc. 13

21. Other descendants of ALGOL (cont.) - Modula-3 (late 1980s at Digital & Olivetti) - Modula-2 plus classes, exception handling, garbage collection, and concurrency - Oberon (late 1980s by Wirth at ETH) - Adds support for OOP to Modula-2 - Many Modula-2 features were deleted (e.g., for statement, enumeration types, with statement, noninteger array indices) - Delphi (Borland) - Pascal plus features to support OOP - More elegant and safer than C++ 22. Prolog - 1972 - Developed at the University of Aix-Marseille, by Comerauer and Roussel, with some help from Kowalski at the University of Edinburgh - Based on formal logic - Non-procedural - Can be summarized as being an intelligent database system that uses an inferencing process to infer the truth of given queries Copyright 1998 by Addison Wesley Longman, Inc. 14

23. Ada - 1983 (began in mid-1970s) - Huge design effort, involving hundreds of people, much money, and about eight years - Contributions: 1. Packages - support for data abstraction 2. Exception handling - elaborate 3. Generic program units 4. Concurrency - through the tasking model - Comments: - Competitive design - Included all that was then known about software engineering and language design - First compilers were very difficult; the first really usable compiler came nearly five years after the language design was completed - Ada 95 (began in 1988) - Support for OOP through type derivation - Better control mechanisms for shared data (new concurrency features) - More flexible libraries Copyright 1998 by Addison Wesley Longman, Inc. 15

24. Smalltalk - 1972-1980 - Developed at Xerox PARC, initially by Alan Kay, later by Adele Goldberg - First full implementation of an object-oriented language (data abstraction, inheritance, and dynamic type binding) - Pioneered the graphical user interface everyone now uses 25. C++ - 1985 - Developed at Bell Labs by Stroustrup - Evolved from C and SIMULA 67 - Facilities for object-oriented programming, taken partially from SIMULA 67, were added to C - Also has exception handling - A large and complex language, in part because it supports both procedural and OO programming - Rapidly grew in popularity, along with OOP - ANSI standard approved in November, 1997 - Eiffel - a related language that supports OOP - (Designed by Bertrand Meyer - 1992) - Not directly derived from any other language - Smaller and simpler than C++, but still has most of the power Copyright 1998 by Addison Wesley Longman, Inc. 16

26. Java (1995) - Developed at Sun in the early 1990s - Based on C++ - Significantly simplified - Supports only OOP - Has references, but not pointers - Includes support for applets and a form of concurrency Copyright 1998 by Addison Wesley Longman, Inc. 17