DOCSLIB.ORG

Programming in Modula-3

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Programming in Modula-3 Programming in Modula-3 Springer Berlin Heidelberg New York Barcelona Budapest Hong Kong London Milan Paris Santa Clara Singapore Tokyo Laszlo Boszormenyi Carsten Weich Programming in Modula-3 An Introduction in Programming with Style Foreword by Joseph Weizenbaum , Springer Usz16 Boszormenyi Carsten Weich U niversitat Klagenfurt Institutfiir Informatik UniversitatsstraBe 65-67 A-9022 Klagenfurt With 61 figures The software environment was created with the kind support of Springer­ Verlag, Digital Equipment Corporation, and Raiffeisenverband Karnten Translated from the German edition Programmieren mit Modula-3 by Robert Bach, Traunkirchen, Austria ISBN-13: 978-3-642-64614-0 e-ISBN-13: 978-3-642-60940-4 DOl: 10.1007/978-3-642-60940-4 CIP-data applied for Die Deutsche Bibliothek CIP-Einheitsaufnahme programming in Modula-3: an introduction in programming with style / Uszl6 Boszormenyi; Carsten Weich. Foreword by Joseph Weizenbaum [Trans!. from the German ed. by Robert Bach J. - Berlin; Heidelberg; New York; Barcelona; Budapest; Hong Kong; London; Milan; Paris; Santa Clara; Signapore; Tokyo: Springer; 1996 Dt. Ausg. u.d.T.: Boszormenyi. Uszl6: Programmieren mit Modula-3 ISBN-13: 978-3-642-64614-0 NE: Weich. Carsten: This work is subject to copyright. All rights are reserved. whether the whole or part of the material is concerned. specifically the rights oftranslation. reprinting. reuse ofillustrations. recitation. broadcasting. reproduction on microfilm or in other ways. and storage in data banks. Duplication ofthis publication or parts thereofis permiuedonlyunder the provisions of the German Copyright Law of September 9.1965. in its current version. and permission for use must always be obtained from Springer-Verlag. Violations are liable for prosecution act under German Copyright Law. © Springer-Verlag Berlin Heidelberg 1996 Softcover reprint ofthe hardcover 1st edition 1996 The use ofgeneral descriptive names. registered names. trademarks. etc. in this publication does not imply. even in the absence of a specific statement. that such names are exempt from the relevant protective laws and regulations and therefore free for general use. Typesetting: Camera-ready by authors; Cover illustration: Hegedus Miklos Cover design: Klinkel + Lopka Werbeagentur. Ilvesheim SPIN:I0426494 33/3020-543210 - Printed on acid -free paper To Joseph Weizenbaum Foreword by Joseph Weizenbaum Since the dawn of the age of computers, people have cursed the difficulty of programming. Over and over again we encounter the suggestion that we should be able to communicate to a computer in natural language what we want it to do. Unfortunately, such advice rests upon a misconception of both the computer and its task. The computer might not be stupid, but it is stubborn. That is, the computer does what all the details of its pro­ gram command it to do, i.e., what the programmer "tells" it to do. And this can be quite different from what the programmer intended. The misun­ derstanding with respect to tasks posed to the computer arises from the failure to recognize that such tasks can scarcely be expressed in natural language, if indeed at all. For example, can we practice music, chemistry or mathematics without their respective special symbolic languages? Yet books about computers and programming languages can be written more or less reasonably, even if they are not quite poetic or lyrical. This book can serve as an example of this art and as a model for anyone at­ tempting to teach inherently difficult subject matters to others. Klagenfurt, April 1995 Preface Striving to make learning to program easier, this book addresses primarily students beginning a computer science major. For our program examples, we employ a new, elegant programming language, Modula-3. However, most of the concepts that we introduce apply and are relevant indepen­ dently of the specific programming language. This book can either accompany an introductory lecture on program­ ming or serve self-study purposes. Both cases absolutely demand hands-on programming practice in addition to reading the book. Perusing a book on programming in dry dock without ever navigating the challenging waters of programming would be like reading about how to playa violin without ever touching the instrument. Learning to program means mastering both theory and practice, preferably simultaneously. Newcomers to a computer science major bring with them a broad range of different backgrounds. Some have no computer literacy, while others can handle certain application programs such as word processors or spread­ sheets. Still others have programming experience, although the breadth and depth of their skills varies greatly. This book assumes no particular prerequisites. A reader armed with normal high school mathematics and rudimentary computer literacy should be able to understand this book. We begin with fundamental concepts and only stepwise introduce the more dif­ ficult, higher-level concepts that build on them. To avoid the risk of bore­ dom, students with a higher level of programming experience should feel free to skim over exhaustive explanations that are already clear to them. Organization of the Book The book consists offive parts: 1. Introduction In the first chapter we cast light on the term programming from var­ ious perspectives and show their relative importance in the field of computer science. The second chapter introduces a formal notation for the precise specification of the syntax of programming languages. x 2. Introduction to Programming Chapters 3 to 10 introduce the classical programming concepts. Be­ ginning with a sequence of statements and many simple and user­ defined static types, these chapters move on to arm the reader with procedures, functions and modules to be able to correctly structure even complex problems. On completion of Chapter 10, the reader should be able to write many challenging programs. 3. Advanced Programming Here we introduce a number of concepts that particularly support the development of program systems that need to react to ever changing sets of data. We present dynamic data structures as well as recur­ sion at the algorithmic and data-structure level. The reader also be­ comes familiar with persistent data and exception handling. Chapter 13 treats object-oriented programming, which has conquered an ever growing share of the field of software system development. Another steadily rising field, parallel programming, highlights Chapter 16. 4. Appendices Through the appendices we have striven to ease the task of Modula-3 programming. Appendix A describes a complete non-trivial program to manage music CD's. Appendix B, intended as a reference for the pros, offers a complete but very compact description of the semantics of Modula-3. It is a reprint of the original Modula-3 language defini­ tion [CDG+S9]. Further appendices describe the most important in­ terfaces to the Modula-3 development environment and provide con­ cise descriptions of various such environments. The appendices also include detailed instructions on installing and configuring a Modula-3 development environment and the software included with this book. 5. Included Software All examples in the book have been tested. They are either executable themselves or parts of executable programs. We provide these to the reader at no charge. All Modula-3 programs (including the Modula-3 compiler) can be started from an integrated, interactive, user-friendly environment. Acknowledgments Our foremost gratitude goes to Roland Mittermeir, who profoundly con­ tributed to the production of this book. Significant texts and examples in Chapters 10 to 12 come from him. He is actually a co-author of this book. We also owe special thanks to Hans-Peter Mossenbock, Peter Rechen­ berg, Johann Eder and Karl-Heinz Eder; they assumed the enormously Xl work-intensive and thankless task of thoroughly proofreading the origi­ nal German manuscript. We likewise wish to express our gratitude to Michael Dobrovnik for his comments on our example program in the ap­ pendix. Their criticisms and comments taught us a great deal, and without their contributions it would have been impossible to complete this book. Naturally the authors retain full and sole accountability for any errors. Our gratitude also goes to the researchers at Digital Systems Research Center, Palo Alto, who developed Modula-3 and made it available. We es­ pecially thank Marc Najork, for his support. We are also grateful to Greg Nelson and Bill Kalsow. We also extend our appreciation to Springer-Verlag, Digital Equipment Corporation, the University of Klagenfurt and the Raiffeisen Bank of Ca­ rinthia for their generous support of the development of our user-friendly Modula-3 environment and to Miklos Szabo for his development work. We also offer our sincere thanks to Silvia Nedizavec for her meticulous preparation of the figures in this book and to Michael Vrbicky for his help in formatting the English edition. Last but not least, we thank our patient families, who spent many evenings and weekends without us during the two years in which we wrote this book. We offer the reader this book as the fruits of our labors in the hope that it proves to be a useful learning instrument and that it provides some fun and pleasure along the way. Contents 1 What is programming? 1 1.1 An informal introduction. 1 1.1.1 Algorithms ..... 2 1.1.2 Switches and symbols 4 1.1.3 Turing machine ... 6 1.1.4 Computability .... 7 1.2 The von Neumann computer. 9 1.3 Rigid thought structures ... 11 1.4 Programming in the small . 14 1.4.1 Software production methods 14 1.4.2 Writing simple programs ... 17 1. 5 Levels of programming . 18 1.5.1 Formal and human languages. 18 1.5.2 Assembler ........... 20 1.5.3 High-level programming languages. 21 1.6 Programming and computer science .... 24 1.6.1 The responsibility of computer scientists 25 2 Metalanguages 27 2.1 Definition of formal languages . 27 2.2 Digits and numbers . 29 2.3 Names ............
Load more

Recommended publications
  • Methods for Fitting the Linear Ballistic Accumulator
    Behavior Research Methods 2009, 41 (4), 1095-1110 doi:10.3758/BRM.41.4.1095 Getting more from accuracy and response time data: Methods for fitting the linear ballistic accumulator CHRIS DONKIN , LEE A VERE ll , SC OTT BROWN , A N D A N D REW HE ATH C OTE University of Newcastle, Callaghan, New South Wales, Australia Cognitive models of the decision process provide greater insight into response time and accuracy than do stan- dard ANOVA techniques. However, such models can be mathematically and computationally difficult to apply. We provide instructions and computer code for three methods for estimating the parameters of the linear ballistic accumulator (LBA), a new and computationally tractable model of decisions between two or more choices. These methods—a Microsoft Excel worksheet, scripts for the statistical program R, and code for implementation of the LBA into the Bayesian sampling software WinBUGS—vary in their flexibility and user accessibility. We also provide scripts in R that produce a graphical summary of the data and model predictions. In a simulation study, we explored the effect of sample size on parameter recovery for each method. The materials discussed in this article may be downloaded as a supplement from http://brm.psychonomic-journals.org/content/supplemental. Many tasks used in experimental psychology involve edly samples information from the environment and that participants making relatively simple decisions, for which this information is used as evidence for one of the potential the experimenter measures the response times (RTs) and responses. As soon as the evidence in favor of one potential the accuracy of the responses.
    [Show full text]
  • Language-Level Support for Exploratory Programming of Distributed Virtual Environments
    In Proc ACM UIST ‘96 (Symp. on User Interface Software and Technology), Seattle, WA, November 6–8, 1996, pp. 83–94. Language-Level Support for Exploratory Programming of Distributed Virtual Environments Blair MacIntyre and Steven Feiner Department of Computer Science, Columbia University, New York, NY, 10027 {bm,feiner}@cs.columbia.edu http://www.cs.columbia.edu/~{bm,feiner} Abstract resulted in an unmanageable welter of client-server relation- ships, with each of a dozen or more processes needing to We describe COTERIE, a toolkit that provides language- create and maintain explicit connections to each other and to level support for building distributed virtual environments. handle inevitable crashes. COTERIE is based on the distributed data-object paradigm for distributed shared memory. Any data object in COTE- We spent a sufficiently large portion of our time reengineer- RIE can be declared to be a Shared Object that is replicated ing client-server code that it became clear to us that our fully in any process that is interested in it. These Shared implementation of the client-server model was unsuitable Objects support asynchronous data propagation with atomic for exploratory programming of distributed research proto- serializable updates, and asynchronous notification of types. The heart of the problem, as we saw it, was a lack of updates. COTERIE is built in Modula-3 and uses existing support for data sharing that was both efficient and easy for Modula-3 packages that support an integrated interpreted programmers to use in the face of frequent and unantici- language, multithreading, and 3D animation. Unlike other pated changes.
    [Show full text]
  • The Zonnon Project: a .NET Language and Compiler Experiment
    The Zonnon Project: A .NET Language and Compiler Experiment Jürg Gutknecht Vladimir Romanov Eugene Zueff Swiss Fed Inst of Technology Moscow State University Swiss Fed Inst of Technology (ETH) Computer Science Department (ETH) Zürich, Switzerland Moscow, Russia Zürich, Switzerland [email protected] [email protected] [email protected] ABSTRACT Zonnon is a new programming language that combines the style and the virtues of the Pascal family with a number of novel programming concepts and constructs. It covers a wide range of programming models from algorithms and data structures to interoperating active objects in a distributed system. In contrast to popular object-oriented languages, Zonnon propagates a symmetric compositional inheritance model. In this paper, we first give a brief overview of the language and then focus on the implementation of the compiler and builder on top of .NET, with a particular emphasis on the use of the MS Common Compiler Infrastructure (CCI). The Zonnon compiler is an interesting showcase for the .NET interoperability platform because it implements a non-trivial but still “natural” mapping from the language’s intrinsic object model to the underlying CLR. Keywords Oberon, Zonnon, Compiler, Common Compiler Infrastructure (CCI), Integration. 1. INTRODUCTION: THE BRIEF CCI and b) to experiment with evolutionary language HISTORY OF THE PROJECT concepts. The notion of active object was taken from the Active Oberon language [Gut01]. In addition, two This is a technical paper presenting and describing new concurrency mechanisms have been added: an the current state of the Zonnon project. Zonnon is an accompanying communication mechanism based on evolution of the Pascal, Modula, Oberon language syntax-oriented protocols , borrowed from the Active line [Wir88].
    [Show full text]
  • MODULA-2 TRANSLATOR USER's MANUAL First Edition May 1986
    LOGITECH SOFTWARE ENGINEERING LIBRARY PASCAL TO MODULA-2 TRANSLATOR USER'S MANUAL First Edition May 1986 Copyright (C) 1984, 1985, 1986, 1987 LOGITECH, Inc. All Rights Reserved. No part of this document may be copied or reproduced in any form or by any means without the prior written consent of LOGITECH, Inc. LOGITECH, MODULA-2186,and MODULA-2IVX86 are trademarks ofLOGITECH, Inc. Microsoft is a registered trademark of Microsoft Corporation. MS-DOS is a trademark of Microsoft Corporation. Intel is a registered trademark ofIntel Corporation. IBM is a registered trademark ofInternational Business Machines Corporation. Turbo Pascal is a registered trademark ofBorland International, Inc. LOGITECH, Inc. makes no warranties with respect to this documentation and disclaims any implied warranties of merchantability and fitness for a particular purpose. The information in this document is subject to change without notice. LOGITECH, Inc. assumes no responsibility for any errors that may appear in this document. From time to time changes may occur in the filenames and in the files actually included on the distribution disks. LOGITECH, Inc. makes no warranties that such files or facilities as mentioned in this documentation exist on the distribution disks or as part of the materials distributed. LU-GUllO-1 Initial issue: May 1986 Reprinted: September 1987 This edition applies to Release 1.00 or later of the software. ii TRANSLATOR Preface LOGITECH'S POLICIES AND SERVICES Congratulations on the purchase of your LOGITECH Pascal To Modula-2 Translator. Please refer to the following infonnation for details about LOGITECH's policies and services. We feel that effective communication with our customers is the key to quality service.
    [Show full text]
  • MODULA a Language for Modular Multiprogramming, Wirth, 1976
    Research Collection Report MODULA a language for modular multiprogramming Author(s): Wirth, Niklaus Publication Date: 1976 Permanent Link: https://doi.org/10.3929/ethz-a-000199440 Rights / License: In Copyright - Non-Commercial Use Permitted This page was generated automatically upon download from the ETH Zurich Research Collection. For more information please consult the Terms of use. ETH Library ~ idgenöss · ische ·Institut T echnisc ~he für. Hochschule Informatik Zürich MODULA: A language formodular multiprogramming ~~8rz 1976 18 ~ ., ' , „· Eidgenössische Institut Technische für Hochschule Informatik Zürich Niklaus Wirth MODULA: A language formodular multiprogramming - 1 - N .Wirth Abstract This paper defines a language called Modula, which is intended primarily for programming dedicated computer systems, including process control systems on smaller machines. The language is largely based on Pascal, but in addition to conventional block ) structure it introduces a so - called module structure . A module is a set of procedures, data types, and variables, where the programmer has precise control over the names that are imported from and exported to the environment. Modula includes general multiprocessing facilities, namely processes , interfacp, modules, and Signals . It also allows the specification of facilities that represent a computer ' s specific peripheral devices . Those given in this paper pertain to the PDP - 11. Author ' s address: Institut für Informatik , ETH , CH-8092 Zürich - 2 - Coaten ts 1. Introduction 3 2. 0 verview 5 3. Notation for syotactic description 10 4. Language vocabulary and representation 10 5. Facilities for sequential programmiog 12 1. Constant declarations 12 2. Type declarations 12 1 • Basic types 13 2. E n um e ratio n s 13 3.
    [Show full text]
  • Clouds and the Earth's Radiant Energy System (CERES) Data Management System
    NASA'S MISSION TO PLANET EARTH EARTH PROBES EOS DATA INFORMATION SYSTEM EARTH OBSERVING SYSTEM National Aeronautics and Space Administration Langley Research Center Hampton, Virginia 23681-2199 Clouds and the Earth's Radiant Energy System (CERES) Data Management System View HDF User's Guide S RA TH DIA AR N E T E E N H E T R D G N Y A CERES S S Y D S U T E O M L Version 5.0 C November 2007 NASA Clouds and the Earth's Radiant Energy System (CERES) Data Management System View_Hdf User’s Guide Version 5.0 Primary Author Kam-Pui Lee Science Systems and Applications, Inc. (SSAI) One Enterprise Parkway Hampton, Virginia 23666 November 2007 TABLE OF CONTENTS Section Page 1.0 Introduction . 1 2.0 Installation . 2 3.0 How to Start . 4 4.0 GUI Description . 12 4.1 Main Menu . 15 4.2 Select Function Menu . 68 4.3 Plot Window Menu . 92 5.0 Recognized Variable Names . 107 6.0 Configuration File . 111 7.0 Examples . 114 8.0 References . 132 9.0 List of Acronyms . 133 10.0 Data Center/Data Access Information . 134 iii LIST OF FIGURES Figure Page Fig. 3-1. Main Menu . 4 Fig. 3-2. File Menu . 5 Fig. 3-3. Select File Window . 5 Fig. 3-4. List SDS and Vdata Names . 6 Fig. 3-5. SDS Range Input Window . 7 Fig. 3-6. Import SDS . 7 Fig. 3-7. Vdata Fields Window . 8 Fig. 3-8. Vdata Field Range Window . 8 Fig. 3-9.
    [Show full text]
  • Extensibility in the Oberon System
    Nordic Journal of Computing 1(1994), 77{93. EXTENSIBILITY IN THE OBERON SYSTEM HANSPETER MOSSENB¨ OCK¨ ∗ Institute for Computer Systems ETH Zurich¨ CH{8092 Zurich¨ Switzerland Abstract. We show how an object-oriented system-and in particular the Oberon System-can be used to write software that is extensible by end users even while the software is running. Extensibility instead of completeness may be a way out of the unpleasant situation in software industry where applications still tend to become bigger every year. Oberon is both an object-oriented programming language and an operating system with new concepts such as commands and dynamic loading. The language and the system make up an environment that is similar to Smalltalk in its flexibility but offers static type-checking and is much more efficient. CR Classification: D.2.2, D.1.5 1. Introduction Ambitious software systems with large functionality and thousands of users can hardly be designed in a form that meets all future needs from the be- ginning. It is impossible to foresee all the ways in which such systems will be used so that requests for extensions will arise naturally. Current software industry tries to cope with this problem by including as many features as possible into a software system. This leads to huge monolithic software that offers amazing functionality but still leaves some users disappointed because it typically lacks just their favorite feature. The opposite approach is to design a system only as a minimal kernel and to provide means to extend it. This allows vendors and even users to add more functionality later without bothering other users which do not need it.
    [Show full text]
  • Warum Unix-Ports Pascal Bis Oberon in Der Bremer Informatik
    Warum Unix-Ports Pascal bis Oberon in der Bremer Informatik Günter Feldmann Universität Bremen [email protected] 1970th, Dept. of Electrical Engineering ● 1974/75: first university computer CII-Honeywell Bull, IRIS-80 ● first Pascal port from a university in Paris. ● learned Pascal by reading the compiler sources ● engineers needed 64-bit REALS, compiler got modified accordingly ● compiling and linking the compiler took 2 days ● N. Wirth: Systematisches Programmieren Since 1981, Dept. of Mathematics and Computer Science ● first personal computers: DEC PDT 11 ● PDP11 instruction set, but some instructions were missing, these had to be emulated in software as the interpreters and compilers used them. ● UCSD Pascal and some times a Modula (not Modula-2) compiler under RT11. ● Small local area network via V24 connections Computer Science ● A series of different computers ● DEC PDP11/44, BSD Unix ● DEC VAX 750 with 8 VT100 terminals, BSD Unix ● 30 Atari 520 ST (M6800) ● 20 Sun3 Workstations (M6820) ● all machines were equipped with Pascal and/or Modula-2 compilers ● Some machines (Pascal Microengine, PERQ) were microprogrammed for Pascal (p-code, Q- code) Computer Science ● workstation pool for students ● 30 machines (1986), 100 machines today ● in the beginning of 1990th we acquired Sun4 workstations (SPARC). No Modula-2 compiler! ● ETHZ released the SPARC Oberon system hosted by SunOS. This system was used in the course “Software Projekt” until 1996. Then “Java” came … ● programming courses got replaced by courses in “internet programming” Keeping Oberon alive on our hardware ● OS change: SunOS (BSD) to Solaris (SYSVR4) ● despite binary compatibility SPARC Oberon failed. Oberon compiler used registers reserved for usage by the system.
    [Show full text]
  • Towards Mathix / Math-X, a Computer Algebra Language That Can Create Its Own Operating System, and That Is Amazingly User- Friendly and Secure
    Towards Mathix / Math-x, a computer algebra language that can create its own operating system, and that is amazingly user- friendly and secure Thomas Colignatus, August 19 2009, some clarifications August 23 2009 http://www.dataweb.nl/~cool Summary Given the current supply and demand for computer languages and systems, there is a clear window of opportunity for the software community to collaborate and create Mathix and Math-x. The base would be Oberon, which itself derives from Algol / Pascal / Modula and which is better designed than Unix / Linux, and which now has the system Bluebottle / A2 at http://bluebottle.ethz.ch. Mathix is defined as Oberon/A2 extended with a suitable computer algebra language (say, CAL). Math-x is defined as Minix ported to Oberon/A2 (via Cyclone) and extended with that CAL. Mathix and Math-x thus can create their own OS. Mathix and Math-x are flexible in that they contain both a strongly typed dialect relevant for OS creation (current Oberon) and a more flexible dialect relevant for the human user (CAL, to be created). The dialects have much syntax in common but the CAL allows more flexibility. The CAL is internally translated into Oberon/A2 which allows compilation as well. 2 2009-08-23-Math-x.nb Note This paper is best understood in the context of my book Elegance with Substance on mathematics education - see http://www.dataweb.nl/~cool/Papers/Math/Index.html. My book advises that each national parliament investigates the stagnation in doing mathematics on the computer in school. This paper suggests how the software community might anticipate on common sense conclusions and start working on improvement.
    [Show full text]
  • Report on the Programming Language Modula-2
    The Programming language Modula-2 133 Report on the Programming Language Modula-2 1. Introduction Modula-2 grew out of a practical need for a general, efficiently implementable systems programming language for minicomputers. Its ancestors are Pascal and Modula. From the latter It has inherited the name, the important module concept, and a systematic, modern syntax, from Pascal most of the rest. This includes in particular the data structures, I.e. arrays, records, variant records, sets, and pointers. Structured statements include the familiar if, case, repeat, while, for, and with statements. Their syntax is such that every structure ends with an explicit termination symbol. The language is essentially machine-independent, with the exception of limitations due to word size. This appears to be in contradiction to the notion of a system-programming language, in which it must be possible to express all operations inherent in the underlying computer. The dilemma is resolved with the aid of the module concept. Machine-dependent items can be introduced in specific modules, and their use can thereby effectively be confined and isolated. In particular, the language provides the possibility to relax rules about data type compatibility in these cases. In a capable system-programming language it is possible to express input/output conversion procedures, file handling routines, storage allocators, process schedulers etc. Such facilities must therefore not be included as elements of the language itself, but appear as (so-called low-level) modules which are components of most programs written. Such a collection of standard modules is therefore an essential part of a Modula-2 implementation.
    [Show full text]
  • An Extensible Programrning Environment for Modula-3%
    An Extensible Programrning Environment for Modula-3% Mick Jordan’ Abstract 2 Goals This paper describes the design and implementation of The long term objective was to build a practical envi- a practical programming environment for the Modula-3 ronment to support large scale software development in programming language. The environment is organised Modula-3. Initially, the environment would contain only a around an extensible intermediate representation of pro- basic set of well integrated tools such as a compiler, linker grams and makes extensive use of reusable components. and debugger, but would be capable of supporting real The environment is implemented in Modula-3 and exploits projects on a variety of systems. In the longer term ad- some of the novel features of the language. ditional tools such as code browsers, code analysers, and improvements like smart recompilation would be added, building on the basic environment. In this paper, we 1 Introduction are more concerned with how tools are constructed and combined than with the exact details of their functionality The successof a programming language owes much to its or interface to users of the environment. The idea is that, associatedprogramming environment, especially to the set of tools which enable the construction and modification of if the construction of new tools is made easy enough, programs. W5th a new language there is trade-off between new and powerful tools will appear routinely. Important producing an implementation quickly and in providing a sub-goals for the environment were as follows: rich and powerful set of tools. Choosing the first approach typically results in low quality, poorly integrated tools.
    [Show full text]
  • Project Oberon the Design of an Operating System and Compiler
    1 Niklaus Wirth Jürg Gutknecht Project Oberon The Design of an Operating System and Compiler Edition 2005 2 Project Oberon Preface This book presents the results of Project Oberon, namely an entire software environment for a modern workstation. The project was undertaken by the authors in the years 1986-89, and its primary goal was to design and implement an entire system from scratch, and to structure it in such a way that it can be described, explained, and understood as a whole. In order to become confronted with all aspects, problems, design decisions and details, the authors not only conceived but also programmed the entire system described in this book, and more. Although there exist numerous books explaining principles and structures of operating systems, there is a lack of descriptions of systems actually implemented and used. We wished not only to give advice on how a system might be built, but to demonstrate how one was built. Program listings therefore play a key role in this text, because they alone contain the ultimate explanations. The choice of a suitable formalism therefore assumed great importance, and we designed the language Oberon as not only an effective vehicle for implementation, but also as a publication medium for algorithms in the spirit in which Algol 60 had been created three decades ago. Because of its structure, the language Oberon is equally well suited to exhibit global, modular structures of programmed systems. In spite of the small number of man-years spent on realizing the Oberon System, and in spite of its compactness letting its description fit a single book, it is not an academic toy, but rather a versatile workstation system that has found many satisfied and even enthusiastic users in academia and industry.
    [Show full text]