suzanne.soy/racket
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

doc: small adjustments to "eval-model.scrbl"

Browse Source
This commit is contained in:
Matthew Flatt 2018-11-14 10:44:58 -07:00 committed by Matthew Flatt
parent 19d096dde7
commit e745c047b0
1 changed files with 6 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
pkgs/racket-doc/scribblings/reference/eval-model.scrbl
View File

@ -179,7 +179,7 @@ Each evaluation step, then, transforms the current set of definitions and
program into a new set of definitions and program. Before a program into a new set of definitions and program. Before a
@racket[define] can be moved into the set of definitions, its @racket[define] can be moved into the set of definitions, its
expression (i.e., its right-hand side) must be reduced to a @tech{value}. expression (i.e., its right-hand side) must be reduced to a @tech{value}.
(The left-hand side is not evaluated.) (The left-hand side is not an expression position, and so it is not evaluated.)
@prog-steps/no-obj[ @prog-steps/no-obj[
[{} [{}
@ -414,8 +414,8 @@ changed, the value cannot be substituted for @racket[x] when
the procedure is first applied. the procedure is first applied.
@margin-note{We do not use the term ``parameter variable'' to refer to @margin-note{We do not use the term ``parameter variable'' to refer to
the parameter variable names declared with a function. This is to avoid the argument variable names declared with a function. This choice avoids
confusion with Parameters (see @secref["parameter-model"]).} confusion with @tech{parameters}.}
Instead, a new @deftech{location} is created for each @tech{variable} Instead, a new @deftech{location} is created for each @tech{variable}
on each application. The argument @tech{value} is placed in the on each application. The argument @tech{value} is placed in the
@ -556,9 +556,11 @@ module-specific prefix).
@;------------------------------------------------------------------------ @;------------------------------------------------------------------------
@subsection[#:tag "module-phase"]{Phases} @subsection[#:tag "module-phase"]{Phases}
@guidealso["phases"]
The purpose of @deftech{phases} is to The purpose of @deftech{phases} is to
address the necessary separation of names defined at execution time versus address the necessary separation of names defined at execution time versus
names defined at expansion time. See Section @secref["phases"] in the Guide. names defined at expansion time.
A module can be @tech{instantiate}d in multiple @tech{phases}. A A module can be @tech{instantiate}d in multiple @tech{phases}. A
phase is an integer that, like a module name, is effectively a prefix on the names phase is an integer that, like a module name, is effectively a prefix on the names