DOCSLIB.ORG

Notes on Subroutines

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Notes on Subroutines Course Notes 1.2 Fall 2001 94.201 Page 1 of 9 Notes on Subroutines Programs are often required to perform the same operation many times. For example, applications involving integers are often required to display integer values. The code fragment that performs an operation must be executed each time the operation is to be performed. One way to achieve this would be to duplicate the code fragment at each point it is needed. This could work, but might make the program very large. A better solution might be to load one copy of the code fragment into memory as a subroutine, and to provide instructions that allow a program to invoke (i.e. transfer control to) the subroutine whenever the operation is to be performed. At first glance, a simple JMP to the subroutine might seem appropriate; however, the JMP instruction does not include any mechanism to allow control to be returned to the point in the program from which the subroutine was invoked. Subroutines are such a widely used programming concept, that processors include special instructions to support the implementation of subroutines. The p86 processor includes the CALL (invoke) and RET (return) instructions to support subroutines. The execution of the instructions relies on the presence of a stack to hold the return address while the subroutine is executing. Programs wishing to use subroutines must be sure that a stack has been set up using the SP register. The CALL instruction is similar to the JMP instruction, except that the address of the instruction that follows the CALL instruction is pushed onto the stack as part of the CALL execution. The value that is pushed onto the stack is referred to as the return address. This is not difficult to implement, since the address of the next sequential instruction (i.e. the return address) is present in the IP register immediately after fetching the CALL instruction. The CALL instruction uses relative addressing (as does the JMP instruction). The execution of the CALL instruction can be summarized as: PUSH IP JMP target where: target is the relative offset from the instruction after the CALL to the first instruction of the subroutine. The RET instruction returns execution control to the instruction immediately after the CALL instruction that invoked the subroutine. This is accomplished by popping the return address off of the stack and into the IP register. After executing the RET instruction, the next instruction to be executed will be fetched from the return address. The RET instruction will only succeed in accomplishing this objective if the return address is the value on the top of the stack at the time the RET is executed. Subroutines must be careful to ensure that this condition is satisfied! Copyright ã Trevor W. Pearce, October 11, 2000 For use in the 94.201 course only – not for distribution outside of the Department of Systems and Computer Engineering, Carleton University, Ottawa, Canada Course Notes 1.2 Fall 2001 94.201 Page 2 of 9 There are many details associated with subroutines and parameter passing, and there may be several possible ways to deal with the details. By following programming POLICY, the details are handled consistently, which results in programs that are easier to construct, understand and modify. Parameters Parameters allow information to be communicated between the caller (i.e. the code that is invoking the subroutine) and the callee (i.e. the subroutine). Parameters allow subroutines to implement a wider range of operations, which typically results in fewer subroutines being needed in a program. Furthermore, subroutines that have been generalized are often more easily re-used in other applications. For example, a DISPLAY subroutine might be written to display 16-bit integer values in signed ASCII-decimal form. A C++ prototype for the subroutine would be written: void DISPLAY ( int X ) The intention of the subroutine is to display the supplied integer value (represented by the parameter X). An invocation of the subroutine must supply a value for X. When referring to the general description of the subroutine, X is a parameter. When considering a specific invocation of the subroutine, the particular value supplied for X is referred to as the argument. Subroutines are based on assumptions about the purpose of the subroutine. For example, the DISPLAY subroutine described above assumes that the value is to be displayed in signed decimal form. The subroutine might be further generalized by adding an additional parameter that is used to specify the display form. For example, suppose that the prototype for the DISPLAY function was augmented to become: void DISPLAY ( word X, int format ) where: format is an integer value used to represent how the value should be displayed format = 0: signed decimal format = 1: unsigned decimal format = 2: hexadecimal format = 3: binary The augmented DISPLAY function is a further generalization of the previous DISPLAY function. Signed decimal format can still be displayed by passing the format value = 0; but the augment function also handles 3 additional display formats. There are several ways in which parameter information can be communicated (i.e. passed) from the caller to the subroutine: Copyright ã Trevor W. Pearce, October 11, 2000 For use in the 94.201 course only – not for distribution outside of the Department of Systems and Computer Engineering, Carleton University, Ottawa, Canada Course Notes 1.2 Fall 2001 94.201 Page 3 of 9 Global Variables: A global variable is one that is shared by both the caller and the subroutine. The caller communicates information to the subroutine by writing a value into the shared variable before calling the subroutine. The subroutine obtains the information by reading the variable. The variable is referred to as being "global" because the variable's static name (i.e. address) is known both to the caller and the subroutine. The use of global variables is not (generally) considered to be good programming practice; however, we will see in the 94.203 course that there are important cases where global variables are the only practical mechanism for communicating between program components. Registers: Registers may be used to pass information. The caller places arguments in relevant registers before calling the subroutine, and the subroutine assumes that the relevant registers contain arguments. There are two limitations to this approach: First, there are a limited number of registers, and this in turn limits the number of parameters that may be passed via this mechanism. Second, assembly-level programming involves the use of the registers to accomplish program objectives, and therefore, parameters passed in registers must often be saved to memory (perhaps the stack?) to allow the registers to be used by the subroutine. Stack: Parameters may be passed on the stack. The caller must push arguments onto the stack prior to calling the subroutine, and the subroutine must retrieve the arguments from the stack. In this course, we will use the following POLICY: parameters will be passed on the stack. (Passing parameters on the stack is discussed in much more detail below!) In addition to the issue of the physical location (global, register, stack) used to pass parameters, there is also the issue of whether each parameter is passed by value or by reference. When passing by value, a copy of the relevant information is passed. When passing by reference, a reference to a variable containing the relevant information is passed. Passing parameters by reference is often implemented by passing the address of the variable. Whether a parameter is passed by value or reference can be specified in the prototype used to describe the subroutine. As a POLICY in this course, let's assume that the default is to pass by value, and that reference parameters will be prefixed with "&". For example, consider the prototype: void SQUARE( int X, int & XSquared ) The purpose of the SQUARE subroutine is to calculate X*X, and to return the result in the variable XSquared. The parameter X is passed by value, and the parameter XSquared is passed by reference. When setting up to call the subroutine, the caller must supply an integer value as the X argument, and a reference to (i.e. the address of) an integer variable as the XSquared argument. Copyright ã Trevor W. Pearce, October 11, 2000 For use in the 94.201 course only – not for distribution outside of the Department of Systems and Computer Engineering, Carleton University, Ottawa, Canada Course Notes 1.2 Fall 2001 94.201 Page 4 of 9 Parameter Passing on the Stack When passing parameters on the stack, the caller must push the relevant arguments before calling the subroutine. An immediate question that arises is the order in which the parameters are pushed onto the stack. In this course, we will use the following POLICY: each subroutine will be documented by (at least) a C++-like prototype of the subroutine, and the parameters will be pushed onto the stack in right-to-left order of appearance in the prototype. For example, recall the prototype: void SQUARE( int X, int & XSquared ) The XSquared parameter is the rightmost, and the X parameter is the leftmost (as they appear in the prototype); therefore, when calling the SQUARE subroutine, the XSquared argument would be pushed onto the stack before pushing the X argument. Following a call to a subroutine, the stack has the following configuration: SP return address arguments A simple way for the subroutine to access the arguments would be to use register indirect addressing based on the SP value; however, the SP register is not one of the registers permitted for this addressing mode (recall that only BX, BP, SI and DI are permitted).
Load more

Recommended publications
  • Writing Fast Fortran Routines for Python
    Writing fast Fortran routines for Python Table of contents Table of contents ............................................................................................................................ 1 Overview ......................................................................................................................................... 2 Installation ...................................................................................................................................... 2 Basic Fortran programming ............................................................................................................ 3 A Fortran case study ....................................................................................................................... 8 Maximizing computational efficiency in Fortran code ................................................................. 12 Multiple functions in each Fortran file ......................................................................................... 14 Compiling and debugging ............................................................................................................ 15 Preparing code for f2py ................................................................................................................ 16 Running f2py ................................................................................................................................. 17 Help with f2py ..............................................................................................................................
    [Show full text]
  • Scope in Fortran 90
    Scope in Fortran 90 The scope of objects (variables, named constants, subprograms) within a program is the portion of the program in which the object is visible (can be use and, if it is a variable, modified). It is important to understand the scope of objects not only so that we know where to define an object we wish to use, but also what portion of a program unit is effected when, for example, a variable is changed, and, what errors might occur when using identifiers declared in other program sections. Objects declared in a program unit (a main program section, module, or external subprogram) are visible throughout that program unit, including any internal subprograms it hosts. Such objects are said to be global. Objects are not visible between program units. This is illustrated in Figure 1. Figure 1: The figure shows three program units. Main program unit Main is a host to the internal function F1. The module program unit Mod is a host to internal function F2. The external subroutine Sub hosts internal function F3. Objects declared inside a program unit are global; they are visible anywhere in the program unit including in any internal subprograms that it hosts. Objects in one program unit are not visible in another program unit, for example variable X and function F3 are not visible to the module program unit Mod. Objects in the module Mod can be imported to the main program section via the USE statement, see later in this section. Data declared in an internal subprogram is only visible to that subprogram; i.e.
    [Show full text]
  • Subroutines – Get Efficient
    Subroutines – get efficient So far: The code we have looked at so far has been sequential: Subroutines – getting efficient with Perl do this; do that; now do something; finish; Problem Bela Tiwari You need something to be done over and over, perhaps slightly [email protected] differently depending on the context Solution Environmental Genomics Thematic Programme Put the code in a subroutine and call the subroutine whenever needed. Data Centre http://envgen.nox.ac.uk Syntax: There are a number of correct ways you can define and use Subroutines – get efficient subroutines. One is: A subroutine is a named block of code that can be executed as many times #!/usr/bin/perl as you wish. some code here; some more here; An artificial example: lalala(); #declare and call the subroutine Instead of: a bit more code here; print “Hello everyone!”; exit(); #explicitly exit the program ############ You could use: sub lalala { #define the subroutine sub hello_sub { print "Hello everyone!\n“; } #subroutine definition code to define what lalala does; #code defining the functionality of lalala more defining lalala; &hello_sub; #call the subroutine return(); #end of subroutine – return to the program } Syntax: Outline review of previous slide: Subroutines – get efficient Syntax: #!/usr/bin/perl Permutations on the theme: lalala(); #call the subroutine Defining the whole subroutine within the script when it is first needed: sub hello_sub {print “Hello everyone\n”;} ########### sub lalala { #define the subroutine The use of an ampersand to call the subroutine: &hello_sub; return(); #end of subroutine – return to the program } Note: There are subtle differences in the syntax allowed and required by Perl depending on how you declare/define/call your subroutines.
    [Show full text]
  • COBOL-Skills, Where Art Thou?
    DEGREE PROJECT IN COMPUTER ENGINEERING 180 CREDITS, BASIC LEVEL STOCKHOLM, SWEDEN 2016 COBOL-skills, Where art Thou? An assessment of future COBOL needs at Handelsbanken Samy Khatib KTH ROYAL INSTITUTE OF TECHNOLOGY i INFORMATION AND COMMUNICATION TECHNOLOGY Abstract The impending mass retirement of baby-boomer COBOL developers, has companies that wish to maintain their COBOL systems fearing a skill shortage. Due to the dominance of COBOL within the financial sector, COBOL will be continually developed over at least the coming decade. This thesis consists of two parts. The first part consists of a literature study of COBOL; both as a programming language and the skills required as a COBOL developer. Interviews were conducted with key Handelsbanken staff, regarding the current state of COBOL and the future of COBOL in Handelsbanken. The second part consists of a quantitative forecast of future COBOL workforce state in Handelsbanken. The forecast uses data that was gathered by sending out a questionnaire to all COBOL staff. The continued lack of COBOL developers entering the labor market may create a skill-shortage. It is crucial to gather the knowledge of the skilled developers before they retire, as changes in old COBOL systems may have gone undocumented, making it very hard for new developers to understand how the systems work without guidance. To mitigate the skill shortage and enable modernization, an extraction of the business knowledge from the systems should be done. Doing this before the current COBOL workforce retires will ease the understanding of the extracted data. The forecasts of Handelsbanken’s COBOL workforce are based on developer experience and hiring, averaged over the last five years.
    [Show full text]
  • Subroutines and Control Abstraction
    Subroutines and Control Abstraction CSE 307 – Principles of Programming Languages Stony Brook University http://www.cs.stonybrook.edu/~cse307 1 Subroutines Why use subroutines? Give a name to a task. We no longer care how the task is done. The subroutine call is an expression Subroutines take arguments (in the formal parameters) Values are placed into variables (actual parameters/arguments), and A value is (usually) returned 2 (c) Paul Fodor (CS Stony Brook) and Elsevier Review Of Memory Layout Allocation strategies: Static Code Globals Explicit constants (including strings, sets, other aggregates) Small scalars may be stored in the instructions themselves Stack parameters local variables temporaries bookkeeping information Heap 3 dynamic allocation(c) Paul Fodor (CS Stony Brook) and Elsevier Review Of Stack Layout 4 (c) Paul Fodor (CS Stony Brook) and Elsevier Review Of Stack Layout Contents of a stack frame: bookkeeping return Program Counter saved registers line number static link arguments and returns local variables temporaries 5 (c) Paul Fodor (CS Stony Brook) and Elsevier Calling Sequences Maintenance of stack is responsibility of calling sequence and subroutines prolog and epilog Tasks that must be accomplished on the way into a subroutine include passing parameters, saving the return address, changing the program counter, changing the stack pointer to allocate space, saving registers (including the frame pointer) that contain important values and that may be overwritten by the callee, changing the frame pointer to refer to the new frame, and executing initialization code for any objects in the new frame that require it. Tasks that must be accomplished on the way out include passing return parameters or function values, executing finalization code for any local objects that require it, deallocating the stack frame (restoring the stack pointer), restoring other saved registers (including the frame pointer), and restoring the program counter.
    [Show full text]
  • A Subroutine's Stack Frames Differently • May Require That the Steps Involved in Calling a Subroutine Be Performed in Different Orders
    Chapter 04: Instruction Sets and the Processor organizations Lesson 14 Use of the Stack Frames Schaum’s Outline of Theory and Problems of Computer Architecture 1 Copyright © The McGraw-Hill Companies Inc. Indian Special Edition 2009 Objective • To understand call and return, nested calls and use of stack frames Schaum’s Outline of Theory and Problems of Computer Architecture 2 Copyright © The McGraw-Hill Companies Inc. Indian Special Edition 2009 Calling a subroutine Schaum’s Outline of Theory and Problems of Computer Architecture 3 Copyright © The McGraw-Hill Companies Inc. Indian Special Edition 2009 Calls to the subroutines • Allow commonly used functions to be written once and used whenever they are needed, and provide abstraction, making it easier for multiple programmers to collaborate on a program • Important part of virtually all computer languages • Function calls in a C language program • Also included additional functions from library by including the header files Schaum’s Outline of Theory and Problems of Computer Architecture 4 Copyright © The McGraw-Hill Companies Inc. Indian Special Edition 2009 Difficulties when Calling a subroutine Schaum’s Outline of Theory and Problems of Computer Architecture 5 Copyright © The McGraw-Hill Companies Inc. Indian Special Edition 2009 Difficulties involved in implementing subroutine calls 1. Programs need a way to pass inputs to subroutines that they call and to receive outputs back from them Schaum’s Outline of Theory and Problems of Computer Architecture 6 Copyright © The McGraw-Hill Companies Inc. Indian Special Edition 2009 Difficulties involved in implementing subroutine calls 2. Subroutines need to be able to allocate space in memory for local variables without overwriting any data used by the subroutine-calling program Schaum’s Outline of Theory and Problems of Computer Architecture 7 Copyright © The McGraw-Hill Companies Inc.
    [Show full text]
  • Chapter 9: Functions and Subroutines – Reusing Code. Page 125 Chapter 9: Functions and Subroutines – Reusing Code
    Chapter 9: Functions and Subroutines – Reusing Code. Page 125 Chapter 9: Functions and Subroutines – Reusing Code. This chapter introduces the use of Functions and Subroutines. Programmers create subroutines and functions to test small parts of a program, reuse these parts where they are needed, extend the programming language, and simplify programs. Functions: A function is a small program within your larger program that does something for you. You may send zero or more values to a function and the function will return one value. You are already familiar with several built in functions like: rand and rgb. Now we will create our own. Illustration 22: Block Diagram of a Function © 2014 James M. Reneau (CC BY-NC-SA 3.0 US) Chapter 9: Functions and Subroutines – Reusing Code. Page 126 Function functionname( argument(s) ) statements End Function Function functionname$( argument(s) ) statements End Function The Function statement creates a new named block of programming statements and assigns a unique name to that block of code. It is recommended that you do not name your function the same name as a variable in your program, as it may cause confusion later. In the required parenthesis you may also define a list of variables that will receive values from the “calling” part of the program. These variables belong to the function and are not available to the part of the program that calls the function. A function definition must be closed or finished with an End Function. This tells the computer that we are done defining the function. The value being returned by the function may be set in one of two ways: 1) by using the return statement with a value following it or 2) by setting the function name to a value within the function.
    [Show full text]
  • Object Oriented Programming*
    SLAC-PUB-5629 August 1991 ESTABLISHED 1962 (T/E/I) Object Oriented Programming* Paul F. Kunz Stanford Linear Accelerator Center Stanford University Stanford, California 94309, USA ABSTRACT This paper is an introduction to object oriented programming. The object oriented approach is very pow- erful and not inherently difficult, but most programmers find a relatively high threshold in learning it. Thus, this paper will attempt to convey the concepts with examples rather than explain the formal theory. 1.0 Introduction program is a collection of interacting objects that commu- nicate with each other via messaging. To the FORTRAN In this paper, the object oriented programming tech- programmer, a message is like a CALL to a subroutine. In niques will be explored. We will try to understand what it object oriented programming, the message tells an object really is and how it works. Analogies will be made with tra- what operation should be performed on its data. The word ditional programming in an attempt to separate the basic method is used for the name of the operation to be carried concepts from the details of learning a new programming out. The last key idea is that of inheritance. This idea can language. Most experienced programmers find there is a not be explained until the other ideas are better understood, relatively high threshold in learning the object oriented thus it will be treated later on in this paper. techniques. There are a lot of new words for which one An object is executable code with local data. This data needs to know the meaning in the context of a program; is called instance variables.
    [Show full text]
  • 5. Subroutines
    IA010: Principles of Programming Languages 5. Subroutines Jan Obdržálek obdrzalek@fi.muni.cz Faculty of Informatics, Masaryk University, Brno IA010 5. Subroutines 1 Subroutines Subprograms, functions, procedures, . • principal mechanism for control abstraction • details of subroutine’s computation are replaced by a statement that calls the subroutine • increases readability: emphasizes logical structure, while hiding the low-level details • facilitate code reuse, saving • memory • coding time • subroutines vs OOP methods: • differ in the way they are called • methods are associated with classes and objects IA010 5. Subroutines 2 Outline Fundamentals of subroutines Parameter-passing methods Overloaded and generic subroutines Functions – specifics Coroutines IA010 5. Subroutines 3 Fundamentals of subroutines IA010 5. Subroutines 4 Subroutine characteristics • each subroutine has a single entry point • the calling program unit is suspended during subroutine execution (so only one subroutine is in execution at any given time) • control returns to the caller once subroutine execution is terminated • alternatives: • coroutines • concurrent units IA010 5. Subroutines 5 Basic definitions • subroutine definition – describes the interface and actions • subroutine call – an explicit request for the subroutine to be executed • active subroutine – has been executed, but has not yet completed its execution • subroutine header – part of the definition, specifies: • the kind of the subroutine (function/procedure) • a name (if not anonymous) • a list of parameters • parameter profile – the number, order and types of formal parameters • protocol – parameter profile + return type IA010 5. Subroutines 6 Procedures and functions procedures • do not return values • in effect define new statements • as functions: can return a value using • global variables • two-way communication through parameters functions • return values • function call is, in effect, replaced by the return value • as procedures: e.g.
    [Show full text]
  • Object Oriented Programming Via Fortran 90 (Preprint: Engineering Computations, V
    Object Oriented Programming via Fortran 90 (Preprint: Engineering Computations, v. 16, n. 1, pp. 26-48, 1999) J. E. Akin Rice University, MEMS Dept. Houston, TX 77005-1892 Keywords object-oriented, encapsulation, inheritance, polymorphism, Fortran 90 Abstract There is a widely available object-oriented (OO) programming language that is usually overlooked in the OO Analysis, OO Design, OO Programming literature. It was designed with most of the features of languages like C++, Eiffel, and Smalltalk. It has extensive and efficient numerical abilities including concise array and matrix handling, like Matlab®. In addition, it is readily extended to massively parallel machines and is backed by an international ISO and ANSI standard. The language is Fortran 90 (and Fortran 95). When the explosion of books and articles on OOP began appearing in the early 1990's many of them correctly disparaged Fortran 77 (F77) for its lack of object oriented abilities and data structures. However, then and now many authors fail to realize that the then new Fortran 90 (F90) standard established a well planned object oriented programming language while maintaining a full backward compatibility with the old F77 standard. F90 offers strong typing, encapsulation, inheritance, multiple inheritance, polymorphism, and other features important to object oriented programming. This paper will illustrate several of these features that are important to engineering computation using OOP. 1. Introduction The use of Object Oriented (OO) design and Object Oriented Programming (OOP) is becoming increasingly popular (Coad, 1991; Filho, 1991; Rumbaugh, 1991), and today there are more than 100 OO languages. Thus, it is useful to have an introductory understanding of OOP and some of the programming features of OO languages.
    [Show full text]
  • Introduction to MARIE, a Basic CPU Simulator
    Introduction to MARIE, A Basic CPU Simulator 2nd Edition Jason Nyugen, Saurabh Joshi, Eric Jiang THE MARIE.JS TEAM (HTTPS://GITHUB.COM/MARIE-JS/) Introduction to MARIE, A Basic CPU Simulator Copyright © 2016 Second Edition Updated August 2016 First Edition – July 2016 By Jason Nyugen, Saurabh Joshi and Eric Jiang This document is licensed under the MIT License To contribute to our project visit: https//www.github.com/MARIE-js/MARIE.js/ The MIT License (MIT) Copyright (c) 2016 Jason Nguyen, Saurabh Joshi, Eric Jiang Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. Please reference this document at https://marie-js.github.io/MARIE.js/book.pdf for Student Integrity Policies for more information please visit your university’s Student Integrity Policy.
    [Show full text]
  • LISP 1.5 Programmer's Manual
    LISP 1.5 Programmer's Manual The Computation Center and Research Laboratory of Eleotronics Massachusetts Institute of Technology John McCarthy Paul W. Abrahams Daniel J. Edwards Timothy P. Hart The M. I.T. Press Massrchusetts Institute of Toohnology Cambridge, Massrchusetts The Research Laboratory af Electronics is an interdepartmental laboratory in which faculty members and graduate students from numerous academic departments conduct research. The research reported in this document was made possible in part by support extended the Massachusetts Institute of Technology, Re- search Laboratory of Electronics, jointly by the U.S. Army, the U.S. Navy (Office of Naval Research), and the U.S. Air Force (Office of Scientific Research) under Contract DA36-039-sc-78108, Department of the Army Task 3-99-25-001-08; and in part by Con- tract DA-SIG-36-039-61-G14; additional support was received from the National Science Foundation (Grant G-16526) and the National Institutes of Health (Grant MH-04737-02). Reproduction in whole or in part is permitted for any purpose of the United States Government. SECOND EDITION Elfteenth printing, 1985 ISBN 0 262 130 11 4 (paperback) PREFACE The over-all design of the LISP Programming System is the work of John McCarthy and is based on his paper NRecursiveFunctions of Symbolic Expressions and Their Com- putation by Machinett which was published in Communications of the ACM, April 1960. This manual was written by Michael I. Levin. The interpreter was programmed by Stephen B. Russell and Daniel J. Edwards. The print and read programs were written by John McCarthy, Klim Maling, Daniel J.
    [Show full text]