56 lines
1.7 KiB
Racket
56 lines
1.7 KiB
Racket
#lang scribble/doc
|
|
@(require "mz.ss")
|
|
|
|
@title[#:tag "load-lang"]{The @schememodname[scheme/load] Language}
|
|
|
|
@defmodulelang[scheme/load]
|
|
|
|
The @scheme[scheme/load] language supports traditional Scheme
|
|
evaluation, where each top-level form in the module body is separately
|
|
passed to @scheme[eval] in the same way as for @scheme[load]. The
|
|
namespace for evaluation shares the @tech{module registry} with the
|
|
enclosing module, but it has a separate top-level environment, and it is
|
|
initialized with the bindings of @schememodname[scheme]. The
|
|
@scheme[scheme/load] library itself exports only
|
|
@schemeidfont{#%module-begin} and @schemeidfont{#%top-interaction}
|
|
forms that effectively swap in the evaluation namespace and call
|
|
@scheme[eval].
|
|
|
|
For example, the body of a module using @scheme[scheme/load] can
|
|
include @scheme[module] forms, so that running the following module
|
|
prints @schemeresultfont{5}:
|
|
|
|
@schememod[
|
|
scheme/load
|
|
|
|
(module m scheme/base
|
|
(provide x)
|
|
(define x 5))
|
|
|
|
(module n scheme/base
|
|
(require 'm)
|
|
(display x))
|
|
|
|
(require 'n)
|
|
]
|
|
|
|
Definitions in a module using @scheme[scheme/load] are evaluated in
|
|
the current namespace, which means that @scheme[load] and
|
|
@scheme[eval] can see the definitions. For example, running the
|
|
following module prints @schemeresultfont{6}:
|
|
|
|
@schememod[
|
|
scheme/load
|
|
|
|
(define x 6)
|
|
(display (eval 'x))
|
|
]
|
|
|
|
Since all forms within a @schememodname[scheme/load] module are
|
|
evaluated in the top level, bindings cannot be exported from the
|
|
module using @scheme[provide]. Similarly, since evaluation of the
|
|
module-body forms is inherently dynamic, compilation of the module
|
|
provides essentially no benefit. For these reasons, use
|
|
@schememodname[scheme/load] for interactive exploration of top-level
|
|
forms only, and not for constructing larger programs.
|