Programming Language and Paradigms

61
Programming Language and Paradigms Introduction Introduction Tasanawan Soonklang Department of Computing, Silpakorn University

Transcript of Programming Language and Paradigms

Page 1: Programming Language and Paradigms

Programming Language and Paradigms

IntroductionIntroduction

Tasanawan SoonklangDepartment of Computing, Silpakorn University

Page 2: Programming Language and Paradigms

Chapter 1 Topics

• A brief history of programming languages• Why study programming languages?• The art of language design• Language evaluation criteria• Programming language paradigms• Implementation methods• Programming environments

2

• A brief history of programming languages• Why study programming languages?• The art of language design• Language evaluation criteria• Programming language paradigms• Implementation methods• Programming environments

Page 3: Programming Language and Paradigms

A Brief History ofProgramming Languages

A Brief History ofProgramming Languages

Page 4: Programming Language and Paradigms

Brief history: Machine language

• Machine language – the sequence of bits thatdirectly controls a processor

• Add, compare, move data from one place to another,and so forth at appropriate times

55 89 e5 53 83 ec 04 83 e4 f0 e8 31 00 00 00 89 c3 e8 2a 0000 00 39 c3 74 10 8d b6 00 00 00 00 39 c3 7e 13 29 c3 39 c375 f6 89 1c 24 e8 6e 00 00 00 8b 5d fc c9 c3 29 d8 eb eb 90

GCD program in machine language for the x86 (Pentium)instruction set, expressed as hexadecimal (base 16) numbers

4

• Machine language – the sequence of bits thatdirectly controls a processor

• Add, compare, move data from one place to another,and so forth at appropriate times

55 89 e5 53 83 ec 04 83 e4 f0 e8 31 00 00 00 89 c3 e8 2a 0000 00 39 c3 74 10 8d b6 00 00 00 00 39 c3 7e 13 29 c3 39 c375 f6 89 1c 24 e8 6e 00 00 00 8b 5d fc c9 c3 29 d8 eb eb 90

GCD program in machine language for the x86 (Pentium)instruction set, expressed as hexadecimal (base 16) numbers

Page 5: Programming Language and Paradigms

Brief history: Assembly language

• Assembly language – expressed with mnemonicabbreviations, a less error-prone notation

pushl % ebp jle Dmovl %esp, %ebp subl %eax, %ebxpushl %ebx B: cmpl %eax, %ebxsubl $4, %esp jne Aandl $-16, %esp C: movl %ebx, (%esp)call getint call put intmovl %eax, %ebx movl -4(%ebp), %ebxcall getint leavecmpl %eax, %ebx retje C D: subl %ebx, %eax

A: cmpl %eax, %ebx jmp B

GCD program in assembly language for the x86.

5

• Assembly language – expressed with mnemonicabbreviations, a less error-prone notation

pushl % ebp jle Dmovl %esp, %ebp subl %eax, %ebxpushl %ebx B: cmpl %eax, %ebxsubl $4, %esp jne Aandl $-16, %esp C: movl %ebx, (%esp)call getint call put intmovl %eax, %ebx movl -4(%ebp), %ebxcall getint leavecmpl %eax, %ebx retje C D: subl %ebx, %eax

A: cmpl %eax, %ebx jmp B

GCD program in assembly language for the x86.

Page 6: Programming Language and Paradigms

Brief history: Assembly language

• One-to-one correspondence between mnemonicsand machine language instructions

• Assembler – system program for translating frommnemonics to machine language

• Machine-dependent language – rewrite programsfor every new machine

• Difficult to read and write large programs

6

• One-to-one correspondence between mnemonicsand machine language instructions

• Assembler – system program for translating frommnemonics to machine language

• Machine-dependent language – rewrite programsfor every new machine

• Difficult to read and write large programs

Page 7: Programming Language and Paradigms

Brief history: high-level language

• Fortran – first high-level language in the mid-1950s

• Machine-independent language• Compiler – system program for translating

from high-level language to assembly ormachine language

• Not one-to-one correspondence betweensource and target operations.

7

• Fortran – first high-level language in the mid-1950s

• Machine-independent language• Compiler – system program for translating

from high-level language to assembly ormachine language

• Not one-to-one correspondence betweensource and target operations.

Page 8: Programming Language and Paradigms

8

Page 9: Programming Language and Paradigms

9

Page 10: Programming Language and Paradigms

Why Study ProgrammingLanguages?

Why Study ProgrammingLanguages?

Page 11: Programming Language and Paradigms

Why study programming languages?

• Understand obscure features• Choose among alternative ways to express things• Simulate useful features in languages that lack

them• Make it easier to learn new languages• Help you choose a language

11

• Understand obscure features• Choose among alternative ways to express things• Simulate useful features in languages that lack

them• Make it easier to learn new languages• Help you choose a language

Page 12: Programming Language and Paradigms

Why study programming languages?

• Understand obscure features– In C, help you understand unions, arrays &

pointers, separate compilation, catch and throw– In C++, help you understand multiple inheritance,

* operator– In Common Lisp, help you understand first-class

functions/closures, streams, catch and throw,symbol internals

12

• Understand obscure features– In C, help you understand unions, arrays &

pointers, separate compilation, catch and throw– In C++, help you understand multiple inheritance,

* operator– In Common Lisp, help you understand first-class

functions/closures, streams, catch and throw,symbol internals

Page 13: Programming Language and Paradigms

Why study programming languages?

• Choose among alternative ways to express things– understand implementation costs:– based on knowledge of what will be done underneath:

• use simple arithmetic equal (use x*x instead of x**2)• use C pointers or Pascal "with" statement to factor address

calculations• avoid call by value with large data items in Pascal• avoid the use of call by name in Algol 60• choose between computation and table lookup (e.g. for

cardinality operator in C or C++)

13

• Choose among alternative ways to express things– understand implementation costs:– based on knowledge of what will be done underneath:

• use simple arithmetic equal (use x*x instead of x**2)• use C pointers or Pascal "with" statement to factor address

calculations• avoid call by value with large data items in Pascal• avoid the use of call by name in Algol 60• choose between computation and table lookup (e.g. for

cardinality operator in C or C++)

Page 14: Programming Language and Paradigms

Why study programming languages?

• Simulate useful features in languages thatlack them– lack of named constants and enumerations in

Fortranuse variables that are initialized once, then neverchanged

– lack of modules in C and Pascaluse comments and programmer discipline

– lack of suitable control structures in Fortranuse comments and programmer discipline forcontrol structures

14

• Simulate useful features in languages thatlack them– lack of named constants and enumerations in

Fortranuse variables that are initialized once, then neverchanged

– lack of modules in C and Pascaluse comments and programmer discipline

– lack of suitable control structures in Fortranuse comments and programmer discipline forcontrol structures

Page 15: Programming Language and Paradigms

Why study programming languages?

• Make it easier to learn new languages– some languages are similar; easy to walk down

family tree– concepts have even more similarity;– if you think in terms of iteration, recursion,

abstraction (for example), you will find it easier toassimilate the syntax and semantic details of anew language than if you try to pick it up in avacuum.

15

• Make it easier to learn new languages– some languages are similar; easy to walk down

family tree– concepts have even more similarity;– if you think in terms of iteration, recursion,

abstraction (for example), you will find it easier toassimilate the syntax and semantic details of anew language than if you try to pick it up in avacuum.

Page 16: Programming Language and Paradigms

Why study programming languages?

• Help you choose a language– C vs. Modula-3 vs. C++ for systems programming– Fortran vs. APL vs. Ada for numerical

computations– Ada vs. Modula-2 for embedded systems– Common Lisp vs. Scheme vs. ML for symbolic data

manipulation– Java vs. C/CORBA for networked PC programs

16

• Help you choose a language– C vs. Modula-3 vs. C++ for systems programming– Fortran vs. APL vs. Ada for numerical

computations– Ada vs. Modula-2 for embedded systems– Common Lisp vs. Scheme vs. ML for symbolic data

manipulation– Java vs. C/CORBA for networked PC programs

Page 17: Programming Language and Paradigms

The Art of Language DesignThe Art of Language Design

Page 18: Programming Language and Paradigms

What is a language for?

• Way of thinking – way of expressing algorithms• Languages from the user's point of view• Abstraction of virtual machine – way of specifying

what you want the hardware to do without gettingdown into the bits

• Languages from the implementer's point of view

• Way of thinking – way of expressing algorithms• Languages from the user's point of view• Abstraction of virtual machine – way of specifying

what you want the hardware to do without gettingdown into the bits

• Languages from the implementer's point of view

18

Page 19: Programming Language and Paradigms

Why are there so many?• Evolution - learn better ways of doing things over time

– goto-based control flow (Fortran)– structured programming (Pascal, C)– object-oriented structure (C++, Java)

• Special purpose– symbolic data– character strings– low-level system programming– reasoning, logical relation

• Socio-economic factors - proprietary interests, commercial advantage

• Personal preference - diverse ideas about what is pleasant to use

• Special hardware

• Evolution - learn better ways of doing things over time– goto-based control flow (Fortran)– structured programming (Pascal, C)– object-oriented structure (C++, Java)

• Special purpose– symbolic data– character strings– low-level system programming– reasoning, logical relation

• Socio-economic factors - proprietary interests, commercial advantage

• Personal preference - diverse ideas about what is pleasant to use

• Special hardware

19

Page 20: Programming Language and Paradigms

What makes a language successful?

• Expressive power – easy to express things, to use once fluent (C, APL,Algol-68, Perl)

• Ease of use for novice – easy to learn (BASIC, Pascal, LOGO)

• Ease of implementation – (BASIC, Forth)

• Standardization – (C, Java)

• Open source - wide dissemination without cost (Pascal, Java)

• Excellent compilers – possible to compile to very good (fast/small)code (Fortran)

• Patronage - backing of a powerful sponsor (COBOL, PL/1, Ada, VisualBasic)

• Expressive power – easy to express things, to use once fluent (C, APL,Algol-68, Perl)

• Ease of use for novice – easy to learn (BASIC, Pascal, LOGO)

• Ease of implementation – (BASIC, Forth)

• Standardization – (C, Java)

• Open source - wide dissemination without cost (Pascal, Java)

• Excellent compilers – possible to compile to very good (fast/small)code (Fortran)

• Patronage - backing of a powerful sponsor (COBOL, PL/1, Ada, VisualBasic)

20

Page 21: Programming Language and Paradigms

Language Evaluation CriteriaLanguage Evaluation Criteria

Page 22: Programming Language and Paradigms

Language Evaluation Criteria

• Readability: the ease with whichprograms can be read and understood

• Writability: the ease with which alanguage can be used to create programs

• Reliability: conformance to specifications(i.e., performs to its specifications underall conditions)

22

• Readability: the ease with whichprograms can be read and understood

• Writability: the ease with which alanguage can be used to create programs

• Reliability: conformance to specifications(i.e., performs to its specifications underall conditions)

Page 23: Programming Language and Paradigms

Evaluation Criteria: Others• Cost

– the ultimate total cost

• 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

23

• Cost– the ultimate total cost

• 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 24: Programming Language and Paradigms

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

24

• 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

Page 25: Programming Language and Paradigms

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

25

• 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 26: Programming Language and Paradigms

Evaluation Criteria: Writability• Simplicity and orthogonality

– Few constructs, a small number of primitives, asmall 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 specifyingoperations

– Example: the inclusion of for statement in manymodern languages

26

• 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 oroperations 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 27: Programming Language and Paradigms

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

27

• 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 ofexpressing an algorithm will necessarily use “unnatural”approaches, and hence reduced reliability

Page 28: Programming Language and Paradigms

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

28

• 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

Page 29: Programming Language and Paradigms

Language Characteristics & CriteriaCriteria

Characteristic Readability Writability ReliabilitySimplicity & orthogonality

Control statements

Data types and structure

Syntax design

Support for abstraction

Expressivity

Type checking

Exception handling

Restricted aliasing 29

CriteriaCharacteristic Readability Writability ReliabilitySimplicity & orthogonality

Control statements

Data types and structure

Syntax design

Support for abstraction

Expressivity

Type checking

Exception handling

Restricted aliasing

Page 30: Programming Language and Paradigms

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 executioncosts

• Readability vs. writability– Another conflicting criteria– Example: APL provides many powerful operators (and a large

number of new symbols), allowing complex computations to bewritten 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 used30

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

• Readability vs. writability– Another conflicting criteria– Example: APL provides many powerful operators (and a large

number of new symbols), allowing complex computations to bewritten 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 31: Programming Language and Paradigms

Programming LanguageParadigms

Programming LanguageParadigms

Page 32: Programming Language and Paradigms

Programming Paradigms• Imperative

– Central features are variables, assignment statements, anditeration

– 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 togiven 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

32

• 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

Page 33: Programming Language and Paradigms

Programming Paradigms

• Imperative– Von Neumann (Fortran, Pascal, Basic, C)– Scripting (Perl, Python, JavaScript, PHP)– Object-oriented (Smalltalk, Eiffel, C++)

• Declarative– Functional (Scheme, ML, pure Lisp, FP)– Logic, constraint-based (Prolog, VisiCalc, RPG)

• Imperative– Von Neumann (Fortran, Pascal, Basic, C)– Scripting (Perl, Python, JavaScript, PHP)– Object-oriented (Smalltalk, Eiffel, C++)

• Declarative– Functional (Scheme, ML, pure Lisp, FP)– Logic, constraint-based (Prolog, VisiCalc, RPG)

33

Page 34: Programming Language and Paradigms

Programming Paradigms: Alternatives

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

34

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

Page 35: Programming Language and Paradigms

Example of GCD programint 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

35

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.

Page 36: Programming Language and Paradigms

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

36

• 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

Page 37: Programming Language and Paradigms

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

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

37

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

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

Page 38: Programming Language and Paradigms

A BriefHistoricalLineage ofSome KeyProgrammingLanguages

38

Page 39: Programming Language and Paradigms

Implementation MethodsImplementation Methods

Page 40: Programming Language and Paradigms

Layered Viewof Computer

Virtual computer– the OS andlanguageimplementationwhich are layeredover machineinterface ofa computer

40

Virtual computer– the OS andlanguageimplementationwhich are layeredover machineinterface ofa computer

Page 41: Programming Language and Paradigms

Implementation Methods

• Compilation– Programs are translated into machine

language

• Pure Interpretation– Programs are interpreted by another

program known as an interpreter

• Hybrid /Mixing– A compromise between compilers and

pure interpreters

41

• Compilation– Programs are translated into machine

language

• Pure Interpretation– Programs are interpreted by another

program known as an interpreter

• Hybrid /Mixing– A compromise between compilers and

pure interpreters

Page 42: Programming Language and Paradigms

Implementation Methods

• Interpretation:– Greater flexibility– Better diagnostics (error messages)

• Compilation– Better performance

42

• Interpretation:– Greater flexibility– Better diagnostics (error messages)

• Compilation– Better performance

Page 43: Programming Language and Paradigms

Implementation Methods

• Compilation

• Interpretation

• Mixing• Compilation

• Interpretation

43Copyright © 2009 Elsevier, Inc. All rights reserved.

Page 44: Programming Language and Paradigms

44

Page 45: Programming Language and Paradigms

Implementation Methods

• Library routines and linking • Post-compilation assembly

45Copyright © 2009 Elsevier, Inc. All rights reserved.

Page 46: Programming Language and Paradigms

Overview of Compilation

46 Copyright © 2009 Elsevier, Inc. All rights reserved.

Page 47: Programming Language and Paradigms

Overview of Compilation

• Lexical analysis• Syntax analysis• Semantic Analysis & intermediate code

generation• Target code generation• Code improvement

47

• Lexical analysis• Syntax analysis• Semantic Analysis & intermediate code

generation• Target code generation• Code improvement

Page 48: Programming Language and Paradigms

Overview of Compilation• Lexical and Syntax Analysis

GCD Program (in C)

int main() {int i = getint(), j = getint();while (i != j) {if (i > j) i = i - j;else j = j - i;}putint(i);}

48

int main() {int i = getint(), j = getint();while (i != j) {if (i > j) i = i - j;else j = j - i;}putint(i);}

Page 49: Programming Language and Paradigms

Overview of Compilation• Lexical Analysis

• Scanning and parsing recognize the structure ofthe program, groups characters into tokens, thesmallest meaningful units of the program

GCD Program Tokens

49

• Lexical Analysis• Scanning and parsing recognize the structure of

the program, groups characters into tokens, thesmallest meaningful units of the program

GCD Program Tokensint main ( ) {int i = getint ( ) , j = getint ( ) ;while ( i != j ) {if ( i > j ) i = i - j ;else j = j - i ;}Putint ( i ) ;}

Page 50: Programming Language and Paradigms

Overview of Compilation

• Syntax Analysis– Context-Free Grammar and Parsing

• Parsing organizes tokens into a parse tree thatrepresents higher-level constructs in terms oftheir constituents

• Potentially recursive rules known as context-free grammar define the ways in which theseconstituents combine

50

• Syntax Analysis– Context-Free Grammar and Parsing

• Parsing organizes tokens into a parse tree thatrepresents higher-level constructs in terms oftheir constituents

• Potentially recursive rules known as context-free grammar define the ways in which theseconstituents combine

Page 51: Programming Language and Paradigms

Overview of Compilation

• Context-Free Grammar and ParsingExample (while loop in C)

iteration-statement → while ( expression ) statement

statement, in turn, is often a list enclosed in braces:statement → compound-statementcompound-statement → { block-item-list opt }whereblock-item-list opt → block-item-listorblock-item-list opt → ϵandblock-item-list → block-itemblock-item-list → block-item-list block-itemblock-item → declarationblock-item → statement

51

iteration-statement → while ( expression ) statement

statement, in turn, is often a list enclosed in braces:statement → compound-statementcompound-statement → { block-item-list opt }whereblock-item-list opt → block-item-listorblock-item-list opt → ϵandblock-item-list → block-itemblock-item-list → block-item-list block-itemblock-item → declarationblock-item → statement

Page 52: Programming Language and Paradigms

Overview of Compilation• Context-Free Grammar and Parsing

GCD Program Parse Tree

52 next slide

A

B

Page 53: Programming Language and Paradigms

Overview of Compilation• Context-Free Grammar and Parsing

53

Page 54: Programming Language and Paradigms

Overview of Compilation• Context-Free Grammar and Parsing

A B

54

Page 55: Programming Language and Paradigms

Overview of Compilation• Syntax Tree - GCD Program Parse Tree

55 Copyright © 2009 Elsevier, Inc. All rights reserved.

Page 56: Programming Language and Paradigms

Programming EnvironmentsProgramming Environments

Page 57: Programming Language and Paradigms

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

57

• 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 58: Programming Language and Paradigms

Programming Environments

Tools

58

Page 59: Programming Language and Paradigms

Programming Languages: Trend

59

Page 60: Programming Language and Paradigms

Programm

ing Languages:Trend

60

Programm

ing Languages:Trend

Page 61: Programming Language and Paradigms

References

Books• 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_programm

ing_languages• timeline: http://www.levenez.com/lang/lang_a4.pdf

61

Books• 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_programm

ing_languages• timeline: http://www.levenez.com/lang/lang_a4.pdf