Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Adds back missing refs to 5.4.1 and 5.5.6 #269

Merged
merged 1 commit into from
Jun 26, 2020
Merged

Adds back missing refs to 5.4.1 and 5.5.6 #269

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 1 addition & 4 deletions xml/chapter4/section1/subsection2.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -651,14 +651,11 @@ cond_expr_alt(my_cond_expr);
selectors for a list of statements<EMDASH/>and the corresponding
ones for a list of operands<EMDASH/>are not intended
as a data abstraction.
<!-- They are introduced as mnemonic names for the
They are introduced as mnemonic names for the
basic list operations in order to make it easier to understand the
explicit-control evaluator in
section<SPACE/><REF NAME="sec:eceval"/>.
<LABEL NAME="foot:mceval-abstraction"/>
-->
<!-- FIXME: include the commented-out part once
Chapter 5.4.1 is adapted to JavaScript -->
</FOOTNOTE>
<SNIPPET PAGE="371">
<NAME>begin</NAME>
Expand Down
9 changes: 0 additions & 9 deletions xml/chapter4/section1/subsection3.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -808,17 +808,8 @@ evaluate(my_block, the_global_environment);
<INDEX>deep binding</INDEX><INDEX>binding<SUBINDEX>deep</SUBINDEX></INDEX>
(Such an approach is referred to as <EM>deep binding</EM>.) One way to avoid
this inefficiency is to make use of a strategy called
<SPLIT>
<SCHEME>
<EM>lexical addressing</EM>, which will be discussed in
section<SPACE/><REF NAME="sec:lexical-addressing"/>.
</SCHEME>
<JAVASCRIPT>
<EM>lexical addressing</EM>.
<!-- FIXME: remove split and replace with Scheme version once
Chapter 5.5.6 is adapted to JavaScript -->
</JAVASCRIPT>
</SPLIT>
</FOOTNOTE>
<INDEX>metacircular evaluator for Scheme
<SUBINDEX>representation of environments|)</SUBINDEX></INDEX>
Expand Down
11 changes: 2 additions & 9 deletions xml/chapter4/section1/subsection7.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -337,18 +337,11 @@ function analyze_self_evaluating(stmt) {
</JAVASCRIPT>
</SPLITINLINE>
that <EM>can</EM> be done as part of the syntactic analysis.
<SPLIT>
<SCHEME>
As we will show in section<SPACE/><REF NAME="sec:lexical-addressing"/>,
As we will show in section<SPACE/><REF NAME="sec:lexical-addressing"/>,
one can determine the position in the environment structure where the
value of the variable will be found, thus obviating the need to scan the
environment for the entry that matches the variable.
</SCHEME>
<JAVASCRIPT>
<!-- FIXME: remove split and replace with scheme text once
Chapter 5.5.6 is adapted to JavaScript -->
</JAVASCRIPT>
</SPLIT></FOOTNOTE>
</FOOTNOTE>
<SNIPPET HIDE="yes">
<NAME>analyze_variable_example</NAME>
<REQUIRES>functions_4_1_2</REQUIRES>
Expand Down
11 changes: 1 addition & 10 deletions xml/chapter4/section2/subsection2.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -813,17 +813,8 @@ function thunk_env(thunk) {
<INDEX>garbage collection<SUBINDEX>memoization and</SUBINDEX></INDEX>
<INDEX>memoization<SUBINDEX>garbage collection and</SUBINDEX></INDEX>
<EM>garbage-collected</EM> and its space
<SPLITINLINE>
<SCHEME>
recycled, as we will discuss in
section<SPACE/><REF NAME="sec:storage-allocation"/>.
</SCHEME>
<JAVASCRIPT>
recycled.
<!-- FIXME: remove split and replace with Scheme text once
Chapter 5.3.3 is adapted to JavaScript -->
</JAVASCRIPT>
</SPLITINLINE>
section<SPACE/><REF NAME="sec:storage-allocation"/>.
Similarly, we could have allowed unneeded environments in the memoized
delayed objects of section<SPACE/><REF NAME="sec:delayed-lists"/>
to be garbage-collected, by having
Expand Down