CSUG8 Errata
March 2010 Printing for Version 8.0
Page 10 (reported by Jamie Taylor): In the last sentence of the third paragraph, no period should appear after "command-line option" and before "to invoke debug directly."
Page 74, 75 (reported by Jamie Taylor): The argument to Senable_expeditor should be history_file rather than historyfile.
Page 77 (reported by the author): In the description of the C-interface string operations, the text
The sequence is always followed by a null byte for convenience in interfacing with C. The trailing null byte is not counted in determining the length of the string.
should be eliminated.
Page 116 (reported by Jamie Taylor): The values given for s2 in the three string-copy! examples should be, in order, "-bol------", "-bolly----", and "-bollolly-".
Page 184 (reported by the author): The second occurrence of the port-length prototype should be replaced with an identical one for file-length.
Page 184, 186 (reported by Jamie Taylor): In the descriptions of port-length, set-port-length!, and file-position, "232" should read "232."
Page 186 (reported by Chris Payne): In the description of file-position, "232" should read "232."
Page 200 (reported by Bob Burger): In the prototypes for put-bytevector-some, the first argument should be listed as a binary-output-port rather than a textual-output-port.
Page 218 (reported by Jamie Taylor): The description of directory-list refers to delete-directory where it should refer to directory-list.
Page 240 (reported by Chris Payne): In the sentence that begins with "The list of exports", "library-export" should be "library-exports."
Page 246 (reported by Jamie Taylor): In the description of syntax->list, the word "are" should not appear in the phrase "from individual are pattern variable values." The same is true for the similar phrase in the description of syntax->vector.
Page 277 (reported by Jamie Taylor): The examples for ieee-environment should invoke ieee-environment, not scheme-environment.
Page 277, 278 (reported by the author): In the examples for scheme-environment and ieee-environment, (set! cons 3) should be (define cons 3). The same is true for the first set of examples in the description of interaction-environment,
Page 279 (reported by Jamie Taylor): In the description of revert-interaction-semantics, the final assignment to cons in the first block of example code should not be shown to cause an exception, since it does not.
Page 288 (reported by Jamie Taylor): In the description of expand/optimize, the phrase "through a letrec the source optimizer" should read "through the source optimizer."
Page 289 (reported by Jamie Taylor): At the end of the fifth paragraph of the description of eval-when, the phrase "the following definitions for and" should read "the following definitions for nodups? and mvlet."
Page 291 (reported by Jamie Taylor): At the end of the description of the load eval-when situation, the extraneous words "subsequently loaded" should not appear.
Page 293 (reported by Jamie Taylor): In the fourth-to-last paragraph of the description of eval-when, the single quotation mark in front of "V" in the fourth line should be a double quotation mark.
Page 294 (reported by Chris Payne): In the description of alias, the last example and the text before it is incorrect for Version 8 and beyond. Aliases now transfer the current binding from the old identifier to the new, so the new identifier does not track changes to the binding of the old identifier.
Page 310 (reported by Jamie Taylor): The descriptions of command-line and command-line-arguments should say that the default value of scheme-program sets the parameters when the --program option is used, just as the default value of scheme-script does when the --script argument is used.
Page 316 (reported by Bob Burger): The description of time-utc->date should document the optional second argument, offset, which serves the same purpose as the optional offset argument to current-date.
Page 336 (reported by Jamie Taylor): In the description of ee-paren-flash-delay, "It's default value is #t" should read "It's default value is 100."
Page 339 (reported by Jamie Taylor): In the description of ee-next-line, the terminating phrase "behaves like" should read "behaves like ee-history-fwd." Similarly, in the description of ee-previous-line, "behaves like" should read "behaves like ee-history-bwd."
Page 382 (reported by the author): The prototype for port-length should replaced with an identical one for file-length.
Page 394 (reported by Bob Burger): In the prototypes for put-bytevector-some, the first argument should be listed as a binary-output-port rather than a textual-output-port.
May 2011 Printing for Version 8.2
Page 365 (reported by Ramana Kumar): In the second sentence, "features of the thread" should read "features of the thread system."