III Abstraction
16 Similarities Everywhere
Many of our data definitions and function definitions look alike. For example, the definition for a list of strings differs from that of a list of numbers in only two regards: the name of the class of data and the words “string” and “number.” Similarly, a function that looks for a specific string in a list of strings is nearly indistinguishable from one that looks for a specific number in a list of numbers.
Over the years, Seen this way, a program is just like an essay or a memo. The first version is just a draft, and drafts demand editing. people have come to realize that these kinds of similarities are problematic. Therefore good programmers try to eliminate them as much as possible. “Eliminate” implies that programmers write down their first drafts of programs, spot similarities, and then rework their drafts. Good programmers go through several such rounds of editing, but they also know when to stop because further rounds of editing eliminate only insignificant similarities.
This chapter is about eliminating similarities in function definitions and in data definitions, a process that is called abstraction. Our means of avoiding similarities are specific to “Intermediate Student Language” or ISL for short. In DrRacket, choose “Intermediate Student Language” from the “How to Design Programs” submenu in the “Language” menu. Other programming languages provide similar means, but in objectoriented languages you may find additional mechanisms. Nevertheless, all abstraction step share the basic ideas spelled out in this chapter, and it will thus help you become a good programmer.
16.1 Similarities In Functions
The design recipe determines a function’s basic organization because the template is created from the data definition without regard to the purpose of the function. Not surprisingly then, functions that consume the same kind of data look alike.
; Los > Boolean ; does l contain "dog" (define (containsdog? l) (cond [(empty? l) false] [else (or (string=? (first l) "dog") (containsdog? (rest l)))]))
; Los > Boolean ; does l contain "cat" (define (containscat? l) (cond [(empty? l) false] [else (or (string=? (first l) "cat") (containscat? (rest l)))]))
Consider the two functions in figure 50, which consume lists of strings and look for specific strings. The function on the left looks for "dog", the one on the right for "cat". The two functions are nearly indistinguishable. Each consumes lists of strings; each function body consists of a cond expressions with two clauses. Each produces false if the input is empty; each uses an or expressions to determine whether the first item is the desired item and, if not, uses recursion to look in the rest of the list. The only difference is the string that is used in the comparison of the nested cond expressions: containsdog? uses "dog" and containscat? uses "cat". To highlight the differences, the two strings are shaded.
; String Los > Boolean ; to determine whether l contains the string s (define (contains? s l) (cond [(empty? l) false] [else (or (string=? (first l) s) (contains? s (rest l)))]))
; Los > Boolean ; does l contain "dog" (define (containsdog? l) (contains? "dog" l))
; Los > Boolean ; does l contain "cat" (define (containscat? l) (contains? "cat" l))
Computing borrows the term “abstract” from mathematics. A mathematician refers to “6” as an abstract number because it only represents all different ways of naming six things. In contrast, “6 inches” or “6 eggs” are concrete instances of “6” because they express a measurement and a count. What you have just seen is called functional abstraction. Abstracting different versions of functions is one way to eliminate similarities from programs, and as you can see with this one simple example, doing so simplifies programs.
Exercise 198. Use contains? to define functions that search for "atom", "basic", and "zoo", respectively.
; Lon > Lon ; add 1 to each number on l (define (add1* l) (cond [(empty? l) '()] [else (cons (add1 (first l)) (add1* (rest l)))]))
; Lon > Lon ; add 5 to each number on l (define (plus5 l) (cond [(empty? l) '()] [else (cons (+ (first l) 5) (plus5 (rest l)))])) Then abstract over them. Define above two functions in terms of the abstraction as oneliners and use the existing test suites to confirm that the revised definitions work properly. Finally, design a function that subtracts 2 from each number on a given list.
16.2 More Similarities In Functions
Abstraction looks easy in the case of containsdog? and containscat?. It takes only a comparison of two function definitions, a replacement of a literal string with a function parameter, and a quick check that it is easy to define the old functions with the abstract function. This kind of abstraction is so natural that it showed up in the preceding two parts of the book without much ado.
This section illustrates how the very same principle yields a powerful form of abstraction. Take a look at figure 52. Both functions consume a list of numbers and a threshold. The left one produces a list of all those numbers that are below the threshold, while the one on the right produces all those that are above the threshold.
; Lon Number > Lon ; construct the list of numbers ; on l that are below t (define (small l t) (cond [(empty? l) empty] [else (cond [(< (first l) t) (cons (first l) (small (rest l) t))] [else (small (rest l) t)])]))
; Lon Number > Lon ; construct the list of numbers ; on l that are above t (define (large l t) (cond [(empty? l) empty] [else (cond [(> (first l) t) (cons (first l) (large (rest l) t))] [else (large (rest l) t)])]))
The two functions different in only one place: the comparison operator that determines whether a number from the given list should be a part of the result or not. The function on the left uses <, the right one >. Other than that, the two functions look identical, not counting the function name.
(define (extract R l t) (cond [(empty? l) empty] [else (cond [(R (first l) t) (cons (first l) (extract R (rest l) t))] [else (extract R (rest l) t)])]))
Stop! At this point you should ask whether this definition makes any
sense. Without further ado, we have created a function that consumes a
function—
(extract < (cons 4 empty) 5) = (cond [(empty? (cons 4 empty)) empty] [else (cond [(< (first (cons 4 empty)) 5) (cons (first (cons 4 empty)) (extract < (rest (cons 4 empty)) 5))] [else (extract < (rest (cons 4 empty)) 5)])])
(cond [(empty? (cons 4 empty)) empty] [else (cond [(< (first (cons 4 empty)) 5) (cons (first (cons 4 empty)) (extract < (rest (cons 4 empty)) 5))] [else (extract < (rest (cons 4 empty)) 5)])]) = (cond [false empty] [else (cond [(< (first (cons 4 empty)) 5) (cons (first (cons 4 empty)) (extract < (rest (cons 4 empty)) 5))] [else (extract < (rest (cons 4 empty)) 5)])]) = (cond [(< (first (cons 4 empty)) 5) (cons (first (cons 4 empty)) (extract < (rest (cons 4 empty)) 5))] [else (extract < (rest (cons 4 empty)) 5)]) = (cond [(< 4 5) (cons (first (cons 4 empty)) (extract < (rest (cons 4 empty)) 5))] [else (extract < (rest (cons 4 empty)) 5)]) = (cond [true (cons (first (cons 4 empty)) (extract < (rest (cons 4 empty)) 5))] [else (extract < (rest (cons 4 empty)) 5)]) = (cons 4 (extract < (rest (cons 4 empty)) 5)) = (cons 4 (extract < empty 5)) = (cons 4 empty)
(extract < (cons 6 (cons 4 empty)) 5) = (extract < (cons 4 empty) 5) = (cons 4 (extract < empty 5)) = (cons 4 empty)
by hand. Show every step.
by hand. Show the new steps, rely on prior calculations where possible.


; Number Number > Boolean ; is the area of a square with side x larger than c (define (squared>? x c) (> (* x x) c))
(extract squared>? (list 3 4 5) 10)
Exercise 202. Evaluate (squared>? 3 10), (squared>? 4 10), and (squared>? 5 10) by hand. Then show that(extract squared>? (list 3 4 5) 10)
So far you have seen that abstracted function definitions can be more useful than the functions you start from. For example, contains? is more useful than containsdog? and containscat?, and extract is more useful than small and large. These effects of abstraction are crucial for large, industrial programming projects. For that reason, programming language and software engineering research has focused on how to create single points of control in large projects. Of course, the same idea applies to all kinds of computer designs (word documents, spread sheets) and organizations in general. Another important aspect of abstraction is that you now have a single point of control over all these functions. If it turns out that the abstract function contains a mistake, fixing its definition suffices to fix all other definitions. Similarly, if you figure out how to accelerate the computations of the abstract function or how to reduce its energy consumption, then all functions defined in terms of this function are improved without further ado. The following exercises indicate how these singlepointofcontrol improvements work.
; Nelon > Number ; to determine the smallest ; number on l (define (inf l) (cond [(empty? (rest l)) (first l)] [else (cond [(< (first l) (inf (rest l))) (first l)] [else (inf (rest l))])]))
; Nelon > Number ; to determine the largest ; number on l (define (sup l) (cond [(empty? (rest l)) (first l)] [else (cond [(> (first l) (sup (rest l))) (first l)] [else (sup (rest l))])])) Both consume nonempty lists of numbers (Nelon) and produce a single number. The left one produces the smallest number in the list, the right one the largest.Define inf1 and sup1 in terms of the abstract function. Test each of them with these two lists:
(list 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1) (list 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25) Why are these functions slow on some of the long lists?Modify the original functions with the use of max, which picks the larger of two numbers, and min, which picks the smaller one. Then abstract again, define inf2 and sup2, and test them with the same inputs again. Why are these versions so much faster?
For a complete answer to the two questions on performance, see Local Function Definitions.
16.3 Similarities In Data Definitions


[Listof Number] says that ITEM represents all numbers so the notation is just another name for Listofnumbers;
[Listof String] defines the same class of data as ListofString; and
 if we had identified a class of inventory records, like this:
(definestruct ir (name price)) ; An IR is ; (makeir String Number)
(definestruct point (hori veri))


To instantiate a data definition with two parameters, you need two names of data collections. Using Number and Image for the parameters of CP, you get [CP Number Image], which describes the collections of points that combine a number with an image. In contrast [CP Boolean String] combines Boolean values with strings in a point structure.
; A Nestedstring is one of: ; – String ; – (makelayer Nestedstring)
; A Nestednumber is one of: ; – Number ; – (makelayer Nestednumber) Both data definitions exploit this structure type definition:(definestruct layer (stuff))
Both define nested forms of data’ one is about numbers and the other about strings. Make examples for both. Abstract over the two. Then instantiate the abstract definition to get back the originals.
; A [Bucket ITEM] is ; (makebucket N [Listof ITEM]) ; interp. the n in (makebucket n l) is the length of l ; i.e., (= (length l) n) is always true When you instantiate Bucket with String, IR, and Posn, you get three different data collections. Describe each of them with a sentence and with two distinct examples.Now consider this instantiations:Construct three distinct pieces of data that belong to this collection.
; A [Maybe X] is one of: ; – false ; – X Interpret the following data definitions:What does the following function signature mean:
; String [Listof String] > [Maybe [Listof String]] ; returns the remainder of the list los if it contains s ; false otherwise (checkexpect (occurs "a" (list "b" "a" "d")) (list "d")) (checkexpect (occurs "a" (list "b" "c" "d")) #f) (define (occurs s los) los) Design the function.
16.4 Functions Are Values
The functions of this section stretch our understanding of program evaluation. It is easy to understand how functions consume more than numbers, say strings, images, and Boolean values. Structures and lists are a bit of a stretch, but they are finite “things” in the end. Functionconsuming functions, however, are strange. Indeed, these kind of functions violate the BSL grammar of the first intermezzo in two ways. First, the names of primitive operations and functions are used as arguments in applications. Second, parameters are used as if they were functions, that is, the first position of applications.
Spelling out the problem tells you how the ISL grammar differs from BSL’s. First, our expression language should include the names of functions and primitive operations in the definition. Second, the first position in an application should allow things other than function names and primitive operations; at a minimum, it must allow variables and function parameters. In anticipation of other uses of functions, we agree on allowing arbitrary expressions in that position.
The changes to the grammar seem to demand changes to the evaluation rules, but they don’t change at all. All that changes is the set of values. To accommodate functions as arguments of functions, the simplest change is to say that functions are values. Thus, we start using the names of functions and primitive operations as values; later we introduce another way to deal with functions as values.
Exercise 207. Assume the definitions area in DrRacket contains (define (f x) x). Identify the values among the following expressions:Explain why they are values and why the remaining expressions are not values.
Explain your reasoning.
Exercise 209. Develop function=at123and5.775?. The function determines whether two functions from numbers to numbers produce the same results for 1.2, 3, and 5.775.
Mathematicians say that two functions are equal if they compute the same result when given the same input—
for all possible inputs. Can we hope to define function=?, which determines whether two functions from numbers to numbers are equal f? If so, define the function. If not, explain why and consider the implication that you have encountered the first easily definable idea for which you cannot define a function.
17 Designing Abstractions
In essence, to abstract is to turn something concrete into a parameter. We have this several times in the preceding section. To abstract similar function definitions, you add parameters that replace concrete values in the definition. To abstract similar data definitions, you create parametric data definitions. When you will encounter other programming languages, you will see that their abstraction mechanisms also require the introduction of parameters, though they may not be function parameters.
17.1 Abstractions From Examples
When you first learned to add, you worked with concrete examples. Your parents probably taught you to use your fingers to add two small numbers. Later on, you studied how to add two arbitrary numbers; you were introduced to your first kind of abstraction. Much later still, you learned to formulate expressions that convert temperatures from Celsius to Fahrenheit or calculate the distance that a car travels at a certain speed in a given amount of time. In short, you went from very concrete examples to abstract relations.
This section introduces a design recipe for creating abstractions from examples. As the preceding section shows, creating abstractions is easy. We leave the difficult part to the next section where we show you how to find and use existing abstractions.
Step 1 is to compare two items for similarities.
When you find two function definitions that are almost the same except for their namesThe recipe requires a substantial modification for abstracting over nonvalues. and some values at a few analogous places, compare them, mark the differences. If the two definitions differ in more than one place, connect the corresponding differences with a line or a comment.
Here is a pair of similar function definitions:; Listofnumbers > Listofnumbers ; convert a list of Celsius ; temperatures to Fahrenheit (define (cf* l) (cond [(empty? l) empty] [else (cons (C2F (first l)) (cf* (rest l)))])) ; Inventory > Listofstrings ; extract the names of toys ; from an inventory (define (names i) (cond [(empty? i) empty] [else (cons (IRname (first i)) (names (rest i)))])) ; ; Number > Number ; convert one Celsius ; temperature to Fahrenheit (define (C2F c) (+ (* 9/5 c) 32)) ; (definestruct IR (name price)) ; An IR is (makeIR String Number) ; An Inventory is one of: ; – empty ; – (cons IR Inventory) The two functions apply a function to each item in a list. They differ only as to which function they apply to each item. The two highlights emphasize this essential difference. They also differ in two inessential was: the names of the function and the names of the parameters.
Next we abstract. To abstract means to replace the contents of corresponding code highlights with new names and add these names to the parameter list. For our running example, we obtain the following pair of functions after replacing the differences with g:
(define (cf* l g) (cond [(empty? l) empty] [else (cons (g (first l)) (cf* (rest l) g))])) (define (names i g) (cond [(empty? i) empty] [else (cons (g (first i)) (names (rest i) g))])) This first change eliminates the essential difference. Now each function traverses a list and applies some given function to each item.The inessential differences—
the names of the functions and occasionally the names of some parameters— are easy to eliminate. Indeed, if you have explored DrRacket, you know that check syntax allows you to do this systematically and easily: (define (map1 k g) (cond [(empty? k) empty] [else (cons (g (first k)) (map1 (rest k) g))])) (define (map1 k g) (cond [(empty? k) empty] [else (cons (g (first k)) (map1 (rest k) g))])) We choose to use map1 for the name of the function and k for the name of the list parameter. No matter which names you choose, the result is two identical function definitions.Our example is simple. In many cases, you will find that there is more than just one pair of differences. The key is to find pairs of differences. When you mark up the differences on paper and pencil, connect related boxes with a line. Then introduce one additional parameter per line. And don’t forget to change all recursive uses of the function so that the additional parameters go along for the ride.
Now we must validate that the new function is a correct abstraction of the original pair of functions. To validate means to test to test, which here means to define the two original functions in terms of the abstraction.
Thus suppose that one original function is called foriginal and consumes one argument and that the abstract function is called abstract. If foriginal differs from the other concrete function in the use of one value, say, val, the following function definition(define (ffromabstract x) (abstract x val)) introduces the function ffromabstract, which should be equivalent to foriginal. That is, for every proper value V, (ffromabstract V) should produce the same answer as (foriginal V). This particularly true for all values that your tests for foriginal use. So reformulate and rerun those tests for ffromabstract and make sure they succeed.Let us return to our running example:; Listofnumbers > Listofnumbers (define (cf*frommap1 l) (map1 l C2F)) ; Inventory > Listofstrings (define (namesfrommap1 i) (map1 i IRname)) A complete example would include some tests, and thus we can assume that both cf* and names come with some tests:(checkexpect (cf* (list 100 0 40)) (list 212 32 40)) (checkexpect (names (list (makeIR "doll" 21.0) (makeIR "bear" 13.0))) (list "doll" "bear")) To ensure that the functions defined in terms of map1 work properly, you can copy the tests and change the function names appropriately:(checkexpect (cf*frommap1 (list 100 0 40)) (list 212 32 40)) (checkexpect (namesfrommap1 (list (makeIR "doll" 21.0) (makeIR "bear" 13.0))) (list "doll" "bear")) To make a new abstraction useful, it needs a signature. As Using Abstractions, Part I explains, reuse of abstract functions start with their signatures. Finding useful signatures is, however, a serious problem. For now we just use the running example to illustrate the problem. Similarities In Signatures below resolves the issue.
So consider the problem of finding a signature for map1. On the one hand, if you view map1 as an abstraction of cf*, you might think the signature is; Listofnumbers (Number > Number) > Listofnumbers
That is, the original signature extended with one signature for functions: (Number > Number). Since the additional parameter for map1 is a function, the use of a function signature shouldn’t surprise you. This function signature is also quite simple; it is a “name” for all the functions from numbers to numbers. Here C2F is such a function, and so are add1, sin, and imagpart.On the other hand, if you view map1 as an abstraction of names, the signature is quite different:; Inventory (IR > String) > Listofstrings
This time the additional parameter is IRname, which is a selector function that consumes IRs and produces Strings. But clearly this second signature would be useless in the first case, and vice versa. To accommodate both cases, the signature for map1 must express that Number, IR, and String are coincidental.Also concerning signatures, you are probably eager to use Listof by now. It is clearly easier to write [Listof IR] than spelling out a data definition for Inventory. So yes, as of now, we use Listof when it is all about lists and you should too.
; Listofnumbers > Listofnumbers (define (add1toeach l) (map1 add1 l))
; Number > [Listof Number] ; tabulate sin between n ; and 0 (inclusive) in a list (define (tabsin n) (cond [(= n 0) (list (sin 0))] [else (cons (sin n) (tabsin (sub1 n)))]))
; Number > [Listof Number] ; tabulate sqrt between n ; and 0 (inclusive) in a list (define (tabsqrt n) (cond [(= n 0) (list (sqrt 0))] [else (cons (sqrt n) (tabsqrt (sub1 n)))]))
; [Listof Number] > Number (define (product l) (cond [(empty? l) 1] [else (* (first l) (product (rest l)))]))
; [Listof Posn] > Image (define (image* l) (cond [(empty? l) emt] [else (placedot (first l) (image* (rest l)))])) ; Posn Image > Image (define (placedot p img) (placeimage dot (posnx p) (posny p) img)) ; graphical constants: (define emt (emptyscene 100 100)) (define dot (circle 3 "solid" "red")) Compare this exercise with exercise 211. Even though both involve the product function, this exercise poses an additional challenge because the second function, image*, consumes a list of Posns and produces an Image. Still, the solution is within reach of the material in this section, and it is especially worth comparing the solution with the one to the preceding exercise. The comparison yields interesting insights into abstract signatures.
Last but not least, when you are dealing with data definitions, the abstraction process proceed in an analogous manner. The extra parameters to data definitions stands for collections of values, and to testing means to spell out a data definition for some concrete examples. All in all, abstracting over data definitions tends to be easier than abstracting over functions, and so we leave it to you to adapt the design recipe appropriately.
17.2 Similarities In Signatures
As it turns out, a function’s signature is key to its reuse. Thus, to
increase the usefulness of an abstract function, you must learn to
formulate signatures that describes abstracts in their most general terms
possible. To understand how this works, we start with a second look at
signatures and from the simple—
; Number Boolean > String (define (f n b) "hello world")
In general, the arrow notation of signatures is like the
Listof notation from Similarities In Data Definitions.
The latter consumes (the name of) one class of data, say X, and describes
all lists of X items—
What this means is that the abstraction design recipe applies to signatures, too. You compare similar signatures; you highlight the differences; and then you replace those with parameters. But the process of abstracting signatures feels more complicated than the one for functions, partly because signature are already abstract pieces of the design recipe and partly because the arrowbased notation is much more complex than anything else we have encountered.
both signatures describe oneargument functions;
both argument descriptions employ the Listof construction;
To make more progress on a signature for the abstraction of the two functions in exercise 212, we need to take the first two steps of the design recipe:


; [X Y] [Listof X] Y (X Y > Y) > Y
Given two similar function definitions, f and g, compare their signatures for similarities and differences. The goal is to discover the organization of the signature and to mark the places where one signature differs from the other. Connect the differences as pairs just like you do when you analyze function bodies.
Abstract f and g into fabs and gabs. That is, add parameters that eliminate the differences between f and g. Create signatures for fabs and gabs. Keep in mind what the new parameters originally stood for; this helps you figure out the new pieces of the signatures.
Check whether the analysis of step 1 extends to the signatures of fabs and gabs. If so, replace the differences with variables that range over classes of data. Once the two signatures are the same you have a signature for the abstracted function.
 Test the abstract signature in two ways. First, ensure that suitable substitutions of the variables in the abstract signature yield the signatures of fabs and gabs. Second, check that the generalized signature is in sync with the code. For example, if p is a new parameter and its signature is
; ... (A B > C) ....
then p should always be applied to two arguments, the first one from A and the second one from B. And the result of an application of p is going to be a C and should be used where elements of C are expected.
; (Number > Boolean) ; (Boolean String > Boolean) ; (Number Number Number > Number) ; (Number > [Listof Number]) ; ([Listof Number] > Boolean) Describe these collections with at least one example from ISL.
sortn, which consumes a list of numbers and a function that consumes two numbers (from the list) and produces a Boolean; sortn produces a sorted list of numbers.
sorts, which consumes a list of srings and a function that consumes two strings (from the list) and produces a Boolean; sorts produces a sorted list of strings.
Then abstract over the two signatures, following the above steps. Also show that the generalized signature can be instantiated to describe the signature of a sort function for lists of IRs.
mapn, which consumes a list of numbers and a function from numbers to numbers to produce a list of numbers.
maps, which consumes a list of srings and a function from strings to strings and produces a list of strings.
Then abstract over the two signatures, following the above steps. Also show that the generalized signature can be instantiated to describe the signature of the mapIR function above.
17.3 Single Point Of Control
In general, programs are like drafts of papers. Editing drafts is important to correct typos, to fix grammatical mistakes, to make the document consistent, and to eliminate repetitions. Nobody wants to read papers that repeat themselves a lot, and nobody wants to read such programs either.
The elimination of similarities in favor of abstractions has many advantages. Creating an abstraction simplifies definitions. It may also uncover problems with existing functions, especially when similarities aren’t quite right. But, the single most important advantage is the creation of single points of control for some common functionality.
Putting the definition for some functionality in one place makes it easy to maintain a program. When you discover a mistake, you have to go to just one place to fix it. When you discover that the code should deal with another form of data, you can add the code to just one place. When you figure out an improvement, one change improves all uses of the functionality. If you had made copies of the functions or code in general, you would have to find all copies and fix them; otherwise the mistake might live on or the only one of the functions would run faster.
We therefore formulate this guideline:
Creating Abstractions: Form an abstraction instead of copying and modifying any piece of a program.
Our design recipe for abstracting functions is the most basic tool to create abstractions. To use it requires practice. As you practice, you expand your capabilities to read, organize, and maintain programs. The best programmers are those who actively edit their programs to build new abstractions so that they collect things related to a task at a single point. Here we use functional abstraction to study this practice; in other courses on programming, you will encounter other forms of abstraction, most importantly inheritance in classbased objectoriented languages.
17.4 Abstractions From Templates
Over the course of the first two chapters, we have designed many functions using the same template. After all, the design recipe says to organize functions around the organization of the (major) input data definition. It is therefore not surprising that many function definitions look similar to each other.
; [X Y] [Listof X] Y (X Y > Y) > Y (define (reduce l base combine) (cond [(empty? l) base] [else (combine (first l) (reduce (rest l) base combine))]))


18 Using Abstractions, Part I
Many programming languages provide a number of looping constructs, or loop for short. A loop processes a compound piece of data, one piece at a time. In our terminology a loop abstracts over the traversal of data and applies some given function to each of its pieces. You have encountered several such loops in the first two sections of this chapter: extract, fold1, map1, etc. These functions consume a function and apply it to each item on some list.
Once you have such loop abstractions, you should use them when possible. They create single points of control data, and they are a worksaving device. To make this precise, the use of an abstraction helps the reader of your code to understand your intentions, in particular if the abstraction is wellknown and built into the language or comes with its standard libraries.
This chapter is all about the reuse of existing ISL abstractions. It starts with a section on existing ISL abstractions, some of which you have seen under false names. The remaining sections are about reusing such abstractions. One key ingredient is a new syntactic construct, local, for defining functions and variables (and even structure types) locally within a function. An auxiliary ingredient, introduced in the last section, is the lambda construct for creating nameless functions; lambda is a convenience but inessential to the idea of reusing abstract functions.
; [X] N (N > X) > [Listof X] ; construct a list by applying f to 0, 1, ..., (sub1 n) ; (buildlist f n) = (list (f 0) ... (f ( n 1))) (define (buildlist n f) ...) ; [X] (X > Boolean) [Listof X] > [Listof X] ; produce a list from all those items on alox for which p holds (define (filter p alox) ...) ; [X] [Listof X] (X X > Boolean) > [Listof X] ; produce a variant of alox that is sorted according to cmp (define (sort alox cmp) ...) ; [X Y] (X > Y) [Listof X] > [Listof Y] ; construct a list by applying f to each item on alox ; (map f (list x1 ... xn)) = (list (f x1) ... (f xn)) (define (map f alox) ...) ; [X] (X > Boolean) [Listof X] > Boolean ; determine whether p holds for every item on alox ; (andmap p (list x1 ... xn)) = (and (p x1) ... (p xn)) (define (andmap p alox) ...) ; [X] (X > Boolean) [Listof X] > Boolean ; determine whether p holds for at least one item on alox ; (ormap p (list x1 ... xn)) = (or (p x1) ... (p xn)) (define (ormap p alox) ...) ; [X Y] (X Y > Y) Y [Listof X] > Y ; compute the result of applying f from right to left to all of ; alox and base, that is, apply f to ; the last item in alox and base, ; the penultimate item and the result of the first step, ; and so on up to the first item ; (foldr f base (list x1 ... xn)) = (f x1 ... (f xn base)) (define (foldr f base alox) ...) ; [X Y] (X Y > Y) Y [Listof X] > Y ; compute the result of applying f from left to right to all of ; alox and base, that is, apply f to ; the first item in alox and base, ; the second item and the result of the first step, ; and so on up to the last item: ; (foldl f base (list x1 ... xn)) = (f xn ... (f x1 base)) (define (foldl f base alox) ...) WARNING: you cannot design buildlist, buildstring, or foldl with the design principles you know at this point; Accumulators covers the necessary ideas.
Figure 53: ISL's builtin abstract functions for listprocessing
18.1 Existing Abstractions
> (buildlist 3 add1) (list 1 2 3)
> (filter odd? (list 1 2 3 4 5)) (list 1 3 5)
> (sort (list 3 2 1 4 5) >) (list 5 4 3 2 1)
> (map add1 (list 1 2 2 3 3 3)) (list 2 3 3 4 4 4)


(definestruct address (firstname lastname street)) ; Addr is (makeaddress String String String) ; [Listof Addr] > String ; a string of first names, sorted in alphabetical order, ; separated and surrounded by blank spaces (define (listing l) (foldr stringappendwithspace " " (sort (map addressfirstname l) string<?))) ; String String > String ; juxtapoint two strings and prefix with space (define (stringappendwithspace s t) (stringappend " " s t)) (define ex0 (list (makeaddress "Matthias" "Fellson" "Sunburst") (makeaddress "Robert" "Findler" "South") (makeaddress "Matthew" "Flatt" "Canyon") (makeaddress "Shriram" "Krishna" "Yellow"))) (checkexpect (listing ex0) " Matthew Matthias Robert Shriram ")
Figure 54 illustrates the power of composing the functions from figure 53. Its main function is listing. The purpose is to create a string from a list of addresses. More precisely, the expected result is a string that represents a sorted list of first names, separated and surrounded by blank spaces.
design a function that extracts the first names from the given list of Addr;
design a function that sorts these names in alphabetical order;
design a function that juxtaposes the strings from step 2.
(map addressfirstname l)
18.2 Local Function Definitions
Take a second look at figure 54. The stringappendwithspace function clearly plays a subordinate role and has no use outside of this narrow context. Almost all programming languages support some way for stating this relationship as a part of the program. The idea is called a local definition, sometimes also a private definition. In ISL, local expressions introduce locally defined functions, variables, and structure types, and this section introduces the mechanics of local.
; [Listof Addr] > String ; a string of first names, sorted in alphabetical order, ; separated and surrounded by blank spaces (define (listing.v2 l) (local (; String String > String ; juxtapoint two strings and prefix with space (define (stringappendwithspace s t) (stringappend " " s t))) (foldr stringappendwithspace " " (sort (map addressfirstname l) string<?))))
In this example, the sequence of definitions consists of a single function definition, the one for stringappendwithspace. The body of local is the body of the original listing function. Its reference to stringappendwithspace is now resolved locally, that is, there is no need to look in the global sequence of definitions. Conversely, outside of the local expression, it is impossible to refer to stringappendwithspace. Since there is no such reference in the original program, it remains intact and you can confirm this with the test suite.
; [Listof Number] (Number Number > Boolean) > [Listof Number] (define (sortcmp alon0 cmp) (local (; [Listof Number] > [Listof Number] ; produces a variant of alon sorted by cmp (define (isort alon) (cond [(empty? alon) empty] [else (insert (first alon) (isort (rest alon)))])) ; Number [Listof Number] > [Listof Number] ; insert n into the sorted list of numbers alon (define (insert n alon) (cond [(empty? alon) (cons n empty)] [else (if (cmp n (first alon)) (cons n alon) (cons (first alon) (insert n (rest alon))))]))) (isort alon0)))
By making insert local, it also becomes impossible to abuse
insert. Reread its purpose statement. The adjective “sorted”
means that a program should use insert only if the second
argument is already sorted. As long as insert is defined at the
toplevel, nothing guarantees that insert is always used
properly. Once its definition is local to the sortcmp function,
the proper use is guaranteed—
Exercise 216. Use a local expression to organize the functions for drawing a polygon in figure 47. If a globally defined functions is widely useful, do not make it local.
Exercise 217. Use a local expression to organize the functions for rearranging words from Rearranging Words.
; Nelon > Number ; to determine the smallest number on l (define (inf l) (cond [(empty? (rest l)) (first l)] [else (local ((define smallestinrest (inf (rest l)))) (cond [(< (first l) smallestinrest) (first l)] [else smallestinrest]))]))
; Lon > Lon ; constructs a list from the items in l in descending order (define (sort> l0) (local (; Lon > Lon (define (sort l) (cond [(empty? l) empty] [else (insert (first l) (sort (rest l)))])) ; Number Lon > Lon (define (insert an l) (cond [(empty? l) (list an)] [else (cond [(> an (first l)) (cons an l)] [else (cons (first l) (insert an (rest l)))])]))) (sort l0))) Create a test suite for sort>.Design the function sort<, which sorts lists of numbers in ascending order.
Create sorta, which abstracts sort> and sort<. It consumes the comparison operation in addition to the list of numbers. Define versions sort> and sort< in terms of sorta.
Use sorta to define a function that sorts a list of strings by their lengths, both in descending and ascending order.
Later we will introduce several different ways to sort lists of numbers, all of them faster than sorta. If you then change sorta, all uses of sorta will benefit.
18.3 ... Add Expressive Power
The third and last example illustrates how local adds expressive
power to BSL+. It starts from the code for simulating finite state
machine in Finite State Machines. After a first analysis, this section
points out that it is impossible to organize the program in a natural
way—
; FSM > FSMState ; interpret a given finite state machine (define (simulate fsm0) (local (; A SimulationState is FSMState. (define initialworldstate (fsmcurrent fsm0)) (define TRANSITIONTABLE (fsmtransitions fsm0)) ; SimulationState > Image ; render current state as colored square (define (stateascoloredsquare s) (square 100 "solid" s)) ; SimulationState KeyEvent > SimulationState ; find the next state in the transition table of fsm0 (define (findnextstate s keyevent) (find TRANSITIONTABLE s)) ; Transitions SimulationState > SimulationState ; find the state matching current ; in the given transition table (define (find transitions current) (cond [(empty? transitions) (error "not found")] [else (local ((define s (first transitions))) (if (state=? (transitioncurrent s) current) (transitionnext s) (find (rest transitions) current)))]))) ; now launch the world (bigbang initialworldstate [todraw stateascoloredsquare] [onkey findnextstate])))
a world state is just a finitestate machine state;
the transition table of fsm0 is like a constant with respect to the locally defined functions even though it is extracted from the given fsm0;
the key event handler and the rendering function consume only a SimulationState not the entire FSM;
but they may access fsm0’s transition table anyway if needed.
18.4 Using Abstractions, By Examples
Sample Problem: Design the function add3toall. The function consumes a list of Posns and adds 3 to the x coordinates of each of them.
; [Listof Posn] > [Listof Posn] ; add 3 to each x coordinate on the given list (checkexpect (add3toall (list (makeposn 30 10) (makeposn 0 0))) (list (makeposn 33 10) (makeposn 3 0))) (define (add3toall lop) empty)
At this point, we stop and ask what kind of function we are dealing with. Clearly, add3toall is clearly a listprocessing function. The question is whether it is like any of the functions in figure 53. The signature tells us that add3toall is a listprocessing function that consumes and produces a list. In figure 53, we have several functions with similar signatures: map, filter, and sort.
The purpose statement and example also tell you that add3toall
deals with each Posn separately and assembles the results into a
single list. Some reflection says that also confirms that the resulting
list contains as many elements as the given list. All this thinking points
to one function—
; [Listof Posn] > [Listof Posn] ; add 3 to each x coordinate on the given list (checkexpect (add3toall (list (makeposn 30 10) (makeposn 0 0))) (list (makeposn 33 10) (makeposn 3 0))) (define (add3toall lop) (local (; Posn > Posn ; ... (define (afunfromposntoposn p) ... p ...)) (map afunfromposntoposn lop)))
(add3toall (list (makeposn 30 10) (makeposn 0 0))) = (map afun (list (makeposn 30 10) (makeposn 0 0))) = (list (afun (makeposn 30 10)) (afun (makeposn 0 0)))
; [Listof Posn] > [Listof Posn] ; add 3 to each x coordinate on the given list (checkexpect (add3toall (list (makeposn 30 10) (makeposn 0 0))) (list (makeposn 33 10) (makeposn 3 0))) (define (add3toall lop) (local (; Posn > Posn ; add 3 to the x coordinate of the given Posn (define (add3toone p) (makeposn (+ (posnx p) 3) (posny p)))) (map add3toone lop)))
Sample Problem: Design a function that eliminates all Posns from a list that have a y coordinate of larger than 100.
; [Listof Posn] > [Listof Posn] ; eliminates Posns whose y coordinate is larger than 100 (checkexpect (keepgood (list (makeposn 0 110) (makeposn 0 60))) (list (makeposn 0 60))) (define (keepgood lop) empty)
; [Listof Posn] > [Listof Posn] ; eliminates Posns whose y coordinate is larger than 100 (checkexpect (keepgood (list (makeposn 0 110) (makeposn 0 60))) (list (makeposn 0 60))) (define (keepgood lop) (local (; Posn > Boolean ; should this Posn stay? (define (good? p) true)) (filter good? lop)))
Before you read on, analyze the signature of filter and keepgood and determine why the helper function consumes individual Posns and produces Booleans.
; [Listof Posn] > [Listof Posn] ; eliminates Posns whose y coordinate is larger than 100 (checkexpect (keepgood (list (makeposn 0 110) (makeposn 0 60))) (list (makeposn 0 60))) (define (keepgood lop) (local (; Posn > Posn ; should this Posn stay? (define (good? p) (not (> (posny p) 100)))) (filter good? lop)))
Sample Problem: Design a function that determines whether any of a list of Posns is close to some given position pt where “close” means a distance of at most 5 pixels.
; Posn Posn Number > Boolean ; is the distance between p and q less than d? (define (closeto p q d) ...)
; [Listof Posn] Posn > Boolean ; is any Posn on lop close to pt? (checkexpect (close? (list (makeposn 47 54) (makeposn 0 60)) (makeposn 50 50)) true) (define (close? lop pt) false)
The Boolean range also gives away a clue with respect to
figure 53. Only two functions in this list produce
Boolean values—
; [Listof Posn] Posn > Boolean (define (close? lop pt) (local (; Posn > Boolean ; ... (define (isoneclose? p) ...)) (ormap closeto? lop)))
; [Listof Posn] > Boolean (define (close? lop pt) (local (; Posn > Boolean ; is one shot close to pt? (define (isoneclose? p) (closeto p pt CLOSENESS))) (ormap isoneclose? lop))) (define CLOSENESS 5)
18.5 Designing With Abstractions
Step 1 is to follow the design recipe for functions for three steps. Specifically, you should distill the problem statement into a signature, a purpose statement, an example, and a stub definition.
Consider the problem of defining a function that places small red circles on a 200 by 200 canvas for a given list of Posns. The first three steps design recipe yield this much:; [Listof Posn] > Image ; add the Posns on lop to the empty scene (checkexpect (dots (list (makeposn 12 31))) (placeimage DOT 12 32 BACKGROUND)) (define (dots lop) BACKGROUND) (define BACKGROUND (emptyscene 200 200)) (define DOT (circle 5 "solid" "red")) Next we exploit the signature and purpose statement to find a matching abstraction. To match means to pick an abstraction whose purpose is more general than the one for the function to be designed; it also means that the signatures are related. It is often best to start with the desired output and to find an abstraction that has the same or a more general output.
For our running example, the desired output is an Image. While none of the available abstractions produces an image, two of them have a variable to the right of >:Write down a template. For the reuse of abstractions a template uses local for two different purposes. The first one is to note which abstraction to use and how in the body of the local expression. The second one is to write down a stub for the helper function: its signature, its purpose (optionally), and its header. Keep in mind that the signature comparison in the preceding step suggests most of the signature for the auxiliary function.
Here is what this template looks like for our running example if we choose foldr:Finally, it is time to define the helper function inside local. In most cases, this auxiliary function consumes relatively simple kinds of data, like those encountered in FixedSize Data. You know how to design those in principle. The only difference is that now you may not only use the function’s arguments and global constants but also the arguments of the surrounding function.
In our running example, the purpose of the helper function is to add one dot to the given scene, which you can (1) guess or (2) derive from the example:The last step is to test the definition in the usual manner.
For abstract functions, it is occasionally possible to use the abstract example of their purpose statement to confirm their workings at a more general level. You may wish to use the abstract example for foldr to confirm that dots does add one dot after another to the background scene.
18.6 Exercises And Projects
Each of the following set of exercises suggests small practice problems for specific abstractions in ISL.
Exercise 220. Use map to define the function converteuro, which converts a list of U.S. dollar amounts into a list of euro amounts based on an exchange rate of 1.22 euro for each dollar.
Also use map to define convertFC, which converts a list of Fahrenheit measurements to a list of Celsius measurements.
Finally, try your hands at translate, a function that translates a list of Posns into a list of list of pairs of numbers, i.e., [Listof [list Number Number]].
Exercise 221. A toy structure specifies the name of a toy, a description, the acquisition price, and the recommended sales price.
Define a function that sorts a list of toy structures by the difference between the two prices.
Exercise 222. Define eliminateexp, which consumes a number, ua and a list of toy structures, and it produces a list of all those structures whose sales price is below ua.
Then use filter to define recall, which consumes the name of a toy, called ty, and a list of toy structures and which produces a list of toy structures that do not use the name ty.
In addition, define selection, which consumes two lists of names and selects all those from the second one that are also on the first.
creates the list 0 ... (n  1) for any natural number n;
creates the list 1 ... nfor any natural number n;
creates the list (list 1 1/10 1/100 ...) of n numbers for any natural number n;
creates the list of the first n even numbers;
creates a list of lists of 0 and 1 in a diagonal arrangement, e.g.,
(equal? (diagonal 3) (list (list 1 0 0) (list 0 1 0) (list 0 0 1)))
Exercise 224. Use ormap to define findname. The function consumes a name and a list of names. It determines whether any of the names on the latter are equal to or an extension of the former.
With andmap you can define a function that checks all names on a list of names start with the letter "a".
Should you use ormap or andmap to define a function that ensures that no name on some list exceeds some given width?
Exercise 225. Recall that the append function in ISL juxtaposes the items of two lists or, equivalently, replaces empty at the end of the first list with the second list:Now use one of the fold functions to define functions that compute the sum and the product, respectively, of a list of numbers.
With one of the fold functions, you can define a function that horizontally juxtaposes a list of Images. Hint: look up beside and emptyimage. Can you use the other fold function? Also define a function that stacks a list of images vertically. Hint: check for above in the libraries.
Exercise 226. The fold functions are so powerful that you can define almost any listprocessing functions with them. Use fold to define mapfromfold, which simulates map.
Now that you have some experience with the existing listprocessing abstractions in ISL, it is time to tackle some real projects. Specifically, we are looking for two kinds of improvements. First, inspect the game programs for functions that traverse lists. For these functions, you already have signatures, purpose statements, tests, and working definitions that pass the tests. Change the definitions to use abstractions from figure 53. Second, also inspect the game programs for opportunities to abstract. Indeed, you might be able to abstract across games and provide a framework of functions that helps you write additional game programs. The following exercises supply specific suggestions for the projects mentioned in this book. If you are using this book for a course, you may have had to deal with other nontrivial exercises; adapt the exercises to those projects.
Exercise 227. Full Space War spells out a game of space war. In the basic version, a UFO descends and a player defends with a tank. One additional suggestion is to equip the UFO with charges that it can drop at the tank; the tank is destroyed if a charge comes close enough.
Inspect the code of your project for places where it can benefit from existing abstraction, e.g., processing lists of shots or charges.
Once you have simplified the code with the use of existing abstractions look for opportunities to create abstractions. Consider moving lists of objects as one example where abstraction may pay off.
Exercise 228. Feeding Worms explains how another one of the oldest computer games work. The game features a worm that moves at a constant speed in a playercontrolled direction. When it encounters food, it eats the food and grows. When it runs into the wall or into itself, the game is over.
This project can also benefit from the abstract listprocessing in ISL. Look for places to use them and replace existing code one piece at a time, relying on the tests to ensure the program works.
19 Nameless Functions
; [Listof IR] String > Boolean (define (find aloir threshold) (local (; IR > Boolean (define (acceptable? ir) (<= (irprice ir) threshold))) (filter acceptable? aloir)))
This situation calls for an improvement to the language. Programmers should be able to create such small and insignificant functions without much effort. In DrRacket, choose “Intermediate Student Language with lambda” from the “How to Design Programs” submenu in the “Language” menu. This section presents lambda, the new feature, and introduces “Intermediate Student Language with lambda.” This language, short: ISL+, is an extension of ISL with lambda. The history of lambda is interesting and intimately involved with the early history of programming and programming language design. When you have time, you should chase down the origins of lambda.
The first two subsections focus on the design of abstractions using lambda. The remaining sections use lambda and local to introduce some basic programming language concepts, namely, scope and abbreviations. In addition, they indicate with one use of lambda that the idea of functions as values has additional ramifications for program design.
19.1 Functions From lambda
(lambda (x) (expt 10 x)), which assumes that the argument is a number and computes the exponent of 10 to the number;
(lambda (name) (stringappend "hello, " name ", how are you?")), which consumes a string and creates a greeting with stringappend; and
(lambda (ir) (<= (irprice ir) threshold)), which is a function on an IR struct that extracts the price field from the structure and compares it with some threshold value.
((lambda (x1 ... xn) exp) val1 ... valn) = exp ; with free occurrences of x1 replaced by val1, etc.
> ((lambda (x) (expt 10 x)) 2) 100
> ((lambda (name rst) (stringappend name ", " rst)) "Robby" "etc.") "Robby, etc."
> ((lambda (ir) (<= (irprice ir) threshold)) (makeir "bear" 10)) true
(define threshold 20)
> (map (lambda (x) (expt 10 x)) '(1 2 3)) (list 10 100 1000)
> (foldl (lambda (name rst) (stringappend name ", " rst)) "etc." '("Matthew" "Robby")) "Robby, Matthew, etc."
> (filter (lambda (ir) (<= (irprice ir) threshold)) (list (makeir "bear" 10) (makeir "doll" 33))) (list (ir ...))
Explain why they are legal or illegal. If in doubt, experiment in the interactions area.
Check your results in DrRacket.
consumes a number and decides whether it is less than 10;
consumes two numbers, multiplies them, and turns the result into a string;
consumes an Posn p and a rectangular Image and adds a red 3pixel dot to the image at p;
consumes an inventory record and compares them by price; and
consumes a natural number and produces 0 if it is even and 1 if it is odd.
Demonstrate how to use these functions in the interactions area.
19.2 Abstracting With lambda I
; [Listof IR] String > Boolean ; VERSION 2 (define (find aloir threshold) (filter (lambda (ir) (<= (irprice ir) threshold)) aloir))
(define (dots lop) (local (; Posn Image > Image (define (addonedot p scene) ...)) (foldr addonedot BACKGROUND lop)))
(define (dots lop) (foldr (lambda (oneposn scene) (placeimage DOT (posnx oneposn) (posny oneposn) scene)) BACKGROUND lop))
 and the third one determines whether any Posn on lop is close to some given point:
The following exercises request that you solve the problems from Exercises And Projects with lambda in ISL+ .
Exercise 232. Use map to define the function converteuro, which converts a list of U.S. dollar amounts into a list of euro amounts based on an exchange rate of 1.22 euro for each dollar.
Also use map to define convertFC, which converts a list of Fahrenheit measurements to a list of Celsius measurements.
Finally, try your hands at translate, a function that translates a list of Posns into a list of list of pairs of numbers, i.e., [Listof [list Number Number]].
Exercise 233. A toy structure specifies the name of a toy, a description, the acquisition price, and the recommended sales price.
Define a function that sorts a list of toy structures by the difference between the two prices.
Exercise 234. Use filter to define eliminateexp. The function consumes a number, ua and a list of toy structures (containing name and price), and it produces a list of all those structures whose acquisition price is below ua.
Then use filter to define recall, which consumes the name of a toy, called ty, and a list of toy structures and which produces a list of toy structures that do not use the name ty.
In addition, define selection, which consumes two lists of names and selects all those from the second one that are also on the first.
creates the list 0 ... (n  1) for any natural number n;
creates the list 1 ... nfor any natural number n;
creates the list (list 1 1/10 1/100 ...) of n numbers for any natural number n;
creates the list of the first n even numbers;
creates a list of lists of 0 and 1 in a diagonal arrangement, e.g.,
(equal? (diagonal 3) (list (list 1 0 0) (list 0 1 0) (list 0 0 1)))
Exercise 236. Use ormap to define findname. The function consumes a name and a list of names. It determines whether any of the names on the latter are equal to or an extension of the former.
With andmap you can define a function that checks all names on a list of names start with the letter "a".
Should you use ormap or andmap to define a function that ensures that no name on some list exceeds some given width?
Exercise 237. Recall that the append function in ISL juxtaposes the items of two lists or, equivalently, replaces empty at the end of the first list with the second list:Now use one of the fold functions to define functions that compute the sum and the product, respectively, of a list of numbers.
With one of the fold functions, you can define a function that horizontally juxtaposes a list of Images. Hint: look up beside and emptyimage. Can you use the other fold function? Also define a function that stacks a list of images vertically. Hint: check for above in the libraries.
Exercise 238. The fold functions are so powerful that you can define almost any listprocessing functions with them. Use fold to define mapfromfold, which simulates map.
19.3 lambda, Technically
What this means is that lambda creates a function without a name,
an anonymous function. This function is a value like any other value. The
name of the function is irrelevant. The only interesting parts are the
function parameters—
This insight is also the missing piece that connects constant definitions and function definitions. Instead of viewing function definitions as given, we can take lambdas as the primitive concept and say that a function definition abbreviates a plain constant definition with a lambda expression on the righthand side.
(compare (random 100000))
19.4 Abstracting With lambda II
Because functions are firstclass values in ISL+, we may think of them as another form of data and use them for data representation. This section provides a taste of this idea; the next few chapters do not rely on it. Its title uses “abstracting” because people consider functional data representation abstract.
Sample Problem: Navy strategists represents fleets of ships as rectangles (the ship itself) and circles (their reach). The coverage of a fleet of ships is the combination of all these shapes. Design a data representation for rectangles, circles, and combinations of shapes. Then design a function that determines whether some point is within a shape.
One mathematical approach considers shapes as sets of points. In turn, a set is a predicate on points, that is, a function that maps a position to Boolean. One particular advantage is that this representation allows the inclusion of infinitely large shapes though we don’t exploit this possibility here.
; Shape is a function: ; [Posn > Boolean] ; interpretation: ; if s is a shape and p a Posn, ; (s p) is true if the Posn is inside the shape ; and true if the Posn is outside
; Number Number Number > Shape ; create a data representation for a circle of radius r ; located at (centerx, centery) (define (makecircle centerx centery r) ; Posn > Boolean (lambda (p) (<= (distancebetween centerx centery p) r)))
; Number Number Number Number > Shape ; create a data representation of a rectangle (define (makerectangle upperleftx upperlefty width height) ; Posn > Boolean (lambda (p) (and (between upperleftx (posnx p) width) (between ( upperlefty height) (posny p) height))))
Exercise 239. Design the function distancebetween. It consumes two numbers and a Posn: x, y, and p. The function computes the distance between the points (x, y) and p. Hint: the distance between (x0,y0) and (x1,y1) isi.e., the distance of (x0  y0,x1  y1) to the origin.
Exercise 240. Design the function between. It consumes three numbers: left, x, and width. The function produces true if x is between left and (+ left width) inclusive.
> circle1 circle1
> rectangle1 rectangle1
Exercise 241. Draw the shapes represented by circle1 and rectangle1 on grid paper. Check that the origin belongs to both.
(checkexpect (shapeinside? circle1 (makeposn 0 1)) false) (checkexpect (shapeinside? circle1 (makeposn 1 3)) true) (checkexpect (shapeinside? rectangle1 (makeposn 0 1)) false) (checkexpect (shapeinside? rectangle1 (makeposn 1 3)) false)
Exercise 242. Confirm these tests with the drawing from exercise 241.
; Shape Shape > Shape ; combine two shapes into one (define (makecombination s1 s2) ; Posn > Boolean (lambda (p) false))
(define combination1 (makecombination circle1 rectangle1))
(checkexpect (shapeinside? union1 (makeposn 0 0)) true) (checkexpect (shapeinside? union1 (makeposn 0 1)) false) (checkexpect (shapeinside? union1 (makeposn 1 3)) true)
; Shape Shape > Shape (define (makecombination s1 s2) ; Posn > Boolean (lambda (p) (or (inside? s1 p) (inside? s2 p))))
; Shape = [Posn > Boolean] ; Shape Posn > Boolean (define (shapeinside? s p) (s p)) ; Number Number Number > Shape (define (makecircle centerx centery r) (lambda (p) (local (; Number Number Posn > Boolean (define (distancebetween x y p) (sqrt (+ (sqr ( x (posnx p))) (sqr ( y (posny p))))))) ; — IN — (<= (distancebetween centerx centery p) r)))) ; Number Number Number Number > Shape (define (makerectangle northwestx northwesty width height) (lambda (p) (local (; Number Number Number > Boolean ; is z between left and (+ left interval) (define (between left z interval) (<= left z (+ left interval)))) ; — IN — (and (between northwestx (posnx p) width) (between ( northwesty height) (posny p) height))))) ; Shape Shape > Shape (define (makecombination s1 s2) (lambda (x) (or (shapeinside? s1 x) (shapeinside? s2 x))))
; — examples (define circle1 (makecircle 3 4 5)) (define rectangle1 (makerectangle 0 3 10 3)) (define union1 (makecombination circle1 rectangle1)) ; — tests (checkexpect (shapeinside? circle1 (makeposn 0 0)) true) (checkexpect (shapeinside? circle1 (makeposn 0 1)) false) (checkexpect (shapeinside? circle1 (makeposn 1 3)) true) (checkexpect (shapeinside? rectangle1 (makeposn 0 0)) true) (checkexpect (shapeinside? rectangle1 (makeposn 0 1)) false) (checkexpect (shapeinside? rectangle1 (makeposn 1 3)) false) (checkexpect (shapeinside? union1 (makeposn 0 0)) true) (checkexpect (shapeinside? union1 (makeposn 0 1)) false) (checkexpect (shapeinside? union1 (makeposn 1 3)) true) Figure 58: A functional representation of geometric shapes, examples
Figure 57 collects all the program fragments into one complete program; figure 58 supplements it with a test suite. Copy and paste all the code into DrRacket and experiment. Most importantly, confirm that all tests pass.
Exercise 243. Design a data representation for finite and infinite sets so that you can represent the sets of all odd numbers, all even numbers, all numbers divisible by 10, etc. Hint: Mathematicians sometimes interpret sets as functions that consume a potential element e and produce true if the e belongs to the set and false if it doesn’t.
Design the functions
addelement, which adds an element to a set;
union, which combines the elements of two sets; and
intersect, which collects all elements common to two sets;
Keep in mind the analogy between sets and shapes.
20 Summary
This third part of the book is about the role of abstraction in program design. Abstraction has two sides: creation and use. It is therefore natural if we summarize the chapter as two lessons:
Repeated code patterns call for abstraction. To abstract means to factor out the repeated pieces of code—
the abstraction— and to parameterize over the differences. With the design of proper abstractions, programmers save themselves future work and headaches because mistakes, inefficiencies, and other problems are all in one place. One fix to the abstraction can thus improve all uses. In contrast, the duplication of code means that a programmer must find all copies and fix all of them when a problem is found. Most languages come with a large collection of abstractions. Some are contributions by the language design and implementation team; others are added by programmers who used the language. To enable effective reuse of these abstractions, their creators must supply the appropriate pieces of documentation: a purpose statement, a signature, and good examples. These pieces should suffice to help programmers figure out how to use the abstraction.
the idea of functions as data and their role in representing information as data.