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

doc: more notes on dynamic-require examples

Browse Source 
Suggested by Shriram.
This commit is contained in:
Matthew Flatt 2020-05-25 07:49:15 -06:00
parent 83d9e56296
commit e4485d1e11
1 changed files with 10 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
pkgs/racket-doc/scribblings/reference/module-reflect.scrbl
View File

@ -544,10 +544,16 @@ above the @tech{base phase}.
(dynamic-require ''a #f) (dynamic-require ''a #f)
] ]
@margin-note{The double quoted @racket[''a] evaluates to the @racket[root-module-path] @racket['a] @margin-note{The double quoted @racket[''a] evaluates to the @racket[_root-module-path] @racket['a]
(see the grammar for @racket[require]). Using @racket['a] or @racket[a] for @racket[mod] won't work (see the grammar for @racket[require]). Using @racket['a] for @racket[mod] won't work,
because the former evaluates to @racket[root-module-path] @racket[a] which fails since the example is because that evaluates to @racket[_root-module-path] @racket[a], and the example is
not a module installed in a collection, the latter is an undefined variable.} not a module installed in a collection. Using @racket[a] won't work, because @racket[a]
is an undefined variable.
Declaring @racket[(module a ....)] within another module, instead of in
the @racket[read-eval-print] loop, would create a submodule. In that case,
@racket[(dynamic-require ''a #f)] would not access the module, because @racket[''a]
does not refer to a submodule.}
When @racket[provided] is a symbol, the value of the module's export When @racket[provided] is a symbol, the value of the module's export
with the given name is returned, and still the module is not with the given name is returned, and still the module is not