|
|
@@ -25,7 +25,7 @@
|
|
|
|
|
|
\def\racketEd{0}
|
|
|
\def\pythonEd{1}
|
|
|
-\def\edition{1}
|
|
|
+\def\edition{0}
|
|
|
|
|
|
% material that is specific to the Racket edition of the book
|
|
|
\newcommand{\racket}[1]{{\if\edition\racketEd{#1}\fi}}
|
|
|
@@ -16317,7 +16317,7 @@ Furthermore, even when primitive operations restrict their inputs to
|
|
|
values of a certain type, this restriction is enforced at runtime
|
|
|
instead of during compilation. For example, the tuple read
|
|
|
operation
|
|
|
-\racket{\code{(vector-ref #t 0)}}
|
|
|
+\racket{\code{(vector-ref \#t 0)}}
|
|
|
\python{\code{True[0]}}
|
|
|
results in a run-time error because the first argument must
|
|
|
be a tuple, not a Boolean.
|
Jeremy Siek