Download - Week 1 Intro1

Transcript
Page 1: Week 1 Intro1

CS 418

Principles of Programming Languages

Lecture 01 - Introduction

1-1

Page 2: Week 1 Intro1

Administrativa

• Tentative schedule:– 1 weekly lecture of 50 minutes duration– 1 weekly lecture of 100 minute duration

• Lab and tutorial sessions – shall be scheduled as required

1-2

Page 3: Week 1 Intro1

Course Objective

• Understand the structure and design principles of programming languages

• Develop your skills in describing, analyzing, and using the features of programming languages

1-3

Page 4: Week 1 Intro1

Motivation

Computer scientist’s destiny:learn a new language every 2-5 years

• Understand structure & design principles of programming languages

1-4

Page 5: Week 1 Intro1

Questions that we shall address

1. Why are there so many programming languages?

2. How and why they are developed?3. What’s the intended purpose of a language?4. In what ways are they similar?5. What are the differences among them?6. Why wouldn’t we simply continue to use what

we have today?7. What kind of programming languages may be

developed?8. Design issues of various languages9. Design choices and alternatives10.Implementation issues 1-5

Page 6: Week 1 Intro1

What we will not study

• Formal semantics of languages• Compiler construction • Formal languages• One or several languages in detail• Low-level (machine) languages

1-6

Page 7: Week 1 Intro1

Tentative Course Plan

Week # Module Topics1 Introduction Preliminaries

Evolution of the major programming languages

2-3 Syntax and Semantics Describing syntax and semantics

Lexical and syntax analysis4 Names, Bindings, Type Checking

and scope

Names Concept of Binding Type checking Strong typing Type compatibility Scope and lifetime Named constants

5 Data Types Primitive data types Character string types User defined ordinal types Pointer and reference types

6 Expression and Assignment Statements

Arithmetic expressions Overloaded operators Type conversions 1-7

Page 8: Week 1 Intro1

7 Mid Term Exam7-8 Control Structures Selection statements

Iterative statements Unconditional branching

8-9 Subprograms Design issues for subprograms

Parameter passing methods Implementing subprograms

10 Abstract Data Types Concept of abstraction Design issues for ADTs

11 Object Oriented Programming Introduction Design Issues Support for OOP in different

languages (C++, Java, Ruby)12-13 Functional Programming Introduction

Fundamentals of Functional Programming languages

LISP Applications of functional

languages14-15 Logic Programming Languages Introduction to logic

programming Basic elements of Prolog Applications of Logic

Programming16 Concurrency Concurrent and distributed

programmingFinal Exam

1-8

Page 9: Week 1 Intro1

ISBN 0-321-49362-1

TextbookSebesta’s Lecture slides shall be adopted with some modifications for instruction

Reference Book:Programming Languages: Design & Implementation, (Terrence W. Pratt, Marvin V. Zelkowitz)

Page 10: Week 1 Intro1

Grading Scheme

• Sessional Marks– Quizzes 8% (~5-10)

– Homework 4% (~2 to 4)

– Term Assignment 4%– Attendance 4%

• Midterm Exam 30%• Final Exam 50%

1-10

Page 11: Week 1 Intro1

PRELIMINARIES

1-11Copyright © 2007 Addison-Wesley. All rights reserved.

Page 12: Week 1 Intro1

1-12

Reasons for Studying 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

Page 13: Week 1 Intro1

Week 1 - Session 2

1-13

Page 14: Week 1 Intro1

1-14

Programming Domains

• Scientific 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 Software– Eclectic collection of languages: markup (e.g., XHTML),

scripting (e.g., PHP), general-purpose (e.g., Java)

Page 15: Week 1 Intro1

1-15

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)

• Cost: the ultimate total cost

Page 16: Week 1 Intro1

1-16

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

• 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

Page 17: Week 1 Intro1

1-17

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

Page 18: Week 1 Intro1

1-18

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

Page 19: Week 1 Intro1

1-19

Evaluation Criteria: Cost

• Training programmers to use language• Writing programs (closeness to particular

applications)• Compiling programs• Executing programs• Language implementation system:

availability of free compilers• Reliability: poor reliability leads to high

costs• Maintaining programs

Page 20: Week 1 Intro1

1-20

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

Page 21: Week 1 Intro1

1-21

Page 22: Week 1 Intro1

1-22

Influences on Language Design

• Computer Architecture– Languages are developed around the

prevalent computer architecture, known as the 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

Page 23: Week 1 Intro1

1-23

Computer Architecture Influence

• Well-known computer 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

Page 24: Week 1 Intro1

1-24

The von Neumann Architecture

Page 25: Week 1 Intro1

1-25

Programming Methodologies Influences• 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

Page 26: Week 1 Intro1

1-26

Language Categories

• Imperative– Central features are variables, assignment statements, and

iteration– Examples: C, Pascal

• 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

• Object-oriented– Data abstraction, inheritance, late binding– Examples: Java, C++

• Markup – New; not a programming per se, but used to specify the layout

of information in Web documents– Examples: XHTML, XML

Page 27: Week 1 Intro1

1-27

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– Another conflicting criteria– Example: C++ pointers are powerful and very flexible

but not reliably used

Page 28: Week 1 Intro1

1-28

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

Page 29: Week 1 Intro1

1-29

Layered View of Computer

The operating system and language implementation are layered over Machine interface of a computer

Page 30: Week 1 Intro1

1-30

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

Page 31: Week 1 Intro1

1-31

The Compilation Process

Page 32: Week 1 Intro1

1-32

Additional Compilation Terminologies

• Load module (executable image): the user and system code together

• Linking and loading: the process of collecting system program and linking them to user program

Page 33: Week 1 Intro1

1-33

Execution of Machine Code

• Fetch-execute-cycle (on a von Neumann architecture)

initialize the program counter

repeat forever

fetch the instruction pointed by the counter

increment the counter

decode the instruction

execute the instruction

end repeat

Page 34: Week 1 Intro1

1-34

Von Neumann Bottleneck

• Connection speed between a computer’s memory and its processor determines the speed of a computer

• Program instructions often can be executed a lot faster than the above connection speed; the connection speed thus results in a bottleneck

• Known as von Neumann bottleneck; it is the primary limiting factor in the speed of computers

Page 35: Week 1 Intro1

1-35

Pure Interpretation

• 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)

Page 36: Week 1 Intro1

1-36

Pure Interpretation Process

Page 37: Week 1 Intro1

1-37

Hybrid Implementation Systems

• 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)

Page 38: Week 1 Intro1

1-38

Hybrid Implementation Process

Page 39: Week 1 Intro1

1-39

Just-in-Time Implementation Systems

• Initially translate programs to an intermediate language

• Then compile intermediate language into machine code

• Machine code version is kept for subsequent calls

• JIT systems are widely used for Java programs

• .NET languages are implemented with a JIT system

Page 40: Week 1 Intro1

1-40

Preprocessors

• Preprocessor macros (instructions) are commonly used to specify that code from another file is to be included

• A preprocessor processes a program immediately before the program is compiled to expand embedded preprocessor macros

• A well-known example: C preprocessor– expands #include, #define, and similar

macros

Page 41: Week 1 Intro1

1-41

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++

Page 42: Week 1 Intro1

1-42

Summary

• The study of programming languages is valuable for a number of reasons:– Increase our capacity to use different constructs– Enable us to choose languages more intelligently– Makes learning new languages easier

• Most important criteria for evaluating programming languages include:– Readability, writability, reliability, cost

• Major influences on language design have been machine architecture and software development methodologies

• The major methods of implementing programming languages are: compilation, pure interpretation, and hybrid implementation


Top Related