Section 3.2.7, second paragraph: The sentence "If the written
representation of a number has no exactness prefix, the constant may be
either inexact or exact" connotes that the implementation has a choice,
whereas in fact it does not. Dropping the words "may be either inexact
or exact. It" states the true position clearly and concisely.
Section 9.17, s.v. "values": the final words "is undefined" need a
space before them.
Section 9.17, s.v. "call-with-values" speaks of calling the producer
with no values rather than no arguments. This is correct but obfuscatory.
Section 9.18, s.v. "do": For "A do expression are evaluated" read "A
do expression is evaluated". The name "<expressionx>" is lame, and is
not used in the explanation anyway, which leaves it up to the reader to
decide that the <expression>s in the fourth paragraph are those of the
(pseudo-)body, whereas the <expression>s in the fifth paragraph are
those following the text.
--
And through this revolting graveyard of the universe the muffled, maddening
beating of drums, and thin, monotonous whine of blasphemous flutes from
inconceivable, unlighted chambers beyond Time; the detestable pounding
and piping whereunto dance slowly, awkwardly, and absurdly the gigantic
tenebrous ultimate gods -- the blind, voiceless, mindless gargoyles whose soul
is Nyarlathotep. (Lovecraft) John Cowan|cowan_at_ccil.org|ccil.org/~cowan
Received on Sat Jan 20 2007 - 13:14:01 UTC