CS 363 Comparative Programming Languages Evolution of Programming Languages.

Slides:



Advertisements
Similar presentations
1 Scheme and Functional Programming Aaron Bloomfield CS 415 Fall 2005.
Advertisements

Names and Bindings.
Programming Languages Marjan Sirjani 2 2. Language Design Issues Design to Run efficiently : early languages Easy to write correctly : new languages.
CS ExCo Advanced in Topics Object-Oriented Programming.
1 ) Definition 2) Note on structured and modular programming, and information hiding 3) Example imperative languages 4) Features of imperative languages.
ISBN Chapter 5 Names, Bindings, Type Checking, and Scopes Names Variables The Concept of Binding Type Checking Strong Typing Type Compatibility.
Reasons to study concepts of PL
A Quick Overview of Languages. FORTRAN Designed in 1955 First release of the compiler in 1957 Algebraic in nature Scientific (numeric not string oriented)
ISBN Chapter 2 Evolution of the Major Programming Languages.
1 Copyright © 1995 by Addison-Wesley Publishing Co. 1. Plankalkül Never implemented - Advanced data structures - floating point, arrays, records.
6/27/2015G. Levine1 PROGRAMMING LANGUAGES Text: Programming Languages, Design and Implementation Pratt and Zelkowitz 4 th ed. Prentice-Hall.
ISBN Chapter 2 Evolution of the Major Programming Languages.
1 Organization of Programming Languages-Cheng (Fall 2004) Evolution of Programming Languages (CSE452) Instructor: Dr. B. Cheng Fall 2004.
ISBN Chapter 2 Evolution of the Major Programming Languages.
ISBN Chapter 2 Evolution of the Major Programming Languages.
Evolution of the Major Programming Languages
BIT Presentation 6. Contents GENERATIONS OF LANGUAGES COMPILERS AND INTERPRETERS VIRTUAL MACHINES OBJECT-ORIENTED PROGRAMMING SCRIPTING LANGUAGES.
CS 355 – PROGRAMMING LANGUAGES Dr. X. Copyright © 2012 Addison-Wesley. All rights reserved.1-2 Topics Zuse’s Plankalkül Minimal Hardware Programming:
Evolution of the Major Programming Languages
ISBN Chapter 2 Evolution of the Major Programming Languages.
ISBN Chapter 2 Evolution of the Major Programming Languages.
Computer Systems Lab Courses. 2CS 363 GMU Spring Programming Languages Sebesta Fig. 1.2 Languages are an abstraction used by the programmer to express.
ISBN Chapter 2 Evolution of the Major Programming Languages.
CS2403 Programming Languages Evolution of Programming Languages Chung-Ta King Department of Computer Science National Tsing Hua University (Slides are.
ISBN Chapter 2 Evolution of the Major Programming Languages.
CSC3315 (Spring 2009)1 CSC 3315 Programming Languages Hamid Harroud School of Science and Engineering, Akhawayn University
5-1 Chapter 5: Names, Bindings, Type Checking, and Scopes Variables The Concept of Binding Type Checking Strong Typing Type Compatibility Scope and Lifetime.
CS 403 Programming Language Theory Class 2 - August 29, 2000.
ISBN Chapter 2 Evolution of the Major Programming Languages.
ISBN Chapter 2 Evolution of the Major Programming Languages.
1 Programming Language History and Evolution In Text: Chapter 2.
CS 403 Programming Language Theory Class 3 - August 31, 2000.
ISBN Chapter 2 Evolution of the Major Programming Languages.
Copyright © 2006 Addison-Wesley. All rights reserved.1-1 ICS 410: Programming Languages.
The Teacher Computing Computer Languages [Computing]
ISBN Chapter 2 Evolution of the Major Programming Languages.
Copyright © 2007 Addison-Wesley. All rights reserved.1-1 Chapter 2: Evolution of the Major Programming Languages The IBM 704 and Fortran Functional Programming:
Comparative Programming Languages Language Comparison: Scheme, Smalltalk, Python, Ruby, Perl, Prolog, ML, C++/STL, Java, Haskell.
The Evolution of Programming Languages Day 2 Lecturer: Xiao Jia The Evolution of PLs1.
1 Chapter 2 © 1998 by Addison Wesley Longman, Inc. 2.1 Plankalkül Never implemented - Advanced data structures - floating point, arrays, records.
1 CS Programming Languages Class 04 September 5, 2000.
Ada, Scheme, R Emory Wingard. Ada History Department of Defense in search of high level language around Requirements drafted for the language.
Evolution of the Major Programming Languages Chapter 2: Evolution of the Major Programming Languages Lectures # 5.
Evolution of the Major Programming Languages SANGJI University Kwangman Ko
History. Development Driven by Function Functions of a Programming Language –To describe computation for use by computers –To describe computation and.
Programming Language History and Evolution
Functional Programming
A BRIEF HISTORY OF PROGRAMMING LANGUAGES
Zuse’s Plankalkül – 1945 Never implemented Problems Zuse Solved
Concepts of Programming Languages
Why study programming languages?
Evolution of the Major Programming Languages
Evolution of the Major Programming Languages
Programming Language History and Evolution
Evolution of the Major Programming Languages
Chapter 2 Plankalkül – Never implemented
Evolution of the Major Programming Languages
Ada – 1983 History’s largest design effort
FP Foundations, Scheme In Text: Chapter 14.
Evolution of the Major Programming Languages
Evolution of the Major Programming Languages
Evolution of the Major Programming Languages
Evolution of the Major Programming Languages
Cobol Design goals: Problems
강의 내용 및 방법 접근방법 리포트 시험 Lambda Calculus, Proof of Correctness
2.1 Plankalkül Pseudocodes Never implemented
Programming Languages
Presentation transcript:

CS 363 Comparative Programming Languages Evolution of Programming Languages

CS 363 GMU Spring Genealogy (incomplete)

CS 363 GMU Spring FORTRAN FORmula TRANslating systems FORTRAN I (FORTRAN not implemented) –Designed by John Backus for the new IBM 704, which had index registers and floating point hardware –Environment of development: Computers were small and unreliable Applications were scientific No programming methodology or tools Machine efficiency was most important

CS 363 GMU Spring FORTRAN Impact of environment on design of FORTRAN I –No need for dynamic storage –Need good array handling and counting loops –No string handling, decimal arithmetic, or powerful input/output (commercial stuff) First implemented version of FORTRAN –Names could have up to six characters –Post-test counting loop ( DO ) –Formatted I/O –User-defined subprograms –Three-way selection statement (arithmetic IF: neg,0,pos ) –No data typing statements – implicit types (I-N are integer) –Fixed program format

CS 363 GMU Spring FORTRAN FORTRAN IV –Explicit type declarations –Logical selection statement –Subprogram names could be parameters –ANSI standard in 1966 FORTRAN –Character string handling –Logical loop control statement –IF-THEN-ELSE statement

CS 363 GMU Spring FORTRAN FORTRAN –Modules –Dynamic arrays –Pointers –Recursion –CASE statement –Parameter type checking

CS 363 GMU Spring FORTRAN Contributions –First widely used programming language –Changed the way people interacted with computers –Set the standard for compilers Goal: generate machine code similar to that of machine language programmers  highly optimized compiler Much of the theory of compilers was developed in this compiler.

CS 363 GMU Spring Sample Fortran subroutine defcolor(rgb,nframe) implicit none integer nframe integer ihpixf, jvpixf parameter(ihpixf = 256, jvpixf = 256) ! pixel size character*1 rgb(3,ihpixf,jvpixf) ! RGB data array local integer i, j, idummy do 100 j = 1, jvpixf do 100 i = 1, ihpixf idummy = i*3*nframe + j*2 idummy = mod(idummy,256) ! assuming color depth is 256 (0--255) rgb(1,i,j) = char(idummy) ! red idummy = i*1*nframe + j*3 idummy = mod(idummy,256) rgb(2,i,j) = char(idummy) ! green idummy = i*5*nframe + j*7 idummy = mod(idummy,256) rgb(3,i,j) = char(idummy) ! blue 100 continue return end

CS 363 GMU Spring Sample Fortran real*4 one,eps, ht, tf real*8 one8, eps8 one = 1. one8 = 1. eps = 1. eps8 = 1. ht = tf = 24. print *, 'Test for precision of real*4, based on 1+eps=1' 10 eps = eps/2. if (one.ne. one+eps) go to 10 eps = 2.*eps print *,' relative precision is ',eps print * print *,'Test for precision of real*4,', + 'based on eps=100000' eps = eps = eps/2. if (ht.ne. ht+eps) go to 15 eps = 2.*eps print *,' relative precision is ',eps print * print *,'Test for precision of real*4,', + 'based on 24+eps=24' eps = eps = eps/2. if (tf.ne. tf+eps) go to 17 eps = 2.*eps print *,' relative precision is ',eps print * print *, 'Test for precision of real*8, based on 1+eps=1' 20 eps8 = eps8/2. if (one8.ne. one8+eps8) go to 20 eps8 = 2.*eps8 print *,' relative precision is ',eps8 end

CS 363 GMU Spring LISP LISt Processing language AI research needed a language that: –Processed data in lists (rather than arrays) –Allowed symbolic computation (rather than numeric) Only two data types: atoms and lists Syntax is based on lambda calculus No variables or assignment Control via recursion and conditional expressions (A B C D) – apply function A to arguments B C D

CS 363 GMU Spring LISP (A B (C D) E) A BE CD (A B C D) A BD C Data Structures for Lists

CS 363 GMU Spring LISP Pioneered functional programming First interpreters slow COMMON LISP and Scheme are contemporary dialects of LISP ML, Miranda, and Haskell are related languages

CS 363 GMU Spring LISP Sample Problem: remove the first occurrence of atom A from list L (define (remove L A) (cond ( (null? L) '() ) ( (= (car L) A) (cdr L)) ; Match found! (else (cons (car L)(remove (cdr L) A))) ; keep searching )

CS 363 GMU Spring ALGOL 58 and 60 Designed as a ‘universal language’ by committee (ACM and European committee) Goals of the language: –Close to mathematical notation –Good for describing algorithms –Must be translatable to machine code Environment of development: –FORTRAN had (barely) arrived for IBM 70x –Many other languages were being developed, all for specific machines –No portable language; all were machine-dependent –No language for communicating algorithms

CS 363 GMU Spring ALGOL 58 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 –No I/O - “would make it machine dependent” –Not meant to be implemented, but variations were (MAD, JOVIAL) –Although IBM was initially enthusiastic, all support was dropped by mid- 1959

CS 363 GMU Spring ALGOL 60 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

CS 363 GMU Spring ALGOL 60 Contribution: –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) Never widely used, especially in U.S. –No I/O and the character set made programs non-portable –Too flexible--hard to implement –Entrenchment of FORTRAN –Formal syntax description –Lack of support of IBM

CS 363 GMU Spring BASIC Beginner’s All-purpose Symbolic Instruction Code Designed by Kemeny & Kurtz at Dartmouth Design Goals: –Easy to learn and use for non-science students –“pleasant and friendly” –Fast turnaround for homework –Free and private access –User time is more important than computer time Current popular dialect: Visual BASIC First widely used language with time sharing

CS 363 GMU Spring PL/I Computing situation in 1964 (IBM's point of view) –Scientific computing IBM 1620 and 7090 computers with FORTRAN –Business computing IBM 1401, 7080 computers with COBOL By 1963, however, –Scientific users began to need more elaborate I/O, like COBOL had; Business users began to need floating point 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: –Build a new computer to do both kinds of applications –Design a new language to do both kinds of applications

CS 363 GMU Spring PL/I Designed in five months PL/I contributions: –First unit-level concurrency –First exception handling –Switch-selectable recursion –First pointer data type –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

CS 363 GMU Spring APL and SNOBOL Characterized by dynamic typing and dynamic storage allocation APL (A Programming Language) 1962 –Designed as a hardware description language (at IBM) –Highly expressive (many operators, for both scalars and arrays of various dimensions) –Programs are very difficult to read SNOBOL(1964) –Designed as a string manipulation language (at Bell Labs) –Powerful operators for string pattern matching

CS 363 GMU Spring Snobol Example * Find biggest words and numbers in a test string * BIGP = (*P $ TRY *GT(SIZE(TRY,SIZE(BIG))) $ BIG FAIL STR = 'IN 1964 NFL ATTENDANCE JUMPED TO 4,807,884; ‘ 'AN INCREASE OF 401,810.' P = SPAN(' ,') BIG = STR BIGP OUTPUT = 'LONGEST NUMBER IS ' BIG P = SPAN('ABCDEFGHIJKLMNOPQRSTUVWXYZ') BIG = STR BIGP OUTPUT = 'LONGEST WORD IS ' BIG END

CS 363 GMU Spring SIMULA Designed primarily for system simulation Based on ALGOL 60 and SIMULA I Primary Contribution: –Co-routines - 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 –Objects and inheritance

CS 363 GMU Spring ALGOL From the continued development of ALGOL 60, but it is not a superset of that language Features: –User-defined data structures –Reference types –Dynamic arrays (called flex arrays) Contribution: –Had even less usage than ALGOL 60 BUT had strong influence on subsequent languages, especially Pascal, C, and Ada

CS 363 GMU Spring Important ALGOL Descendants Pascal –Designed by Wirth, who quit the ALGOL 68 committee (didn't like the direction) –Designed for teaching structured programming –Small, simple, nothing really new –From mid-1970s until the late 1990s, it was the most widely used language for teaching programming in colleges

CS 363 GMU Spring Pascal Sample program fibonacci(input, output); type natural 0..maxint; var fnm1,fnm2, fn,n,i: natural begin readln(n); if n <= 1 then writeln(n) {F 0 = 0 and F 1 = 1} else begin {compute F n } fnm2 := 0; fnm1 := 1; for i := 2 to n do begin fn := fnm1 + fnm2; fnm2 := fnm1; fnm1 := fn; end writeln(fn); end end.

CS 363 GMU Spring Important ALGOL Descendants C –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

CS 363 GMU Spring C Sample #include main() { int fnm1,fnm2, fn,n,i; scanf(“%d”,&n); if (n <= 1) printf(“%d\n”, n) /* F 0 = 0 and F 1 = 1*/ else { /* compute F n */ fnm2 = 0; fnm1 = 1; for (i = 2; i<=n ;++i) { fn = fnm1 + fnm2; fnm2 = fnm1; fnm1 = fn; } printf(“%d\n”,fn); }

CS 363 GMU Spring Important ALGOL Descendants Modula-2 - mid-1970s (Wirth) –Pascal plus modules and some low-level features designed for systems programming Modula-3 - late 1980s (Digital & Olivetti) –Modula-2 plus classes, exception handling, garbage collection, and concurrency Oberon - late 1980s (Wirth) –Adds support for OOP to Modula-2 –Many Modula-2 features were deleted (e.g., for statement, enumeration types, with statement, non- integer array indices)

CS 363 GMU Spring Prolog Developed at the University of Aix-Marseille, by Comerauer and Roussel, with some help from Kowalski at the University of Edinburgh Applications in AI, DBMS 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 Inefficient execution

CS 363 GMU Spring Prolog Sample parent(X,Y) :- mother(X,Y). parent(X,Y) :- father(X,Y). sibling(X,Y) :- mother(M,X), mother(M,Y), father(D,X), father(D,Y),X \== Y. haschildren(X) :- parent(X,_). grandparent(X,Y) :- parent(X,M),parent(M,Y). cousin(X,Y) :- parent(A,X),parent(B,Y),sibling(A,B). mother(anne,mary). mother(anne,liz). mother(anne,susan). mother(anne,virginia). mother(elizabeth,russ). mother(mabel,anne). father(james,zelie). father(james,harry). father(james,ned). father(john,will). father(john,russell). father(jim,rachel). father(jim,maggie). father(tim,patrick). grandparent(anne,Y).

CS 363 GMU Spring Ada (began in mid- 1970s) Huge design effort, involving hundreds of people, much money, and about eight years Environment: More than 450 different languages being used for DOD embedded systems (no software reuse and no development tools) Named for Ada Lovelace ( ) – first programmer (worked with Charles Babbage).

CS 363 GMU Spring Ada Contributions: –Packages - support for data abstraction –Exception handling - elaborate –Generic program units –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 – Compilers had to be ‘validated’ –Strong typechecking

CS 363 GMU Spring Ada Ada 95 (began in 1988) –Also designed by committee –Support for OOP through type derivation –Better control mechanisms for shared data (new concurrency features) –More flexible libraries

CS 363 GMU Spring Ada Sample package ArrayCalc is type Mydata is private; function sum return integer; procedure setval(arg:in integer); private size: constant:= 99; type myarray is array(1..size) of integer; type Mydata is record val: myarray; sz: integer := 0; end record; v: Mydata; end; package body ArrayCalc is function sum return integer is temp: integer; -- Body of function sum begin temp := 0; for i in 1..v.sz loop temp := temp + v.val(i); end loop; v.sz:=0; return temp; end sum; procedure setval(arg:in integer) is begin v.sz:= v.sz+1; v.val(v.sz):=arg; end setval; end; with Text_IO; use Text_IO; with ArrayCalc; use ArrayCalc; procedure main is k, m: integer; begin -- of main get(k); while k>0 loop for j in 1..k loop get(m); put(m,3); setval(m); end loop; new_line; put("SUM ="); put(ArrayCalc.sum,4); new_line; get(k); end loop; end;

CS 363 GMU Spring Smalltalk 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)

CS 363 GMU Spring C 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

CS 363 GMU Spring C++ Related Languages Eiffel - a related language that supports OOP –(Designed by Bertrand Meyer ) –Not directly derived from any other language –Smaller and simpler than C++, but still has most of the power Delphi (Borland) –Pascal plus features to support OOP –More elegant and safer than C++

CS 363 GMU Spring Java (1995) Developed at Sun in the early 1990s Based on C++ –Significantly simplified (does not include struct, union, enum, pointer arithmetic, and half of the assignment coercions of C++) –Supports only OOP –Has references, but not pointers –Includes support for applets and a form of concurrency

CS 363 GMU Spring Scripting Languages JavaScript –HTML-embedded at client side and executed by the client (i.e. web browser) –create dynamic HTML documents PHP –HTML enabled server side –Interpreted by server when a document in which it is embedded is requested. –Output of interpretation is HTML that replaces the PHP