A lot of "MzScheme" -> "Racket"s.

original commit: 2d9601089d1d127374238fdbe41a344ca88ca52f
This commit is contained in:
Eli Barzilay 2010-05-16 18:25:39 -04:00
parent 560ff92c71
commit ce035e3f8c
4 changed files with 9 additions and 9 deletions

View File

@ -361,7 +361,7 @@ The handler recognizes editor files by the first twelve characters of
insert-file], and then converting the editor content into a port with
@scheme[open-input-text-editor]. After obtaining a port in this way,
the content is read in essentially the same way as by the default
MzScheme load handler. The difference is that the editor may contain
Racket load handler. The difference is that the editor may contain
instances of @scheme[readable-snip<%>], which are ``read'' though the
snips' @method[readable-snip<%> read-special] method; see
@scheme[open-input-text-editor] for details.

View File

@ -22,7 +22,7 @@ See @method[event% get-time-stamp] for information about
exact-integer?]{
Returns the time, in milliseconds, when the event occurred. This time
is compatible with times reported by MzScheme's
is compatible with times reported by Racket's
@scheme[current-milliseconds] procedure.
}
@ -31,7 +31,7 @@ Returns the time, in milliseconds, when the event occurred. This time
void?]{
Set the time, in milliseconds, when the event occurred. See also
MzScheme's @scheme[current-milliseconds].
Racket's @scheme[current-milliseconds].
If the supplied value is outside the platform-specific range of time
values, @|MismatchExn|.

View File

@ -180,14 +180,14 @@ Evaluating @scheme[(yield 'wait)] is thus similar to
sensitive to whether the current thread is a handler thread, instead
of the value of the @scheme[current-eventspace] parameter.
If @scheme[v] is an event in MzScheme's sense (not to be confused with
If @scheme[v] is an event in Racket's sense (not to be confused with
a GUI event), @scheme[yield] blocks on @scheme[v] in the same way as
@scheme[sync], except that it may start a @scheme[sync] on @scheme[v]
multiple times (but it will complete a @scheme[sync] on @scheme[v] at
most one time). If the current thread is the current eventspace's
handler thread, events are dispatched until a @scheme[v] sync
succeeds on an event boundary. For other threads, calling
@scheme[yield] with a MzScheme event is equivalent to calling
@scheme[yield] with a Racket event is equivalent to calling
@scheme[sync]. In either case, the result is the same that of
@scheme[sync]; however, if a wrapper procedure is associated with
@scheme[v] via @scheme[handle-evt], it is not called in tail position

View File

@ -86,7 +86,7 @@ The result depends on @scheme[what], and a @scheme[#f] result is only
@item{@scheme['init-file] returns the path to the user-specific
initialization file (containing Scheme code). The directory part of
the path is the same path as returned for @scheme['init-dir] by
MzScheme's @scheme[find-system-path]. The file name is
Racket's @scheme[find-system-path]. The file name is
platform-specific:
@itemize[
@ -367,7 +367,7 @@ containing a typestring and value; each typestring is used ad the
keyword name of an AppleEvent argument for the associated converted
value.
The following types of MzScheme values can be converted to AppleEvent
The following types of Racket values can be converted to AppleEvent
values passed to the receiver:
@atable[
@ -390,7 +390,7 @@ if there is an error. If there is no error or return value,
@scheme[send-event] returns @|void-const|.
The following types of AppleEvent values can be reverse-converted into
a MzScheme value returned by @scheme[send-event]:
a Racket value returned by @scheme[send-event]:
@atable[
(tline @elem{Boolean} @elem{@scheme[#t] or @scheme[#f]})
@ -477,4 +477,4 @@ See also @scheme[get-resource].}
@defproc[(key-code-symbol? [v any/c]) boolean?]{
Returns @scheme[#t] if the argument is a symbol that can be returned by
@scheme[key-event%]'s method @method[key-event% get-key-code].
}
}