Denotational Semantics ______

Total Page:16

File Type:pdf, Size:1020Kb

Denotational Semantics ______ Denotational Semantics ____________________________________________________________________________ ____________________________________________________________________________ ____________________________________________________________________________ A METHODOLOGY FOR LANGUAGE DEVELOPMENT ____________________________________________________________________________ ____________________________________________________________________________ David A. Schmidt Copyright notice: Copyright ! 1997 by David A. Schmidt. Permission to reproduce this material must be obtained from the author. Author’s address: David Schmidt, Department of Computing and Information Sciences, 234 Nichols Hall, Kansas State University, Manhattan, KS 66506. [email protected] Contents Preface viii Chapter 0 INTRODUCTION _______________________________________________________________________________________________ 1 Methods for Semantics Specification 2 Suggested Readings 3 Chapter 1 SYNTAX _____________________________________________________________________________________________________________ 5 1.1 Abstract Syntax Definitions 9 1.2 Mathematical and Structural Induction 12 Suggested Readings 15 Exercises 15 Chapter 2 SETS, FUNCTIONS, AND DOMAINS _____________________________________________________________ 17 2.1 Sets 17 2.1.1 Constructions on Sets 18 2.2 Functions 20 2.2.1 Representing Functions as Sets 21 2.2.2 Representing Functions as Equations 24 2.3 Semantic Domains 25 2.3.1 Semantic Algebras 25 Suggested Readings 27 Exercises 27 Chapter 3 DOMAIN THEORY I: SEMANTIC ALGEBRAS ___________________________________________ 30 3.1 Primitive Domains 30 3.2 Compound Domains 34 3.2.1 Product 34 3.2.2 Disjoint Union 35 3.2.3 Function Space 39 3.2.4 Lifted Domains and Strictness 42 iii iv Contents 3.3 Recursive Function Definitions 44 3.4 Recursive Domain Definitions 46 3.5 Summary 46 Suggested Readings 48 Exercises 48 Chapter 4 BASIC STRUCTURE OF DENOTATIONAL DEFINITIONS _______________________ 54 4.1 The Valuation Function 54 4.2 Format of a Denotational Definition 57 4.3 A Calculator Language 59 Suggested Readings 63 Exercises 63 Chapter 5 IMPERATIVE LANGUAGES ___________________________________________________________________________ 66 5.1 A Language with Assignment 66 5.1.1 Programs are Functions 72 5.2 An Interactive File Editor 73 5.2.1 Interactive Input and Partial Syntax 78 5.3 A Dynamically Typed Language with Input and Output 80 5.4 Altering the Properties of Stores 82 5.4.1 Delayed Evaluation 82 5.4.2 Retaining Multiple Stores 86 5.4.3 Noncommunicating Commands 87 Suggested Readings 88 Exercises 88 Chapter 6 DOMAIN THEORY II: RECURSIVELY DEFINED FUNCTIONS _______________ 94 6.1 Some Recursively Defined Functions 95 6.2 Partial Orderings 98 6.3 Continuous Functions 102 6.4 Least Fixed Points 103 6.5 Domains are Cpos 104 6.6 Examples 109 6.6.1 Factorial Function 109 6.6.2 Copyout Function 110 6.6.3 Double Recursion 111 6.6.4 Simultaneous Definitions 111 v 6.6.5 The While-Loop 112 6.6.6 Soundness of Hoare’s Logic 115 6.7 Reasoning about Least Fixed Points 117 Suggested Readings 119 Exercises 120 Chapter 7 LANGUAGES WITH CONTEXTS ___________________________________________________________________ 125 7.1 A Block-Structured Language 127 7.1.1 Stack-Managed Storage 134 7.1.2 The Meanings of Identifiers 136 7.2 An Applicative Language 137 7.2.1 Scoping Rules 140 7.2.2 Self-Application 143 7.2.3 Recursive Declarations 145 7.3 Compound Data Structures 148 Suggested Readings 154 Exercises 154 Chapter 8 ABSTRACTION, CORRESPONDENCE, AND QUALIFICATION ______________ 160 8.1 Abstraction 161 8.1.1 Recursive Bindings 164 8.2 Parameterization 165 8.2.1 Polymorphism and Typing 167 8.3 Correspondence 170 8.4 Qualification 171 8.5 Orthogonality 173 Suggested Readings 174 Exercises 174 Chapter 9 CONTROL AS A SEMANTIC DOMAIN _________________________________________________________ 178 9.1 Continuations 178 9.1.1 Other Levels of Continuations 181 9.2 Exception Mechanisms 182 9.3 Backtracking Mechanisms 183 9.4 Coroutine Mechanisms 183 9.5 Unrestricted Branching Mechanisms 187 vi Contents 9.6 The Relationship between Direct and Continuation Semantics 193 Suggested Readings 195 Exercises 195 Chapter 10 IMPLEMENTATION OF DENOTATIONAL DEFINITIONS _______________________ 199 10.1 A General Method of Implementation 199 10.1.1 The SIS and SPS Systems 200 10.2 Static Semantics Processing 201 10.3 The Structure of the Evaluator 203 10.3.1 A Stack-Based Evaluator 204 10.3.2 PSP and Appel’s System 208 10.4 Combinator-Based Semantic Notations 209 10.4.1 The Plumb and CERES Systems 211 10.5 Transformations on the Semantic Definition 212 10.5.1 First-Order Data Objects 212 10.5.2 Global Variables 214 10.5.3 Control Structures 217 10.6 Implementation of Continuation-Based Definitions 218 10.6.1 The CGP and VDM Methods 222 10.7 Correctness of Implementation and Full Abstraction 223 Suggested Readings 225 Exercises 226 Chapter 11 DOMAIN THEORY III: RECURSIVE DOMAIN SPECIFICATIONS _________ 230 11.1 Reflexive Domains Have Infinite Elements 230 11.2 The Inverse Limit Construction 234 11.3 Applications 241 11.3.1 Linear Lists 242 11.3.2 Self-Applicative Procedures 243 11.3.3 Recursive Record Structures 244 Suggested Readings 245 Exercises 245 Chapter 12 NONDETERMINISM AND CONCURRENCY _______________________________________________ 250 12.1 Powerdomains 251 12.2 The Guarded Command Language 251 vii 12.3 Concurrency and Resumption Semantics 254 12.4 An Alternative Semantics for Concurrency 258 12.5 The Powerdomain Structure 265 12.5.1 Discrete Powerdomains 266 12.5.2 General Powerdomains 268 Suggested Readings 274 Exercises 274 Bibliography 217 Preface Denotational semantics is a methodology for giving mathematical meaning to programming languages and systems. It was developed by Christopher Strachey’s Programming Research Group at Oxford University in the 1960s. The method combines mathematical rigor, due to the work of Dana Scott, with notational elegance, due to Strachey. Originally used as an analysis tool, denotational semantics has grown in use as a tool for language design and implementa- tion. This book was written to make denotational semantics accessible to a wider audience and to update existing texts in the area. I have presented the topic from an engineering viewpoint, emphasizing the descriptional and implementational aspects. The relevant mathematics is also included, for it gives rigor and validity to the method and provides a foundation for further research. The book is intended as a tutorial for computing professionals and as a text for university courses at the upper undergraduate or beginning graduate level. The reader should be acquainted with discrete structures and one or more general purpose programming languages. Experience with an applicative-style language such as LISP, ML, or Scheme is also helpful. CONTENTS OF THE BOOK ________________________________________________________________________________________________ The Introduction and Chapters 1 through 7 form the core of the book. The Introduction pro- vides motivation and a brief survey of semantics specification methods. Chapter 1 introduces BNF, abstract syntax, and structural induction. Chapter 2 lists those concepts of set theory that are relevant to semantic domain theory. Chapter 3 covers semantic domains, the value sets used in denotational semantics. The fundamental domains and their related operations are presented. Chapter 4 introduces basic denotational semantics. Chapter 5 covers the semantics of computer storage and assignment as found in conventional imperative languages. Nontradi- tional methods of store evaluation are also considered. Chapter 6 presents least fixed point semantics, which is used for determining the meaning of iterative and recursive definitions. The related semantic domain theory is expanded to include complete partial orderings; ‘‘predomains’’ (complete partial orderings less ‘‘bottom’’ elements) are used. Chapter 7 cov- ers block structure and data structures. Chapters 8 through 12 present advanced topics. Tennent’s analysis of procedural abstrac- tion and general binding mechanisms is used as a focal point for Chapter 8. Chapter 9 analyzes forms of imperative control and branching. Chapter 10 surveys techniques for converting a denotational definition into a computer implementation. Chapter 11 contains an overview of Scott’s inverse limit construction for building recursively defined domains. Chapter 12 closes the book with an introduction to methods for understanding nondeterminism and concurrency. Throughout the book I have consistently abused the noun ‘‘access,’’ treating it as a verb. Also, ‘‘iff’’ abbreviates the phrase ‘‘if and only if.’’ viii Preface ix ORGANIZATION OF A COURSE _______________________________________________________________________________________ The book contains more material than what can be comfortably covered in one term. A course plan should include the core chapters; any remaining time can be used for Chapters 8 through 12, which are independent of one another and can be read in any order. The core can be han- dled as follows: • Present the Introduction first. You may wish to give a one lecture preview of Chapter 4. A preview motivates the students to carefully study the material in the background Chapters 1 through 3. • Cover all of Chapters 1 and 2, as they are short and introduce crucial concepts. • Use Chapter 3 as a ‘‘reference manual.’’ You may wish to start at the summary Section 3.5 and outline the structures of semantic domains. Next, present
Recommended publications
  • Operational Semantics Page 1
    Operational Semantics Page 1 Operational Semantics Class notes for a lecture given by Mooly Sagiv Tel Aviv University 24/5/2007 By Roy Ganor and Uri Juhasz Reference Semantics with Applications, H. Nielson and F. Nielson, Chapter 2. http://www.daimi.au.dk/~bra8130/Wiley_book/wiley.html Introduction Semantics is the study of meaning of languages. Formal semantics for programming languages is the study of formalization of the practice of computer programming. A computer language consists of a (formal) syntax – describing the actual structure of programs and the semantics – which describes the meaning of programs. Many tools exist for programming languages (compilers, interpreters, verification tools, … ), the basis on which these tools can cooperate is the formal semantics of the language. Formal Semantics When designing a programming language, formal semantics gives an (hopefully) unambiguous definition of what a program written in the language should do. This definition has several uses: • People learning the language can understand the subtleties of its use • The model over which the semantics is defined (the semantic domain) can indicate what the requirements are for implementing the language (as a compiler/interpreter/…) • Global properties of any program written in the language, and any state occurring in such a program, can be understood from the formal semantics • Implementers of tools for the language (parsers, compilers, interpreters, debuggers etc) have a formal reference for their tool and a formal definition of its correctness/completeness
    [Show full text]
  • Denotational Semantics
    Denotational Semantics CS 6520, Spring 2006 1 Denotations So far in class, we have studied operational semantics in depth. In operational semantics, we define a language by describing the way that it behaves. In a sense, no attempt is made to attach a “meaning” to terms, outside the way that they are evaluated. For example, the symbol ’elephant doesn’t mean anything in particular within the language; it’s up to a programmer to mentally associate meaning to the symbol while defining a program useful for zookeeppers. Similarly, the definition of a sort function has no inherent meaning in the operational view outside of a particular program. Nevertheless, the programmer knows that sort manipulates lists in a useful way: it makes animals in a list easier for a zookeeper to find. In denotational semantics, we define a language by assigning a mathematical meaning to functions; i.e., we say that each expression denotes a particular mathematical object. We might say, for example, that a sort implementation denotes the mathematical sort function, which has certain properties independent of the programming language used to implement it. In other words, operational semantics defines evaluation by sourceExpression1 −→ sourceExpression2 whereas denotational semantics defines evaluation by means means sourceExpression1 → mathematicalEntity1 = mathematicalEntity2 ← sourceExpression2 One advantage of the denotational approach is that we can exploit existing theories by mapping source expressions to mathematical objects in the theory. The denotation of expressions in a language is typically defined using a structurally-recursive definition over expressions. By convention, if e is a source expression, then [[e]] means “the denotation of e”, or “the mathematical object represented by e”.
    [Show full text]
  • Quantum Weakest Preconditions
    Quantum Weakest Preconditions Ellie D’Hondt ∗ Prakash Panangaden †‡ Abstract We develop a notion of predicate transformer and, in particular, the weak- est precondition, appropriate for quantum computation. We show that there is a Stone-type duality between the usual state-transformer semantics and the weakest precondition semantics. Rather than trying to reduce quantum com- putation to probabilistic programming we develop a notion that is directly taken from concepts used in quantum computation. The proof that weak- est preconditions exist for completely positive maps follows from the Kraus representation theorem. As an example we give the semantics of Selinger’s language in terms of our weakest preconditions. 1 Introduction Quantum computation is a field of research that is rapidly acquiring a place as a significant topic in computer science. To be sure, there are still essential tech- nological and conceptual problems to overcome in building functional quantum computers. Nevertheless there are fundamental new insights into quantum com- putability [Deu85, DJ92], quantum algorithms [Gro96, Gro97, Sho94, Sho97] and into the nature of quantum mechanics itself [Per95], particularly with the emer- gence of quantum information theory [NC00]. These developments inspire one to consider the problems of programming full-fledged general purpose quantum computers. Much of the theoretical re- search is aimed at using the new tools available - superposition, entanglement and linearity - for algorithmic efficiency. However, the fact that quantum algorithms are currently done at a very low level only - comparable to classical computing 60 years ago - is a much less explored aspect of the field. The present paper is ∗Centrum Leo Apostel , Vrije Universiteit Brussel, Brussels, Belgium, [email protected].
    [Show full text]
  • Operational Semantics with Hierarchical Abstract Syntax Graphs*
    Operational Semantics with Hierarchical Abstract Syntax Graphs* Dan R. Ghica Huawei Research, Edinburgh University of Birmingham, UK This is a motivating tutorial introduction to a semantic analysis of programming languages using a graphical language as the representation of terms, and graph rewriting as a representation of reduc- tion rules. We show how the graphical language automatically incorporates desirable features, such as a-equivalence and how it can describe pure computation, imperative store, and control features in a uniform framework. The graph semantics combines some of the best features of structural oper- ational semantics and abstract machines, while offering powerful new methods for reasoning about contextual equivalence. All technical details are available in an extended technical report by Muroya and the author [11] and in Muroya’s doctoral dissertation [21]. 1 Hierarchical abstract syntax graphs Before proceeding with the business of analysing and transforming the source code of a program, a com- piler first parses the input text into a sequence of atoms, the lexemes, and then assembles them into a tree, the Abstract Syntax Tree (AST), which corresponds to its grammatical structure. The reason for preferring the AST to raw text or a sequence of lexemes is quite obvious. The structure of the AST incor- porates most of the information needed for the following stage of compilation, in particular identifying operations as nodes in the tree and operands as their branches. This makes the AST algorithmically well suited for its purpose. Conversely, the AST excludes irrelevant lexemes, such as separators (white-space, commas, semicolons) and aggregators (brackets, braces), by making them implicit in the tree-like struc- ture.
    [Show full text]
  • Making Classes Provable Through Contracts, Models and Frames
    View metadata, citation and similar papers at core.ac.uk brought to you by CORE provided by CiteSeerX DISS. ETH NO. 17610 Making classes provable through contracts, models and frames A dissertation submitted to the SWISS FEDERAL INSTITUTE OF TECHNOLOGY ZURICH (ETH Zurich)¨ for the degree of Doctor of Sciences presented by Bernd Schoeller Diplom-Informatiker, TU Berlin born April 5th, 1974 citizen of Federal Republic of Germany accepted on the recommendation of Prof. Dr. Bertrand Meyer, examiner Prof. Dr. Martin Odersky, co-examiner Prof. Dr. Jonathan S. Ostroff, co-examiner 2007 ABSTRACT Software correctness is a relation between code and a specification of the expected behavior of the software component. Without proper specifica- tions, correct software cannot be defined. The Design by Contract methodology is a way to tightly integrate spec- ifications into software development. It has proved to be a light-weight and at the same time powerful description technique that is accepted by software developers. In its more than 20 years of existence, it has demon- strated many uses: documentation, understanding object-oriented inheri- tance, runtime assertion checking, or fully automated testing. This thesis approaches the formal verification of contracted code. It conducts an analysis of Eiffel and how contracts are expressed in the lan- guage as it is now. It formalizes the programming language providing an operational semantics and a formal list of correctness conditions in terms of this operational semantics. It introduces the concept of axiomatic classes and provides a full library of axiomatic classes, called the mathematical model library to overcome prob- lems of contracts on unbounded data structures.
    [Show full text]
  • A Denotational Semantics Approach to Functional and Logic Programming
    A Denotational Semantics Approach to Functional and Logic Programming TR89-030 August, 1989 Frank S.K. Silbermann The University of North Carolina at Chapel Hill Department of Computer Science CB#3175, Sitterson Hall Chapel Hill, NC 27599-3175 UNC is an Equal OpportunityjAfflrmative Action Institution. A Denotational Semantics Approach to Functional and Logic Programming by FrankS. K. Silbermann A dissertation submitted to the faculty of the University of North Carolina at Chapel Hill in par­ tial fulfillment of the requirements for the degree of Doctor of Philosophy in Computer Science. Chapel Hill 1989 @1989 Frank S. K. Silbermann ALL RIGHTS RESERVED 11 FRANK STEVEN KENT SILBERMANN. A Denotational Semantics Approach to Functional and Logic Programming (Under the direction of Bharat Jayaraman.) ABSTRACT This dissertation addresses the problem of incorporating into lazy higher-order functional programming the relational programming capability of Horn logic. The language design is based on set abstraction, a feature whose denotational semantics has until now not been rigorously defined. A novel approach is taken in constructing an operational semantics directly from the denotational description. The main results of this dissertation are: (i) Relative set abstraction can combine lazy higher-order functional program­ ming with not only first-order Horn logic, but also with a useful subset of higher­ order Horn logic. Sets, as well as functions, can be treated as first-class objects. (ii) Angelic powerdomains provide the semantic foundation for relative set ab­ straction. (iii) The computation rule appropriate for this language is a modified parallel­ outermost, rather than the more familiar left-most rule. (iv) Optimizations incorporating ideas from narrowing and resolution greatly improve the efficiency of the interpreter, while maintaining correctness.
    [Show full text]
  • Denotational Semantics
    Denotational Semantics 8–12 lectures for Part II CST 2010/11 Marcelo Fiore Course web page: http://www.cl.cam.ac.uk/teaching/1011/DenotSem/ 1 Lecture 1 Introduction 2 What is this course about? • General area. Formal methods: Mathematical techniques for the specification, development, and verification of software and hardware systems. • Specific area. Formal semantics: Mathematical theories for ascribing meanings to computer languages. 3 Why do we care? • Rigour. specification of programming languages . justification of program transformations • Insight. generalisations of notions computability . higher-order functions ... data structures 4 • Feedback into language design. continuations . monads • Reasoning principles. Scott induction . Logical relations . Co-induction 5 Styles of formal semantics Operational. Meanings for program phrases defined in terms of the steps of computation they can take during program execution. Axiomatic. Meanings for program phrases defined indirectly via the ax- ioms and rules of some logic of program properties. Denotational. Concerned with giving mathematical models of programming languages. Meanings for program phrases defined abstractly as elements of some suitable mathematical structure. 6 Basic idea of denotational semantics [[−]] Syntax −→ Semantics Recursive program → Partial recursive function Boolean circuit → Boolean function P → [[P ]] Concerns: • Abstract models (i.e. implementation/machine independent). Lectures 2, 3 and 4. • Compositionality. Lectures 5 and 6. • Relationship to computation (e.g. operational semantics). Lectures 7 and 8. 7 Characteristic features of a denotational semantics • Each phrase (= part of a program), P , is given a denotation, [[P ]] — a mathematical object representing the contribution of P to the meaning of any complete program in which it occurs. • The denotation of a phrase is determined just by the denotations of its subphrases (one says that the semantics is compositional).
    [Show full text]
  • Probabilistic Predicate Transformers
    Probabilistic Predicate Transformers CARROLL MORGAN, ANNABELLE McIVER, and KAREN SEIDEL Oxford University Probabilistic predicates generalize standard predicates over a state space; with probabilistic pred- icate transformers one thus reasons about imperative programs in terms of probabilistic pre- and postconditions. Probabilistic healthiness conditions generalize the standard ones, characterizing “real” probabilistic programs, and are based on a connection with an underlying relational model for probabilistic execution; in both contexts demonic nondeterminism coexists with probabilis- tic choice. With the healthiness conditions, the associated weakest-precondition calculus seems suitable for exploring the rigorous derivation of small probabilistic programs. Categories and Subject Descriptors: D.2.4 [Program Verification]: Correctness Proofs; D.3.1 [Programming Languages]: Formal Definitions and Theory; F.1.2 [Modes of Computation]: Probabilistic Computation; F.3.1 [Semantics of Programming Languages]: Specifying and Ver- ifying and Reasoning about Programs; G.3 [Probability and Statistics]: Probabilistic Algorithms General Terms: Verification, Theory, Algorithms, Languages Additional Key Words and Phrases: Galois connection, nondeterminism, predicate transformers, probability, program derivation, refinement, weakest preconditions 1. MOTIVATION AND INTRODUCTION The weakest-precondition approach of Dijkstra [1976] has been reasonably success- ful for rigorous derivation of small imperative programs, even (and especially) those involving demonic
    [Show full text]
  • Mechanized Semantics of Simple Imperative Programming Constructs*
    App eared as technical rep ort UIB Universitat Ulm Fakultat fur Informatik Dec Mechanized Semantics of Simple Imp erative Programming Constructs H Pfeifer A Dold F W von Henke H Rue Abt Kunstliche Intelligenz Fakultat fur Informatik Universitat Ulm D Ulm verifixkiinformatikuniulmde Abstract In this pap er a uniform formalization in PVS of various kinds of semantics of imp er ative programming language constructs is presented Based on a comprehensivede velopment of xed p oint theory the denotational semantics of elementary constructs of imp erative programming languages are dened as state transformers These state transformers induce corresp onding predicate transformers providing a means to for mally derivebothaweakest lib eral precondition semantics and an axiomatic semantics in the style of Hoare Moreover algebraic laws as used in renement calculus pro ofs are validated at the level of predicate transformers Simple reformulations of the state transformer semantics yield b oth a continuationstyle semantics and rules similar to those used in Structural Op erational Semantics This formalization provides the foundations on which formal sp ecication of program ming languages and mechanical verication of compilation steps are carried out within the Verix pro ject This research has b een funded in part by the Deutsche Forschungsgemeinschaft DFG under pro ject Verix Contents Intro duction Related Work Overview A brief description of PVS Mechanizing Domain
    [Show full text]
  • Chapter 3 – Describing Syntax and Semantics CS-4337 Organization of Programming Languages
    !" # Chapter 3 – Describing Syntax and Semantics CS-4337 Organization of Programming Languages Dr. Chris Irwin Davis Email: [email protected] Phone: (972) 883-3574 Office: ECSS 4.705 Chapter 3 Topics • Introduction • The General Problem of Describing Syntax • Formal Methods of Describing Syntax • Attribute Grammars • Describing the Meanings of Programs: Dynamic Semantics 1-2 Introduction •Syntax: the form or structure of the expressions, statements, and program units •Semantics: the meaning of the expressions, statements, and program units •Syntax and semantics provide a language’s definition – Users of a language definition •Other language designers •Implementers •Programmers (the users of the language) 1-3 The General Problem of Describing Syntax: Terminology •A sentence is a string of characters over some alphabet •A language is a set of sentences •A lexeme is the lowest level syntactic unit of a language (e.g., *, sum, begin) •A token is a category of lexemes (e.g., identifier) 1-4 Example: Lexemes and Tokens index = 2 * count + 17 Lexemes Tokens index identifier = equal_sign 2 int_literal * mult_op count identifier + plus_op 17 int_literal ; semicolon Formal Definition of Languages • Recognizers – A recognition device reads input strings over the alphabet of the language and decides whether the input strings belong to the language – Example: syntax analysis part of a compiler - Detailed discussion of syntax analysis appears in Chapter 4 • Generators – A device that generates sentences of a language – One can determine if the syntax of a particular sentence is syntactically correct by comparing it to the structure of the generator 1-5 Formal Methods of Describing Syntax •Formal language-generation mechanisms, usually called grammars, are commonly used to describe the syntax of programming languages.
    [Show full text]
  • 1 a Denotational Semantics for IMP
    CS 4110 – Programming Languages and Logics .. Lecture #8: Denotational Semantics . We have now seen two operational models for programming languages: small-step and large-step. In this lecture, we consider a different semantic model, called denotational semantics. The idea in denotational semantics is to express the meaning of a program as the mathematical function that expresses what the program computes. We can think of an IMP program c as a function from stores to stores: given an an initial store, the program produces a nal store. For example, the program foo := bar+1 0 can be thought of as a function that when given an input store σ, produces a nal store σ that is identical 0 to σ except that it maps foo to the integer σ(bar) + 1; that is, σ = σ[foo 7! σ(bar) + 1]. We will model programs as functions from input stores to output stores. As opposed to operational models, which tell us how programs execute, the denotational model shows us what programs compute. 1 A Denotational Semantics for IMP For each program c, we write C[[c]] for the denotation of c, that is, the mathematical function that c represents: C[[c]] : Store * Store: Note that C[[c]] is actually a partial function (as opposed to a total function), both because the store may not be dened on the free variables of the program and because program may not terminate for certain input stores. The function C[[c]] is not dened for non-terminating programs as they have no corresponding output stores. We will write C[[c]]σ for the result of applying the function C[[c]] to the store σ.
    [Show full text]
  • Chapter 1 Introduction
    Chapter Intro duction A language is a systematic means of communicating ideas or feelings among people by the use of conventionalized signs In contrast a programming lan guage can be thought of as a syntactic formalism which provides ameans for the communication of computations among p eople and abstract machines Elements of a programming language are often called programs They are formed according to formal rules which dene the relations between the var ious comp onents of the language Examples of programming languages are conventional languages likePascal or C and also the more the oretical languages such as the calculus or CCS A programming language can b e interpreted on the basis of our intuitive con cept of computation However an informal and vague interpretation of a pro gramming language may cause inconsistency and ambiguity As a consequence dierent implementations maybegiven for the same language p ossibly leading to dierent sets of computations for the same program Had the language in terpretation b een dened in a formal way the implementation could b e proved or disproved correct There are dierent reasons why a formal interpretation of a programming language is desirable to give programmers unambiguous and p erhaps informative answers ab out the language in order to write correct programs to give implementers a precise denition of the language and to develop an abstract but intuitive mo del of the language in order to reason ab out programs and to aid program development from sp ecications Mathematics often emphasizes
    [Show full text]