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

clarify that unbound = top-level binding in reference

Browse Source 
svn: r12226
This commit is contained in:
Matthew Flatt 2008-11-03 16:18:16 +00:00
parent b8f6e1a91a
commit 3a433f4ae4
2 changed files with 17 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
collects/scribblings/reference/stx-comp.scrbl
View File

@ -21,9 +21,10 @@ suitable expression context at the @tech{phase level} indicated by
boolean?]{ boolean?]{
Returns @scheme[#t] if @scheme[a-id] and @scheme[b-id] access the same Returns @scheme[#t] if @scheme[a-id] and @scheme[b-id] access the same
lexical, module, or top-level binding at the @tech{phase level} @tech{local binding}, @tech{module binding}, or @tech{top-level
indicated by @scheme[phase-level]. A @scheme[#f] value for binding} at the @tech{phase level} indicated by
@scheme[phase-level] corresponds to the @tech{label phase level}. @scheme[phase-level]. A @scheme[#f] value for @scheme[phase-level]
corresponds to the @tech{label phase level}.
``Same module binding'' means that the identifiers refer to the same ``Same module binding'' means that the identifiers refer to the same
original definition site, not necessarily the @scheme[require] or original definition site, not necessarily the @scheme[require] or
@ -127,8 +128,9 @@ Returns one of three kinds of values, depending on the binding of
}} }}
@item{The result is @scheme[#f] if @scheme[id-stx] @item{The result is @scheme[#f] if @scheme[id-stx] has a
has a @tech{top-level binding}.} @tech{top-level binding} (or, equivalently, if it is
@tech{unbound}).}
}} }}

13
collects/scribblings/reference/syntax-model.scrbl
View File

@ -48,10 +48,7 @@ form is the set of bindings whose @tech{scope} includes the form. A
binding for a sub-expression @deftech{shadows} any @tech{bindings} binding for a sub-expression @deftech{shadows} any @tech{bindings}
(i.e., it is @deftech{shadowing}) in its @tech{environment}, so that (i.e., it is @deftech{shadowing}) in its @tech{environment}, so that
uses of an @tech{identifier} refer to the @tech{shadowing} uses of an @tech{identifier} refer to the @tech{shadowing}
@tech{binding}. A @deftech{top-level binding} is a @tech{binding} @tech{binding}.
from a definition at the top-level; a @deftech{module binding} is a
binding from a definition in a module; and a @deftech{local binding}
is another other kind of binding.
For example, as a bit of source, the text For example, as a bit of source, the text
@ -63,6 +60,14 @@ appears twice). When this source is parsed in a typical
@tech{variable} (unlike @scheme[let]). In particular, the first @tech{variable} (unlike @scheme[let]). In particular, the first
@scheme[x] @tech{binds} the second @scheme[x]. @scheme[x] @tech{binds} the second @scheme[x].
A @deftech{top-level binding} is a @tech{binding} from a definition at
the top-level; a @deftech{module binding} is a binding from a
definition in a module; and a @deftech{local binding} is another other
kind of binding. There is no difference between an @deftech{unbound}
identifier and one with a @tech{top-level binding}; within a module,
references to @tech{top-level bindings} are disallowed, and so such
identifiers are called @tech{unbound} in a module context.
Throughout the documentation, @tech{identifiers} are typeset to Throughout the documentation, @tech{identifiers} are typeset to
suggest the way that they are parsed. A black, boldface suggest the way that they are parsed. A black, boldface
@tech{identifier} like @scheme[lambda] indicates as a reference to a @tech{identifier} like @scheme[lambda] indicates as a reference to a