C H A P T E R O N E Overview.

Slides:



Advertisements
Similar presentations
Chapter 1: Preliminaries
Advertisements

CS 354 Overview. Addison-Wesley –2 Course Topics What is a programming language? What features do programming languages have? How are these features.
Reasons to study concepts of PL
ISBN Chapter 1 Preliminaries. Copyright © 2004 Pearson Addison-Wesley. All rights reserved.1-2 Chapter 1 Topics Motivation Programming Domains.
ISBN Chapter 1 Preliminaries. Copyright © 2007 Addison-Wesley. All rights reserved.1-2 Chapter 1 Topics Reasons for Studying Concepts of.
CS 354 Overview. Copyright © 2007 Addison-Wesley. All rights reserved. 1–2 Course Topics What is a programming language? What features do programming.
ISBN Chapter 1 Preliminaries. Copyright © 2006 Addison-Wesley. All rights reserved.1-2 Chapter 1 Topics Reasons for Studying Concepts of.
Programming Languages Structure
ISBN Lecture 01 Preliminaries. Copyright © 2004 Pearson Addison-Wesley. All rights reserved.1-2 Lecture 01 Topics Motivation Programming.
Lecture 2 Concepts of Programming Languages
ISBN Chapter 1 Topics Motivation Programming Domains Language Evaluation Criteria Influences on Language Design Language Categories Language.
Copyright © 2006 Addison-Wesley. All rights reserved.1-1 INTRODUCTION "When the only tool you have is a hammer, everything looks like a nail" (Abraham.
Copyright © 1998 by Addison Wesley Longman, Inc. 1 Concepts of Programming Languages Chapter 1.
ISBN Chapter 1 Preliminaries. Copyright © 2007 Addison-Wesley. All rights reserved.1-2 Chapter 1 Topics Reasons for Studying Concepts of.
INTRODUCTION "When the only tool you have is a hammer, everything looks like a nail" (Abraham Maslow)
Chapter 1 Preliminaries.
Chapter 1 Preliminaries. Copyright © 2012 Addison-Wesley. All rights reserved.1-2 Chapter 1 Topics Reasons for Studying Concepts of Programming Languages.
ISBN Chapter 1 Preliminaries. Copyright © 2006 Addison-Wesley. All rights reserved. 1-2 Chapter 1 Topics Reasons for Studying Concepts of.
Programming Language and Paradigms
CS 355 – Programming Languages
CS 363 Comparative Programming Languages
Chapter 1 Preliminaries CS Concepts of Programming Languages.
Copyright © 2006 Addison-Wesley. All rights reserved.1-1 ICS 410: Programming Languages.
C HAPTER 1 Introduction. T OPICS Reasons for Studying Concepts of Programming Languages Programming Domains Language Evaluation Criteria Influences on.
Copyright © 2007 Addison-Wesley. All rights reserved.1-1 Reasons for Studying Concepts of Programming Languages Increased ability to express ideas Improved.
ICS 313 Fundamentals of Programming Languages Instructor: Abdul Wahid Wali Lecturer, CSSE, UoH
ISBN Chapter 1 Preliminaries. Corrected and improved by Assoc. Prof. Zeki Bayram, EMU, North Cyprus. Original Copyright © 2007 Addison-Wesley.
ISBN CS 354 Preliminaries. Copyright © 2006 Addison-Wesley. All rights reserved.1-2 Course Topics What is a programming language? What features.
ISBN Chapter 1 Preliminaries. Copyright © 2015 Pearson. All rights reserved.1-2 Chapter 1 Topics Reasons for Studying Concepts of Programming.
ISBN Chapter 1 Preliminaries. Copyright © 2009 Addison-Wesley. All rights reserved.1-2 Chapter 1 Topics Reasons for Studying Concepts of.
ISBN Chapter 1 Preliminaries. 1-2 Chapter 1 Preliminaries 1.1 Reasons for Studying Concepts of Programming Languages 1.2 Programming Domains.
Chapter 1 Preliminaries. Copyright © 2017 Addison-Wesley. All rights reserved.1-2 Chapter 1 Topics Reasons for Studying Concepts of Programming Languages.
ISBN Chapter 1 Preliminaries. Copyright © 2006 Addison-Wesley. All rights reserved.1-2 Chapter 1 Topics Reasons for Studying Concepts of.
Concepts of Programming Languages
Chapter 1 Preliminaries.
Concepts of Programming Languages
Chapter 1 Preliminaries.
Chapter 1 Preliminaries.
Chapter 1 Preliminaries.
PROGRAMMING LANGUAGES
Chapter 1 Reasons to study concepts of PLs Programming Domains
1.1 Reasons to study concepts of PLs
Chapter 1 Preliminaries.
Chapter 1 Preliminaries.
Chapter 1 Preliminaries.
Chapter 1 Introduction.
Chapter 1 Preliminaries.
Chapter 1 Preliminaries.
Chapter 1 Preliminary. Chapter 1 Preliminary 1.1 Reasons for Studying Concepts of Programming Languages Increased capacity to express ideas Improved.
Chapter 1 Preliminaries.
Chapter 1 Preliminaries.
Chapter 1 Preliminaries.
Chapter 1 Preliminaries.
Chapter 1 Preliminaries.
Chapter 1 Preliminaries.
Chapter 1 Preliminaries.
Chapter 1 Preliminaries.
Chapter 1 Topics Reasons for Studying Concepts of Programming Languages Programming Domains Language Evaluation Criteria Influences on Language Design.
Chapter 1 Preliminaries.
Chapter 1 Preliminaries.
Chapter 1 Preliminaries.
Chapter 1 Preliminaries.
Chapter 1 Preliminaries.
Chapter 1 Preliminaries.
Chapter 1 Preliminaries.
Chapter 1 Preliminaries.
Presentation transcript:

C H A P T E R O N E Overview

Chapter 1 Topics Why Studying Concepts of Programming Languages? The Art of Language Design Programming Domains Language Categories Language Evaluation Criteria Language Design Trade-Offs Implementation Methods Programming Environments

Why Study Concepts of Programming Languages? Increased ability to express ideas Improved background for choosing appropriate languages Increased ability to learn new languages Better understanding of significance of implementation Overall advancement of computing

The art of language design Why are there so many? Evolution Goto-based control flow Structured programming Object-oriented structure Special purpose Symbolic data Character strings Low-level system programming Reasoning, logical relation Personal preference What makes a language successful? Expressive power Ease of use for novice Ease of implementation Standardization Open source Excellent compilers Economics, Patronage, and Inertia

Influences on Language Design Computer Architecture von Neumann architecture Programming Methodologies New software development methodologies (e.g., object-oriented software development) led to new programming paradigms and by extension, new programming languages

Influences: Computer architecture Well-known architecture: von Neumann Imperative languages, most dominant, because of von Neumann computers Data and programs stored in memory Memory is separate from CPU Instructions and data are piped from memory to CPU Basis for imperative languages Variables model memory cells Assignment statements model piping Iteration is efficient

Von Neumann Architecture

Influences: Programming Methodologies 1950s and early 1960s: Simple applications; worry about machine efficiency Late 1960s: People efficiency became important; readability, better control structures structured programming top-down design and step-wise refinement Late 1970s: Process-oriented to data-oriented data abstraction Middle 1980s: Object-oriented programming Data abstraction + inheritance + polymorphism

Programming Paradigms Imperative Central features are variables, assignment statements, and iteration Examples: C, Pascal Object-oriented Data abstraction (Encapsulate data objects with processing), inheritance, dynamic type binding Examples: Java, C++ Functional Main means of making computations is by applying functions to given parameters Examples: LISP, Scheme Logic Rule-based (rules are specified in no particular order) Example: Prolog Markup New; not a programming per se, but used to specify the layout of information in Web documents Examples: XHTML, XML

Programming Paradigms: Alternative Imperative Procedural :- C Block-Structured :-Pascal, Ada Object-based :- Ada Object-oriented :- Ada, Object-Pascal, C++, Java Parallel Processing :- Ada, Pascal-S, Occam, C-Linda Declarative Logic :- Prolog Functional :- LISP, Scheme Database :- SQL

Programming Paradigms: Alternative Imperative Von Neumann Scripting Object-oriented Declarative Functional Dataflow Logic, constraint-based Template-based

Programming Paradigms: Emerging Event-driven/Visual Continuous loop that responds to events Code is executed upon activation of events Subcategory of imperative Examples: Visual Basic .NET, Java Concurrent Cooperating processes Examples: High Performance Fortran

Example of GCD program int gcd(int a, int b) { while (a!=b) { if (a>b) a = a-b; else b = b-a; } return a; } //C (define gcd (lambda (a b) (cond ((= a b) a) ((> a b) (gcd (- a b) b)) (else (gcd (- b a) a))))) ;scheme gcd(A,B,G) :- A = B, G=A. gcd(A,B,G) :- A > B, C is A-B, gcd(C,B,G). gcd(A,B,G) :- B > A, C is B-A, gcd(C,A,G). %Prolog Copyright © 2009 Elsevier, Inc. All rights reserved.

Programming Domains Scientific applications Business applications Large number of floating point computations Fortran Business applications Produce reports, use decimal numbers and characters COBOL Artificial intelligence Symbols rather than numbers manipulated LISP Systems programming Need efficiency because of continuous use C Web Programming Eclectic collection of languages: markup (e.g., XHTML), scripting (e.g., PHP), general-purpose (e.g., Java)

Language Evaluation Criteria Readability: the ease with which programs can be read and understood Writability: the ease with which a language can be used to create programs Reliability: conformance to specifications (i.e., performs to its specifications under all conditions) Cost: the ultimate total cost

Machine code

Evaluation Criteria: Readability Overall simplicity A manageable set of features and constructs Few feature multiplicity (means of doing the same operation) Minimal operator overloading Orthogonality A relatively small set of primitive constructs can be combined in a relatively small number of ways Every possible combination is legal Lack of orthogonality leads to exceptions to rules Makes the language easy to learn and read Meaning is context independent

Evaluation Criteria: Readability Control statements The presence of well-known control structures (e.g., while statement) Data types and structures The presence of adequate facilities for defining data structures Syntax considerations Identifier forms: flexible composition Special words and methods of forming compound statements Form and meaning: self-descriptive constructs, meaningful keywords

Evaluation Criteria: Writability Simplicity and orthogonality Few constructs, a small number of primitives, a small set of rules for combining them Support for abstraction The ability to define and use complex structures or operations in ways that allow details to be ignored Expressivity A set of relatively convenient ways of specifying operations Example: the inclusion of for statement in many modern languages

Evaluation Criteria: Reliability Type checking Testing for type errors Exception handling Intercept run-time errors and take corrective measures Aliasing Presence of two or more distinct referencing methods for the same memory location Readability and writability A language that does not support “natural” ways of expressing an algorithm will necessarily use “unnatural” approaches, and hence reduced reliability

Evaluation Criteria: Cost Training programmers to use language Writing programs Compiling programs Executing programs Language implementation system: availability of free compilers Reliability: poor reliability leads to high costs Maintaining programs

Evaluation Criteria: Others Portability The ease with which programs can be moved from one implementation to another Generality The applicability to a wide range of applications Well-definedness The completeness and precision of the language’s official definition

Language Characteristics & Criteria Characteristic Readability Writability Reliability Simplicity & orthogonality    Control statements    Data types and structure    Syntax design    Support for abstraction   Expressivity   Type checking  Exception handling  Restricted aliasing 

Language Design Trade-Offs Reliability vs. cost of execution Conflicting criteria Example: Java demands all references to array elements be checked for proper indexing but that leads to increased execution costs Readability vs. writability Another conflicting criteria Example: APL provides many powerful operators (and a large number of new symbols), allowing complex computations to be written in a compact program but at the cost of poor readability Writability (flexibility) vs. reliability Example: C++ pointers are powerful and very flexible but not reliably used

Implementation Methods Compilation Programs are translated into machine language Pure Interpretation Programs are interpreted by another program known as an interpreter Hybrid Implementation Systems A compromise between compilers and pure interpreters

Layered View of Computer Virtual computer – the OS and language implementation which are layered over machine interface of a computer

Implementation Methods: Compilation Translate high-level program (source language) into machine code (machine language) Slow translation, fast execution Compilation process has several phases: lexical analysis: converts characters in the source program into lexical units syntax analysis: transforms lexical units into parse trees which represent the syntactic structure of program Semantics analysis: generate intermediate code code generation: machine code is generated

Compilation Process

Source program in C (GCD program) Lexical analyzer int main() { int i = getint(), j = getint(); while (i != j) { if (i > j) i = i - j; else j = j - i; } putint(i); int main ( ) { int i = getint ( ) , j = getint ( ) ; while ( i != j ) { if ( i > j ) i = i - j ; else j = j - i ; putint ( i ) ; Source program in C (GCD program) GCD program tokens

Syntax analyzer

Implementation Methods: Interpreter No translation Easier implementation of programs (run-time errors can easily and immediately displayed) Slower execution (10 to 100 times slower than compiled programs) Often requires more space Becoming rare on high-level languages Significant comeback with some Web scripting languages (e.g., JavaScript)

Pure Interpretation

Implementation Methods: Hybrid A compromise between compilers and pure interpreters A high-level language program is translated to an intermediate language that allows easy interpretation Faster than pure interpretation Examples Perl programs are partially compiled to detect errors before interpretation Initial implementations of Java were hybrid; the intermediate form, byte code, provides portability to any machine that has a byte code interpreter and a run-time system (together, these are called Java Virtual Machine)

Hybrid Implementation System

Programming Environments The collection of tools used in software development UNIX An older operating system and tool collection Nowadays often used through a GUI (e.g., CDE, KDE, or GNOME) that run on top of UNIX Borland JBuilder An integrated development environment for Java Microsoft Visual Studio.NET A large, complex visual environment Used to program in C#, Visual BASIC.NET, Jscript, J#, or C++

History of Programming Languages Machine language Assembly language High-level language 2nd generation 3rd generation 4th generation (very high-level language)

A Brief Historical Lineage of Some Key Programming Languages

Programming Languages: Trend

Principles of Language Design Syntax (next class) Semantics Memory management Exception handling

References Books Interesting links Robert W. Sebesta. Concepts of Programming Languages, Addison Wesley, 2006. Michael L. Scott. Programming Language Pragmatics. Morgan Kaufmann Publishers, 2009 Interesting links history:http://en.wikipedia.org/wiki/History_of_programming_languages timeline: http://www.levenez.com/lang/lang_a4.pdf