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

aother refinement to note on require sub-form expansion

Browse Source 
svn: r14239
This commit is contained in:
Matthew Flatt 2009-03-23 16:38:21 +00:00
parent f3a5008176
commit 31e1057128
1 changed files with 8 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
collects/scribblings/reference/syntax.scrbl
View File

@ -277,8 +277,7 @@ In a @tech{top-level context}, @scheme[require] instantiates modules
@scheme[require] @tech{visits} modules (see @secref["mod-parse"]). In @scheme[require] @tech{visits} modules (see @secref["mod-parse"]). In
both contexts, @scheme[require] introduces bindings into a both contexts, @scheme[require] introduces bindings into a
@tech{namespace} or a module (see @secref["intro-binding"]). @tech{namespace} or a module (see @secref["intro-binding"]).
A A @scheme[require] form in a @tech{expression context} or
@scheme[require] form in a @tech{expression context} or
@tech{internal-definition context} is a syntax error. @tech{internal-definition context} is a syntax error.
A @scheme[require-spec] designates a particular set of identifiers to A @scheme[require-spec] designates a particular set of identifiers to
@ -289,8 +288,11 @@ identifier. Each identifier also binds at a particular @tech{phase
level}. level}.
The syntax of @scheme[require-spec] can be extended via The syntax of @scheme[require-spec] can be extended via
@scheme[define-require-syntax], but the @scheme[define-require-syntax], and when multiple
pre-defined forms are as follows. @scheme[require-spec]s are specified in a @scheme[require], the
bindings of each @scheme[require-spec] are visible for expanding later
@scheme[require-spec]s. The pre-defined forms (as exported by
@scheme[scheme/base]) are as follows:
@specsubform[module-path]{ Imports all exported bindings from the @specsubform[module-path]{ Imports all exported bindings from the
named module, using the export identifiers as the local identifiers. named module, using the export identifiers as the local identifiers.
@ -432,9 +434,7 @@ pre-defined forms are as follows.
@specsubform[derived-require-spec]{See @scheme[define-require-syntax] @specsubform[derived-require-spec]{See @scheme[define-require-syntax]
for information on expanding the set of @scheme[require-spec] for information on expanding the set of @scheme[require-spec]
forms. When multiple @scheme[require-spec]s are specified in a forms.}
@scheme[require], the bindings of each @scheme[require-spec] are
visible for expanding later @scheme[require-spec]s.}
@guideintro["module-paths"]{module paths} @guideintro["module-paths"]{module paths}
@ -998,7 +998,7 @@ sets of imported identifiers.
#rx"-" (string-titlecase name) ""))) #rx"-" (string-titlecase name) "")))
scheme/base))] scheme/base))]
will get the @scheme[scheme/base] bindings that match the regexp, will get the @scheme[scheme/base] bindings that match the regexp,
and renamed to use ``camel case''.} and renamed to use ``camel case.''}
@; -------------------- @; --------------------