mu - Soul of a tiny new machine. More thorough tests → More comprehensible and rewrite-friendly software → More resilient society.

	Commit message (Expand)	Author	Age	Files	Lines
*	3862	Kartik K. Agaram	2017-05-19	1	-4/+4
*	3860 - stop buffering the screen in termbox	Kartik K. Agaram	2017-05-18	1	-23/+4
*	3858	Kartik K. Agaram	2017-05-13	1	-5/+1
*	3857	Kartik K. Agaram	2017-05-13	1	-3/+0
*	3854	Kartik K. Agaram	2017-05-13	1	-5/+31
*	3842	Kartik K. Agaram	2017-05-04	1	-3/+0
*	3824 - experiment: stop buffering in termbox	Kartik K. Agaram	2017-04-16	1	-28/+5
*	3711	Kartik K. Agaram	2016-12-26	1	-4/+0
*	2572	Kartik K. Agaram	2016-01-19	1	-1/+1
*	2181 - detect shift-tab	Kartik K. Agaram	2015-09-11	1	-5/+4
*	2132 - support for ctrl + arrow keys	Kartik K. Agaram	2015-09-02	1	-2/+6
*	2113 - stop updating entire screen on tb_present()	Kartik K. Agaram	2015-08-29	1	-0/+3
*	1964 - don't mess up paste	Kartik K. Agaram	2015-08-09	1	-0/+2
*	1731 - ah, now fully responsive	Kartik K. Agaram	2015-07-08	1	-0/+2
*	1573	Kartik K. Agaram	2015-06-16	1	-0/+1
*	1530 - switch to termbox's 256-color mode	Kartik K. Agaram	2015-06-05	1	-12/+5
*	1486 - repl: hitting enter now working	Kartik K. Agaram	2015-05-27	1	-0/+2
*	1368 - alias carriage-return and newline	Kartik K. Agaram	2015-05-14	1	-0/+3
*	1314	Kartik K. Agaram	2015-05-09	1	-1/+2
*	1276 - make C++ version the default	Kartik K. Agaram	2015-05-05	1	-0/+210

<HTML> <HEAD> <TITLE>Simply Scheme: Glossary</TITLE> </HEAD> <BODY> <CITE>Simply Scheme</CITE>: <CITE>Introducing Computer Science</CITE> 2/e Copyright (C) 1999 MIT <H1>Glossary</H1> <TABLE width="100%"><TR><TD> <IMG SRC="../simply.jpg" ALT="cover photo"> <TD><TABLE> <TR><TD align="right"><CITE><A HREF="http://www.cs.berkeley.edu/~bh/">Brian Harvey</A> University of California, Berkeley</CITE> <TR><TD align="right"><CITE><A HREF="http://ccrma.stanford.edu/~matt">Matthew Wright</A> University of California, Santa Barbara</CITE> <TR><TD align="right"> <TR><TD align="right"><A HREF="../pdf/ssch27.pdf">Download PDF version</A> <TR><TD align="right"><A HREF="../ss-toc2.html">Back to Table of Contents</A> <TR><TD align="right"><A HREF="appendix-funlist.html">BACK</A> chapter thread <A HREF="appuindex.html">NEXT</A> <TR><TD align="right"><A HREF="http://mitpress.mit.edu/0262082810">MIT Press web page for <CITE>Simply Scheme</CITE></A> </TABLE></TABLE> <HR> ADT:    See abstract data type. a-list:    Synonym for association list. abstract data type:    A type that isn't provided automatically by Scheme, but that the programmer invents. In order to create an abstract data type, a programmer must define selectors and constructors for that type, and possibly also mutators. abstraction:    An approach to complex problems in which the solution is built in layers. The structures needed to solve the problem (algorithms and data structures) are implemented using lower-level capabilities and given names that can then be used as if they were primitive facilities. actual argument expression:    An expression that produces an actual argument value. In <CODE>(+ 2 (* 3 5))</CODE>, the subexpression <CODE>(* 3 5)</CODE> is an actual argument expression, since it provides an argument for the invocation of <CODE>+</CODE>. actual argument value:    A value used as an argument to a procedure. For example, in the expression <CODE>(+ 2 (* 3 5))</CODE>, the number <CODE>15</CODE> is an actual argument value. aggregate:    An object that consists of a number of other objects. For example, a sentence is an aggregate whose elements are words. Lists and vectors are also aggregates. A word can be thought of, for some purposes, as an aggregate whose elements are one-letter words. algorithm:    A method for solving a problem. A computer program is the expression of an algorithm in a particular programming language; the same algorithm might also be expressed in a different language. apply:    To invoke a procedure with arguments. For example, "Apply the procedure <CODE>+</CODE> to the arguments <CODE>3</CODE> and <CODE>4</CODE>." argument:    A datum provided to a procedure. For example, in <CODE>(square 13)</CODE>, <CODE>13</CODE> is the argument to <CODE>square</CODE>. association list:    A list in which each element contains a name and a corresponding value. The list is used to look up a value, given a name. atomic expression:    An expression that isn't composed of smaller pieces. backtracking:    A programming technique in which the program tries one possible solution to a problem, but tries a different solution if the first isn't successful. base case:    In a recursive procedure, the part that solves the smallest possible version of the problem without needing a recursive invocation. body:    An expression, part of the definition of a procedure, that is evaluated when that procedure is invoked. For example, in <PRE>(define (square x) (* x x)) </PRE> the expression <CODE>(* x x)</CODE> is the body of the <CODE>square</CODE> procedure. Boolean:    The value <CODE>#t</CODE>, meaning "true," or <CODE>#f</CODE>, meaning "false." branch node:    A tree node with children. The opposite of a leaf node. bug:    An error in a program. This word did not originate with Grace Hopper finding an actual insect inside a malfunctioning computer; she may have done so, but the terminology predates computers by centuries. call:    Synonym for invoke. cell:    One location in a spreadsheet. children:    The nodes directly under this one, in a tree. (See also siblings and parent.) composition of functions:    Using the value returned by a function as an argument to another. In the expression <CODE>(+ 2 (* 3 5))</CODE>, the value returned by the <CODE>*</CODE> function is used as an argument to the <CODE>+</CODE> function. compound expression:    An expression that contains subexpressions. Opposite of atomic expression. compound procedure:    A procedure that a programmer defines. This is the opposite of a primitive procedure. constructor:    A procedure that returns a new object of a certain type. For example, the <CODE>word</CODE> procedure is a constructor that takes words as arguments and returns a new word. See also selector, mutator, and abstract data type. data abstraction:    The invention of abstract data types. data structure:    A mechanism through which several pieces of information are combined into one larger unit. The most appropriate mechanism will depend on the ways in which the small pieces are used in the program, for example, sequentially or in arbitrary order. database program:    A program that maintains an organized collection of data, with facilities to modify or delete old entries, add new entries, and select certain entries for display. datum:    The piece of information stored in each node of a tree. debugging:    The process by which a programmer finds and corrects mistakes in a program. No interesting program works the first time; debugging is a skill to develop, not something to be ashamed of. destructive:    A destructive procedure is one that modifies its arguments. Since the only data type in this book that can be modified is the vector, all destructive procedures call <CODE>vector-set!</CODE>. domain:    The set of all legal arguments to a function. For example, the domain of the <CODE>count</CODE> function is the set of all sentences and all words. effect:    Something a procedure does other than return a value. For example, a procedure might create a file on disk, or print something to the screen, or change the contents of a vector. empty sentence:    The sentence <CODE>()</CODE>, which has no words in it. empty word:    The word <CODE>""</CODE>, which has no letters in it. end-of-file object:    What the file-reading procedures return if asked to read a file with no more unread data. expression:    The representation in Scheme notation of a request to perform a computation. An expression is either an atomic expression, such as <CODE>345</CODE> or <CODE>x</CODE>, or a compound expression consisting of one or more subexpressions enclosed in parentheses, such as <CODE>(+ 3 4)</CODE>. field:    A single component of a database record. For example, "title" is a field in our example database of albums. first-class data:    Data with the following four properties: <TABLE><TR><TH align="right" valign="top">•<TD>    <TD valign="top">It can be the argument to a procedure. </TABLE><TABLE><TR><TH align="right" valign="top">•<TD>    <TD valign="top">It can be the return value from a procedure. </TABLE><TABLE><TR><TH align="right" valign="top">•<TD>    <TD valign="top">It can be given a name. </TABLE><TABLE><TR><TH align="right" valign="top">•<TD>    <TD valign="top">It can be part of a data aggregate. </TABLE> In Scheme, words, lists, sentences, trees, vectors, ports, end-of-file objects, Booleans, and procedures are all first-class. forest:    A list of trees. formal parameter:    In a procedure definition, the name given to refer to an argument. In <PRE>(define (square x) (* x x))</PRE><CODE>x</CODE> is the formal parameter. (Note that this is not the same thing as an actual argument! When we invoke <CODE>square</CODE> later, the argument will be a number, such as 5. The parameter is the name for that number, not the number itself.) function:    A transformation of information that associates a return value with some number of argument values. There may be many different algorithms that compute the same function; the function itself is the relationship between argument values and return value, no matter how it may be implemented. functional programming:    A style of programming in which programs are expressed as compositions of functions, emphasizing their arguments and return values. Compare to sequential programming. global variable:    A variable created with <CODE>define</CODE>, which has meaning everywhere in the program. The opposite of a local variable. helper procedure:    A procedure that exists to help another procedure do its work. Normally, a user does not invoke a helper procedure directly. Instead, the user invokes a top-level procedure, which invokes the helper procedure to assist it in coming up with the answer. higher-order procedure:    A procedure whose domain or range includes other procedures. index:    A number used to select one of the elements of a vector. initialization procedure:    A procedure that doesn't do any work except to invoke a helper procedure with appropriate argument values. interactive:    An interactive program or programming language does its work in response to messages typed by the user at a keyboard (or perhaps indicated with a pointing device like a mouse). Each message from the user causes the program to respond in some way. By contrast, a non-interactive program works with input data that have been prepared in advance. invoke:    To ask a procedure to do its work and come up with a return value. For example, "Invoke the <CODE>+</CODE> procedure," or "Invoke the <CODE>+</CODE> procedure with the arguments <CODE>3</CODE> and <CODE>4</CODE>." keyword:    The name of a special form. kludge:    A method that gets the job done but isn't very elegant. Usually the result is a program that can't be extended the next time a new feature is needed. leaf node:    A tree node with no children. The opposite of a branch node. leap of faith:    A method for understanding recursion in which you say to yourself, "I'm going to assume that the recursive call always returns the right answer," and then use the answer from the recursive call to produce the answer to the entire problem. list:    A data aggregate containing elements that may be of any type. local variable:    A variable that associates a formal parameter name with an actual argument value. It's "local" because the variable exists only within one procedure invocation. (This includes variables created by <CODE>let</CODE>.) This is the opposite of a global variable. mutable:    A data structure is mutable if its contents can change. mutator:    A procedure that changes the value of a data object. In this book, the only mutable data objects we use are vectors, so every mutator is implemented using <CODE>vector-set!</CODE>. See also selector, constructor, and abstract data type. mutual recursion:    The program structure in which one procedure invokes another, and the second invokes the first. node:    An element of a tree. A node has a datum and zero or more children. parent:    The node above this one, in a tree. (See also children and siblings.) pattern matcher:    A program that takes a pattern and a piece of data as inputs and says whether or not that piece of data is one that the pattern describes. We present a pattern matcher in Chapter 16. plumbing diagram:    A pictorial representation of the composition of functions, with the return value from one procedure connected to an argument intake of another. port:    An object that Scheme uses to keep track of a file that is currently open for reading or writing. portable:    A portable program is one that can be run in more than one version of Scheme or on more than one computer. potsticker:    A Chinese dumpling stuffed with meat and vegetables, first steamed and then pan-fried, or sometimes first pan-fried and then simmered in water added to the pan. predicate:    A procedure that always returns a Boolean value. By convention, Scheme predicates have names like "<CODE>equal?</CODE>" that end in a question mark. primitive procedure:    A procedure that is already defined when a Scheme session begins. By contrast, a compound procedure is one that the programmer defines in Scheme. procedure:    The expression of an algorithm in Scheme notation. prompt:    A character or characters that an interactive program prints to tell the user that it's ready for the user to type something. In many versions of Scheme, the prompt is a <CODE>></CODE> character. random access:    A data structure allows random access if the time required to locate an element of the structure is independent of its position within the structure. range:    The set of all possible return values from a function. For example, the range of the <CODE>count</CODE> function is the set of non-negative integers. read-eval-print loop:    The overall structure of a Scheme interpreter. It reads an expression from the keyboard, evaluates the expression by invoking procedures, etc., and prints the resulting value. The same process repeats forever. record:    One complete entry in a database. For example, one album in our database of albums. A record contains several fields. recursion:    Solving a big problem by reducing it to smaller problems of the same kind. If something is defined recursively, then it's defined in terms of itself. See recursion. recursive case:    In a recursive procedure, the part that requires a recursive invocation. The opposite of the base case. rest parameter:    A parameter that represents a variable number of arguments. In the formal parameter list <CODE>(a b . x)</CODE>, <CODE>x</CODE> is a rest parameter. result replacement:    A technique people can use to figure out the value of a complicated Scheme expression by rewriting the expression repeatedly, each time replacing some small subexpression with a simpler expression that has the same value, until all that's left is a single quoted or self-evaluating value. robust:    Able to function despite user errors. Robust programs check for likely errors and recover from them gracefully. root node:    The node at the very top of a tree. selector:    A procedure that takes an object as its argument and returns some part of that object. For example, the selector <CODE>first</CODE> takes a word or sentence as argument and returns the first letter of the word or first word of the sentence. See also constructor, mutator, and abstract data type. self-evaluating:    An expression is self-evaluating if, when evaluated, it has as its value the expression itself. Numbers, Booleans, and strings are the only self-evaluating objects we use in this book. semipredicate:    A procedure that answers a yes-no question by returning <CODE>#f</CODE> for "no," but instead of returning <CODE>#t</CODE> for "yes," it returns some additional piece of information. The primitive <CODE>member</CODE> procedure is a good example of a semipredicate. ("Semipredicate" isn't a common term; we made it up for this book.) sequencing:    Evaluating two or more expressions one after the other, for the sake of their effects. sequential programming:    A style of programming in which programs say, "First do this, then do that, then do that other thing." (Compare to functional programming.) siblings:    Two nodes of a tree that are the children of the same node. (See also children and parent.) side effect:    See effect. special form:    A Scheme expression that begins with a keyword and is evaluated using a special rule. In particular, some of the subexpressions might not be evaluated. The keywords used in this book are <CODE>and</CODE>, <CODE>begin</CODE>, <CODE>cond</CODE>, <CODE>define</CODE>, <CODE>if</CODE>, <CODE>lambda</CODE>, <CODE>let</CODE>, <CODE>or</CODE>, and <CODE>quote</CODE>. (The keyword itself is also sometimes called a special form.) spreadsheet program:    A program that maintains a two-dimensional display of data can compute some elements automatically, based on the values of other elements. state:    A program's memory of what has happened in the past. string:    A word delimited by double-quote marks, such as <CODE>"A Hard Day's Night"</CODE> or <CODE>"000123"</CODE>. structured list:    A list with sublists. subexpression:    An element of a compound expression. For example, the expression <CODE>(+ (* 2 3) 4)</CODE> has three subexpressions: <CODE>+</CODE>, <CODE>(* 2 3)</CODE>, and <CODE>4</CODE>. sublist:    An element of a list that is itself a smaller list. For example, <CODE>(c d)</CODE> is a sublist of the list <CODE>(a b (c d) e)</CODE>. substitution model:    The way we've explained how Scheme evaluates function invocations. According to the substitution model, when a compound procedure is invoked, Scheme goes through the body of that procedure and replaces every copy of a formal parameter with the corresponding actual argument value. Then Scheme evaluates the resulting expression. subtree:    A tree that is part of a larger tree. symbol:    A word that isn't a number or a string. symbolic computing:    Computing that is about words, sentences, and ideas instead of just numbers. tree:    A two-dimensional data structure used to represent hierarchical information. tree recursion:    A form of recursion in which a procedure calls itself recursively more than one time in each level of the recursion. type:    A category of data. For example, words, sentences, Booleans, and procedures are types. Some types overlap: All numbers are also words, for example. variable:    A connection between a name and a value. Variables can be global or local. vector:    A primitive data structure that is mutable and allows random access. word:    A sequence of characters, including letters, digits, or punctuation. Numbers are a special case of words. <HR> <A HREF="../ss-toc2.html">(back to Table of Contents)</A> <A HREF="appendix-funlist.html">BACK</A> chapter thread <A HREF="appuindex.html">NEXT</A> <ADDRESS> <A HREF="../index.html">Brian Harvey</A>, <CODE>bh@cs.berkeley.edu</CODE> </ADDRESS> </BODY> </HTML>