The information here currently corresponds with the version 5.0 of EdScheme for Windows; we will try to track new versions of EdScheme for Windows as they come out. Note also that EdScheme for the Macintosh is different enough that we have a separate web page for it.
error, from chapter 6 onward, as well as in the other two libraries. Another is the graphical images, introduced in the application section of chapter 1 and also used in subsequent chapters. The final one is the object-oriented programming system, used in chapter 14.
Each of these libraries can be downloaded from the web below. Once
you have them on your computer, you can add the pathname of the
directory (folder) where you have stored them to the list of
directories EdScheme looks in for files to load; this is specified in
the Interpreter section of the Options menu. Now you can load any of
the libraries in using the
load procedure. For example,
you could evaluate
(load "error.scm") to load in the
error library. However, you can also put these load commands into a
file, such as our example startup.scm
file, and use the Interpreter section of the Options menu to specify
that as a "startup" file, i.e., one that is automatically loaded every
time you start EdScheme for Windows. That way you will automatically
have full compatibility with the textbook.
error. Not only is this used from chapter 6 onward, it is also used in the other two libraries. Therefore, you must load this one if you load either of the other two. Important note: EdScheme for Windows comes with its own definition of
error, which is not compatible with the textbook. Therefore, if you don't load this library in, you will have more obscure symptoms than simply the procedure not being defined. The library file re-defines it in such a way as to be compatible with both the textbook's usage and the usage shown in the EdScheme documentation.
We list below the affected names, organized into categories and listed within each category in their order of their appearance within the book:
newlineprocedure to break output into separate lines. Unfortunately, there are two different conventions in use by different Scheme systems. One is to always use
newlineat the start of each line of output, while the other is to always use it at the end of each line. As a result of this lack of standardization, wherever we positioned the uses of
(newline)in our programs would result in output that looked odd on some systems. We've tried in the textbook to make choices that don't look too horrible on any system, with the result that the output tends to look sub-optimal on every system. In particular, there tends to be extra blank lines. If you are working consistently within EdScheme for Windows (or any other one system), feel free to remove or reposition
(newline)as necessary to make the output look best.
rcross-bb, are neither pre-defined nor defined within the library. Instead, their definitions are in a separate file.