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

This commit is contained in:
Eli Barzilay 2010-05-16 18:25:39 -04:00
parent 4b0b550e6a
commit 2d9601089d
161 changed files with 345 additions and 346 deletions

View File

@ -6,7 +6,7 @@
(provide compile-simplified)
;; The compiler generates references to prim.ss and
;; runtime.ss exports, as well as MzScheme forms
;; runtime.ss exports, as well as Racket forms
;; and functions. The `ctx' argument provides
;; an appropriate context for those bindings (in
;; the form of a syntax object to use with d->s-o).

View File

@ -295,7 +295,7 @@
(define (never-embedded action)
(when (compiler:option:compile-for-embedded)
(error mzc-symbol "cannot ~a an extension for an embedded MzScheme" action)))
(error mzc-symbol "cannot ~a an extension for an embedded Racket" action)))
(if (compiler:option:3m)
(begin (link-variant '3m) (compile-variant '3m))

View File

@ -79,10 +79,10 @@
[(macosx)
(cond
[(not mred?)
;; Need MzScheme:
;; Need Racket:
(string-append "racket" (variant-suffix variant #f))]
[mred?
;; Need MrEd:
;; Need GRacket:
(let ([sfx (variant-suffix variant #t)])
(build-path (format "GRacket~a.app" sfx)
"Contents" "MacOS"

View File

@ -90,11 +90,11 @@
((,(format "Makes all Scheme sources in specified collection(s)") ""))]
[("--exe")
,(lambda (f name) (exe-output name) 'exe)
(,(format "Embed module in MzScheme to create <exe>")
(,(format "Embed module in Racket to create <exe>")
"exe")]
[("--gui-exe")
,(lambda (f name) (exe-output name) 'gui-exe)
(,(format "Embed module in MrEd to create <exe>")
(,(format "Embed module in GRacket to create <exe>")
"exe")]
[("--exe-dir")
,(lambda (f name) (exe-dir-output name) 'exe-dir)
@ -418,7 +418,7 @@
(define (never-embedded action)
(when (compiler:option:compile-for-embedded)
(error 'mzc "cannot ~a an extension for an embedded MzScheme" action)))
(error 'mzc "cannot ~a an extension for an embedded Racket" action)))
(if (compiler:option:3m)
(begin (link-variant '3m) (compile-variant '3m))

View File

@ -22,7 +22,7 @@
; binding clause for each let-values expression. (Of course, the
; single clause can bind multiple variables.) This linearization does
; not apply to letrec expressions. Technically, it's the source of a bug
; compared to bytecode MzScheme: when call/cc is used on the RHS
; compared to bytecode Racket: when call/cc is used on the RHS
; where an earlier LHS is mutable, the cell for the mutable LHS is
; allocated too early.

View File

@ -178,7 +178,7 @@
case-arities
;; An integer indicating which
;; arity record in compiler:case-lambdas
;; contains MzScheme information for
;; contains Racket information for
;; the arity of the case-lambda. For
;; single-case lambdas, this is #f
;; because the arity information is
@ -201,7 +201,7 @@
prim?
;; application of a known primitive?
prim-name
;; MzScheme name for the known primitive, or #f
;; Racket name for the known primitive, or #f
))
;;----------------------------------------------------------------------------

View File

@ -3,7 +3,7 @@
;; (c) 1997-2001 PLT
; Assign closures to ``vehicles'', and collect information for
; MzScheme about the closures.
; Racket about the closures.
; A vehicle is a C function that implements the body of a
; closure. Multiple closures may be assigned to a single
; vehicle to improve the performance of tail calls.

View File

@ -3379,7 +3379,7 @@
(format " (in ~a)" complain-not-in))
(tok-n (car func))))
;; Lift out function calls as arguments. (Can re-order code.
;; MzScheme source code must live with this change to C's semantics.)
;; Racket source code must live with this change to C's semantics.)
;; Calls are replaced by varaibles, and setup code generated that
;; assigns to the variables.
(let*-values ([(live-vars)

View File

@ -31,7 +31,7 @@
; default = #t
compile-for-embedded ; #f => make objects to be linked
; directly with MzScheme, not dynamically
; directly with Racket, not dynamically
; loaded; default = #f
max-inline-size ; max size of inlined procedures

View File

@ -60,5 +60,5 @@
(extract-suffix append-object-suffix))
(mk 'extract-base-filename/ext
(regexp-quote (subbytes (system-type 'so-suffix) 1) #f)
"MzScheme extension"
"Racket extension"
(extract-suffix append-extension-suffix))))))

View File

@ -7,7 +7,7 @@
(define-struct tid (lid) #:prefab)
(define (create-tid thr) (make-tid thr))
; We need a mapping from MzScheme's tids to our tids (just for `self')
; We need a mapping from Racket's tids to our tids (just for `self')
; and a mapping from symbols to mailboxes (for local threads).
(define tids (make-weak-hash))

View File

@ -149,7 +149,7 @@ _Signal Processors_
> (<proc> behavior ...) -> behavior
FrTime provides "lifted" versions of most of MzScheme. This means
FrTime provides "lifted" versions of most of Racket. This means
that these procedures may be applied to behaviors, and the result
automatically recomputes whenever any of the arguments changes.

View File

@ -665,7 +665,7 @@
(define (racket-launcher-up-to-date? dest [aux null])
(cond
;; When running Setup PLT under Windows, the
;; launcher process stays running until MzScheme
;; launcher process stays running until Racket
;; completes, which means that it cannot be
;; overwritten at that time. So we assume
;; that a Setup-PLT-style independent launcher

View File

@ -139,7 +139,7 @@
;; to whenever the value is actually forced
(~ (parameterize ([param (! val)] ...) (~begin body ...))))
;; Multiple values are problematic: MzScheme promises can use multiple
;; Multiple values are problematic: Racket promises can use multiple
;; values, but to carry that out `call-with-values' should be used in all
;; places that deal with multiple values, which will make the whole thing
;; much slower (about twice in tight loops) -- but multiple values are rarely

View File

@ -99,8 +99,8 @@ _MysterX_
Blocks until all browser windows have been closed or hidden,
using the show method of mx-browser%. This is useful when
a MysterX program file is run as a script, to prevent MzScheme
or MrEd from closing prematurely.
a MysterX program file is run as a script, to prevent Racket
or GRacket from closing prematurely.
> mx-browser% :: (make-object mx-browser% [label] [width] [height] [x] [y] [style-list])
@ -202,7 +202,7 @@ _MysterX_
Handles events using the registered event
handlers. The event handlers are called in a
thread separate from the main MzScheme REPL.
thread separate from the main Racket REPL.
> stop-handling-events :: (send an-mx-browser stop-handling-events)

View File

@ -3,7 +3,7 @@
;; ;Portable regular expressions for Scheme
;; ;Dorai Sitaram
;; ;http://www.ccs.neu.edu/~dorai/pregexp/pregexp.html
;; but `pregexp' functionality is now built into MzScheme, so
;; but `pregexp' functionality is now built into Racket, so
;; this is mostly a wrapper module.
(module pregexp mzscheme

View File

@ -14,16 +14,16 @@
[init-namespace (-> any)])
boolean?]{
Simulates starting MzScheme with the vector of command-line strings
Simulates starting Racket with the vector of command-line strings
@scheme[argv]. The @scheme[init-argv], @scheme[adjust-flag-table], and
@scheme[init-namespace] arguments are used to modify the default
settings for command-line flags, adjust the parsing of command-line
flags, and customize the initial namespace, respectively.
The vector of strings @scheme[init-argv] is read first with the
standard MzScheme command-line parsing. Flags that load files or
standard Racket command-line parsing. Flags that load files or
evaluate expressions (e.g., @Flag{f} and @Flag{e}) are ignored, but
flags that set MzScheme's modes (e.g., @Flag{c} or @Flag{j})
flags that set Racket's modes (e.g., @Flag{c} or @Flag{j})
effectively set the default mode before @scheme[argv] is parsed.
Before @scheme[argv] is parsed, the procedure
@ -34,7 +34,7 @@ a table of command-line flags, and this table is used to parse
add or remove flags from the standard set.
After @scheme[argv] is parsed, a new thread and a namespace are
created for the ``restarted'' MzScheme. (The new namespace is
created for the ``restarted'' Racket. (The new namespace is
installed as the current namespace in the new thread.) In the new
thread, restarting performs the following actions:
@ -64,4 +64,4 @@ the return value is determined as described above.
Note that an error in a command-line expression followed by
@scheme[read-eval-print-loop] produces a @scheme[#t] result. This is
consistent with MzScheme's stand-alone behavior.}
consistent with Racket's stand-alone behavior.}

View File

@ -13,7 +13,7 @@
The @schememodname[mzlib/sendevent] library provides a
@scheme[send-event] function that works only on Mac OS X, and only
when running in MrEd (though the library can be loaded in MzScheme).
when running in GRacket (though the library can be loaded in Racket).
@defproc[(send-event [receiver-bytes (lambda (s) (and (bytes? s)
(= 4 (bytes-length s))))]

View File

@ -249,7 +249,7 @@
(define/kw (zip->output files #:optional [out (current-output-port)])
(parameterize ([current-output-port out])
(let* ([seekable? (seekable-port? (current-output-port))]
[headers ; note: MzScheme's `map' is always left-to-right
[headers ; note: Racket's `map' is always left-to-right
(map (lambda (file)
(zip-one-entry (build-metadata file) seekable?))
files)])

View File

@ -1,4 +1,4 @@
This directory contains a few example MzScheme extensions. Most
This directory contains a few example Racket extensions. Most
examples are implemented directly in C. A few examples listed at the
end use the mzc `c-lambda', etc. forms.
@ -10,7 +10,7 @@ end use the mzc `c-lambda', etc. forms.
from C and adding top-level definitions. (Manually instrumented for
3m, so do not use `mzc --xform'.)
* curses.c - links MzScheme to the curses library. Demonstrates more
* curses.c - links Racket to the curses library. Demonstrates more
procedures and definitions, a little more type dispatching, and
returning multiple values. (Manually instrumented for 3m, so do not
use `mzc --xform'.)

View File

@ -1,5 +1,5 @@
/*
MzScheme extension example that catches exceptions and extracts
Racket extension example that catches exceptions and extracts
error messages.
The defined function is `eval-string/catch-error', which takes a

View File

@ -2,7 +2,7 @@
;; Direct access to fopen, fread, fwrite, and fclose. The interface is
;; not remotely safe, since #f is accepted (and converted to NULL)
;; for `(pointer "FILE")' arguments. Also, blocking reads or writes
;; will block all MzScheme threads.
;; will block all Racket threads.
(c-declare "#include <stdio.h>")

View File

@ -7,7 +7,7 @@
mzc --3m --ld curses.so curses_3m.o -lcurses
For obvious reasons, this library doesn't interact well
with MzScheme's read-eval-print loop. The example file
with Racket's read-eval-print loop. The example file
curses-demo.ss demos this extension.
*/

View File

@ -13,7 +13,7 @@
of Scheme_Object* values for argv, and returns a Scheme_Object*: */
static Scheme_Object *sch_fmod(int argc, Scheme_Object **argv)
{
/* Because we'll use scheme_make_prim_w_arity, MzScheme will
/* Because we'll use scheme_make_prim_w_arity, Racket will
have already checked that we're getting the right number of
arguments. */
Scheme_Object *a = argv[0], *b = argv[1];

View File

@ -1,5 +1,5 @@
/*
MzScheme extension example that returns the string "Hello, world!"
Racket extension example that returns the string "Hello, world!"
when loaded.
For the 3m GC (the default), compile with:

View File

@ -68,9 +68,9 @@
""
"<html>"
"<!-- The form was processed, and this document was generated,"
" using the CGI utilities for MzScheme. For more information"
" on MzScheme, see"
" http://www.plt-scheme.org/software/mzscheme/"
" using the CGI utilities for Racket. For more information"
" on Racket, see"
" http://racket-lang.org/"
" and for the CGI utilities, contact"
" (sk@cs.brown.edu). -->"
"<head>"

View File

@ -88,7 +88,7 @@
(unless (null? cc-recipients)
(write-recipient-header "CC" cc-recipients)))
(fprintf writer "Subject: ~a\n" subject)
(fprintf writer "X-Mailer: MzScheme: see www.plt-scheme.org\n")
(fprintf writer "X-Mailer: Racket (racket-lang.org)\n")
(for-each (lambda (s)
(display s writer)
(newline writer))

View File

@ -5,7 +5,7 @@
;; in the future. (This requirement comes from the SSL library.)
;; Another warning: data that is written and not buffered may still be
;; in flight between MzScheme and the underlying ports. A `flush-output'
;; in flight between Racket and the underlying ports. A `flush-output'
;; won't return until sent data is actually in the underlying port.
;; (This is due to the fact that unbuffered data cannot be written
;; without blocking.)
@ -655,7 +655,7 @@
(flush-ssl mzssl enable-break?)
0)
;; Write request; even if blocking is ok, we treat
;; it as non-blocking and let MzScheme handle blocking
;; it as non-blocking and let Racket handle blocking
(let ([n (SSL_write (mzssl-ssl mzssl) xfer-buffer len)])
(if (n . > . 0)
(begin

View File

@ -135,7 +135,7 @@ number of bytes in the package.
3 Client Download Policies
MzScheme invokes the PLaneT client once for each instance of a require-planet
Racket invokes the PLaneT client once for each instance of a require-planet
form in a program being run (i.e., the transitive closure of the "requires"
relation starting from some specified root module; this closure is calculable
statically). At each of these invocations, the client examines its internal

View File

@ -264,7 +264,7 @@
;; ---
;; documentation stuff --- loaded on demand so that setup/scribble can be
;; omitted in the MzScheme distribution
;; omitted in the Racket distribution
(define-namespace-anchor anchor)
;; render : path[fully-expanded scribble file path] path[fully expanded directory] boolean? -> xref?

View File

@ -2,7 +2,7 @@
_preprocessor_
========================================================================
The "preprocessor" collection defines two MzScheme-based preprocessors
The "preprocessor" collection defines two Racket-based preprocessors
for texts that can have embedded Scheme code. The two processors share
a few features, like several command-line flags and the fact that
embedded Scheme code is case-sensitive by default.
@ -332,7 +332,7 @@ Miscellaneous:
_mztext_
========================================================================
`mztext' is another MzScheme-based preprocessing language. It can be
`mztext' is another Racket-based preprocessing language. It can be
used as a preprocessor in a similar way to `mzpp' since it also uses
`pp-run' functionality. However, `mztext' uses a completely different
processing principle, it is similar to TeX rather than the simple
@ -450,7 +450,7 @@ their arity (preferring a the nullary treatment over the unary one):
* A procedure of arity 0 is simply invoked, and its resulting value is
used. The procedure can freely use the input stream to retrieve
arguments. For example, here is how to define a standard C function
header for use in a MzScheme extension file:
header for use in a Racket extension file:
|@(define (cfunc)
| (format

View File

@ -28,4 +28,4 @@
#:handlers
(lambda (_ . files) (run preprocess run-cmd output files))
'("input-file")
(more-help 'mzpp "a MzScheme-based preprocessor")))
(more-help 'mzpp "a Racket-based preprocessor")))

View File

@ -19,4 +19,4 @@
#:handlers
(lambda (_ . files) (run preprocess run-cmd output files))
'("input-file")
(more-help 'mztext "a MzScheme-based preprocessing language")))
(more-help 'mztext "a Racket-based preprocessing language")))

View File

@ -150,7 +150,7 @@ their arity (preferring a the nullary treatment over the unary one):
@item{A procedure of arity 0 is simply invoked, and its resulting value is
used. The procedure can freely use the input stream to retrieve
arguments. For example, here is how to define a standard C function
header for use in a MzScheme extension file:
header for use in a Racket extension file:
@verbatim[#:indent 2]|{
@(define (cfunc)

View File

@ -463,7 +463,7 @@
begin set!
=> else
;; We have to include the following MzScheme-isms to do anything,
;; We have to include the following Racket-isms to do anything,
;; but they're not legal R5RS names, anyway.
(rename-out [#%plain-module-begin #%module-begin])
#%app #%datum #%top #%top-interaction

View File

@ -456,7 +456,7 @@
(string->symbol thing)]
[(regexp-match? (force rx:number) thing)
(let ([n (string->number
;; MzScheme doesn't handle mantissa widths, yet, so strip them out:
;; Racket doesn't handle mantissa widths, yet, so strip them out:
(regexp-replace* #rx"[|][0-9]+" thing ""))])
(unless n
(error 'r6rs-parser "number didn't convert: ~e" thing))

View File

@ -14,7 +14,7 @@
;; with `module-begin' or `top-interaction', and we wrap such
;; evaluations to swap the namespace in and out.
;; One way in which this differs from MzScheme is that
;; One way in which this differs from Racket is that
;; `#reader'-loaded modules see a different top-level namespace,
;; though it's the same module registry.

View File

@ -2,10 +2,10 @@
;; "genwrite.scm" generic write used by pp.scm
;; copyright (c) 1991, marc feeley
;; Pretty-printer for MzScheme
;; Pretty-printer for Racket
;; Handles structures, cycles, and graphs
;; TO INSTALL this pretty-printer into a MzScheme's read-eval-print loop,
;; TO INSTALL this pretty-printer into Racket's read-eval-print loop,
;; require this module and evaluate:
;; (current-print pretty-print-handler)

View File

@ -5,7 +5,7 @@
(#%require "stxcase-scheme.rkt" "define.rkt"
(for-syntax '#%kernel "stx.rkt"))
;; So that expansions print the way the MzScheme programmer expects:
;; So that expansions print the way the Racket programmer expects:
(#%require (rename '#%kernel #%plain-module-begin #%module-begin))
(define-syntax mzscheme-in-stx-module-begin

View File

@ -2,4 +2,4 @@ The context of this file doesn't matter.
It's existence causes the launcher-maker to
create an "independent launcher", which
means that it doesn't depend on the exact
MzScheme/MrEd executable or DLLs.
Racket/GRacket executable or DLLs.

View File

@ -69,7 +69,7 @@
(verify e_b (imm ṽ_1* ...) ,(add1 (term n_l)) b γ η (shift 1 f))
(where (s_1 γ_1 η_1) (verify e_r (uninit ṽ_1 ...) ,(add1 (term n_l)) #f γ η ))
(side-condition (term (valid? s_1)))
;; MRF: MzScheme implementation checks that s_1 starts with uninit
;; MRF: the Racket implementation checks that s_1 starts with uninit
(where (ṽ_1* ...) (trim s_1 (ṽ_1 ...)))]
; seq

View File

@ -455,7 +455,7 @@
;; ----------------------------------------
;; letrec
;; Need bindings like R5RS, but int-def body like MzScheme
;; Need bindings like R5RS, but int-def body like Racket
(define-syntax-rule (r6rs:letrec bindings . body)
(r5rs:letrec bindings (let () . body)))
@ -512,7 +512,7 @@
;; ----------------------------------------
;; lambda & define
;; Need rest-arg conversion like R5RS, but int-def handlign like MzScheme
;; Need rest-arg conversion like R5RS, but int-def handlign like Racket
(define-syntax (r6rs:lambda stx)
(syntax-case stx ()

View File

@ -7,7 +7,7 @@ The Scribble @-reader is designed to be a convenient facility for
using free-form text in Scheme code, where "@" is chosen as one of
the least-used characters in Scheme code.
You can use the reader via MzScheme's `#reader' form:
You can use the reader via Racket's `#reader' form:
#reader(lib "reader.ss" "scribble")@{This is free-form text!}
@ -19,7 +19,7 @@ A PLT Scheme manual more likely starts with
#reader(lib "docreader.ss" "scribble")
which installs a reader, wraps the file content afterward into a
MzScheme module, and parses the body into a document using
Racket module, and parses the body into a document using
"decode.ss".
Another way to use the reader is to use the `use-at-readtable'

View File

@ -8,7 +8,7 @@ very little insulation against the issues that C programmer faces
related to safety and memory management. An FFI programmer must be
particularly aware of memory management issues for data that spans the
Racket--C divide. Thus, this manual relies in many ways on the
information in @|InsideMzScheme|, which defines how Racket
information in @|InsideRacket|, which defines how Racket
interacts with C APIs in general.
Since using the FFI entails many safety concerns that Racket

View File

@ -39,7 +39,7 @@ If @scheme[path] is @scheme[#f], then the resulting foreign-library
value represents all libraries loaded in the current process,
including libraries previously opened with @scheme[ffi-lib]. In
particular, use @scheme[#f] to access C-level functionality exported
by the run-time system (as described in @|InsideMzScheme|).
by the run-time system (as described in @|InsideRacket|).
Note: @scheme[ffi-lib] tries to look for the library file in a few
places, inluding the PLT libraries (see @scheme[get-lib-search-dirs]),

View File

@ -208,7 +208,7 @@ can contain other information).}
@section{Memory Management}
For general information on C-level memory management with Racket,
see @|InsideMzScheme|.
see @|InsideRacket|.
@defproc[(malloc [bytes-or-type (or/c exact-nonnegative-integer? ctype?)]
[type-or-bytes (or/c exact-nonnegative-integer? ctype?) @#,elem{absent}]

View File

@ -303,7 +303,7 @@ collector.}
A type that can be used with any Racket object; it corresponds to the
@cpp{Scheme_Object*} type of Racket's C API (see
@|InsideMzScheme|). It is useful only for libraries that are aware of
@|InsideRacket|). It is useful only for libraries that are aware of
Racket's C API.}

View File

@ -12,7 +12,7 @@
ffi/vector))
(provide cpp
InsideMzScheme
InsideRacket
(all-from-out scribble/manual)
(for-label (all-from-out racket/base
racket/contract
@ -20,6 +20,5 @@
ffi/unsafe/cvector
ffi/vector)))
(define InsideMzScheme
(define InsideRacket
(other-manual '(lib "scribblings/inside/inside.scrbl")))

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]})

View File

@ -8,7 +8,7 @@
(require (for-label racket/base))
(provide (for-label (all-from-out racket/base)))
(provide Quick MzScheme HtDP
(provide Quick Racket HtDP
tool
moreguide
guideother
@ -60,6 +60,6 @@
(secref #:doc '(lib "scribblings/reference/reference.scrbl") s))
(define (ext-refsecref s)
(make-element #f (list (refsecref s) " in " MzScheme)))
(make-element #f (list (refsecref s) " in " Racket)))
(define MzScheme (other-manual '(lib "scribblings/reference/reference.scrbl"))))
(define Racket (other-manual '(lib "scribblings/reference/reference.scrbl"))))

View File

@ -14,7 +14,7 @@ especially quick introduction to Racket, start with @|Quick|.
@seclink["to-scheme"]{Chapter 2} provides a brief introduction to
Racket. From @seclink["datatypes"]{Chapter 3} on, this guide dives
into details---covering much of the Racket toolbox, but leaving
precise details to @|MzScheme| and other reference manuals.
precise details to @|Racket| and other reference manuals.
@table-of-contents[]

View File

@ -9,7 +9,7 @@
This manual describes Racket's C interface, which allows the
interpreter to be extended by a dynamically-loaded library, or
embedded within an arbitrary C/C++ program. The manual assumes
familiarity with Racket as described in @|MzScheme|.
familiarity with Racket as described in @|Racket|.
For an alternative way of dealing with foreign code, see
@other-manual['(lib "scribblings/foreign/foreign.scrbl")], which

View File

@ -909,7 +909,7 @@ not a file that exists, @var{type} is filled with @cpp{0}.}
[int noexn])]{
Gets the @as-index{current working directory} according to the
operating system. This is separate from MzScheme's current directory
operating system. This is separate from Racket's current directory
parameter.
The directory path is written into @var{buf}, of length @var{buflen},

View File

@ -7,7 +7,7 @@
(for-syntax scheme/base)
(for-label scheme/base))
(provide MzScheme
(provide Racket
mzc cpp cppi cppdef (rename-out [*var var])
function subfunction
FormatD
@ -157,7 +157,7 @@
(define (refsecref s)
(secref #:doc '(lib "scribblings/reference/reference.scrbl") s))
(define MzScheme
(define Racket
(other-manual '(lib "scribblings/reference/reference.scrbl")))
(define (FormatD s)

View File

@ -98,7 +98,7 @@ garbage collector called the master. Places are allowed to garbage collect
independently of one another. The master collector, however, has to pause all
mutators before it can collect garbage.
@section[#:tag "compiling"]{Enabling Places in MzScheme Builds}
@section[#:tag "compiling"]{Enabling Places in Racket Builds}
PLT's parallel-places support is only enabled if you pass
@DFlag{enable-places} to @exec{configure} when you build PLT (and

View File

@ -2,4 +2,4 @@ The context of this file doesn't matter.
It's existence causes the launcher-maker to
create an "independent launcher", which
means that it doesn't depend on the exact
MzScheme/MrEd executable or DLLs.
Racket/GRacket executable or DLLs.

View File

@ -1,4 +1,4 @@
;; sgl -- An OpenGL extension of MzScheme
;; sgl -- An OpenGL extension of Racket
;;
;; Copyright (C) 2003-2010 Scott Owens <sowens@cs.utah.edu>
;;

View File

@ -74,19 +74,19 @@ Slideshow Modules
The _slideshow.ss_ module acts as a language that includes:
- the Slideshow function for creating slides (defined here)
- all of MzScheme
- all of Racket
- texpict/mrpict
- texpict/utils
The _slide.ss_ module is like "slideshow.ss", but it does not
re-provide MzScheme. Thus, "slide.ss" is a non-language version of
re-provide Racket. Thus, "slide.ss" is a non-language version of
"slideshow.ss", and it can be imported with `require' into a module in
any language.
The _run.ss_ module is the same as "slideshow.ss" for backward
compatibility.
[The "slideshow.ss" and "slide.ss" modules also check the MzScheme
[The "slideshow.ss" and "slide.ss" modules also check the Racket
parameter `current-command-line-arguments' to configure the slide
mode.]

View File

@ -296,7 +296,7 @@
;; ----------------------------------------
;; MzScheme provides a rough map to unicode:
;; Racket provides a rough map to unicode:
(define unicode (make-known-char-range-list))
(define (make-standard-set pred?)

View File

@ -37,15 +37,15 @@
;; INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
;; MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
;; -- MzScheme implementation
;; -- Racket implementation
;;
;; The only MzScheme specific features of this implementation is
;; The only Racket specific features of this implementation is
;; CURRENT-SECONDS, the DEFINE-STRUCT procedure (SRFI 9: Defining Record Types
;; could be used), and the constants tm:time-at-zero-seconds
;; and tm:julian-day-at-zero-seconds, which refer to the '0' of CURRENT-SECONDS.
;;
;; SRFI-6, String Ports, and SRFI-8, RECEIVE: Binding Multiple Values,
;; are also used. MzScheme has String Ports built-in. The RECEIVE form
;; are also used. Racket has String Ports built-in. The RECEIVE form
;; is copied below.
;;
; srfi-8: receive
@ -130,7 +130,7 @@
(define time-process 'time-process)
(define time-duration 'time-duration)
;; example of extension (MZScheme specific)
;; example of extension (Racket specific)
(define time-gc 'time-gc)
@ -316,7 +316,7 @@
;;
;; -- using GNU gettimeofday() would be useful here -- gets
;; second + millisecond
;; let's pretend we do, using MzScheme's current-seconds & current-milliseconds
;; let's pretend we do, using Racket's current-seconds & current-milliseconds
;; this is supposed to return UTC.
;;
@ -726,7 +726,7 @@
))
;; relies on the fact that we named our time zone accessor
;; differently from MzScheme's....
;; differently from Racket's....
;; This should be written to be OS specific.
(define (tm:local-tz-offset)
(date-time-zone-offset (seconds->date (current-seconds))))

View File

@ -11,7 +11,7 @@
integer-length)
;; SRFI 60 defines several procedures which are already provided by
;; MzScheme and thus they are not provided by this module, namely
;; Racket and thus they are not provided by this module, namely
;; bitwise-{ior,xor,and,not} and arithmetic-shift. However, SRFI 60
;; names aliases for these procedures, which are provided and which
;; refer to the Mzscheme primitives, namely log{ior,xor,and,not} and
@ -24,7 +24,7 @@
;; The reference implementation follows below and has been changed only
;; by adding S-expression comments to definitions which are not needed,
;; such as definitions implemented as MzScheme exact integer primitives.
;; such as definitions implemented as Racket exact integer primitives.
;;;; "logical.scm", bit access and operations for integers for Scheme
;;; Copyright (C) 1991, 1993, 2001, 2003, 2005 Aubrey Jaffer

View File

@ -4,7 +4,7 @@
_ODBC_
======
SrPersist is an ODBC library for MzScheme and DrScheme.
SrPersist is an ODBC library for Racket and DrRacket.
Any database management system with an ODBC driver should
be usable with SrPersist.
@ -24,7 +24,7 @@
For example, the hypothetical ODBC name SQLProcedureName would be
mapped to the Scheme name procedure-name. The exceptions are SQLError
and SQLExecute, which are mapped to sql-error and sql-execute, to
avoid confusion with MzScheme procedures.
avoid confusion with Racket procedures.
The documentation here may be sufficient to get started with
SrPersist, but you will certainly want to consult an ODBC reference for

View File

@ -13,7 +13,7 @@ installing SrPersist. See the README file in the
SrPersist source directory for such information.
See the section "Loading" in doc.txt to learn how to load
SrPersist into MzScheme or DrScheme. From Help Desk,
SrPersist into Racket or DrRacket. From Help Desk,
search for "SrPersist" and scroll down to that section.
Allocating handles

View File

@ -359,7 +359,7 @@
(stepper-syntax-property #'let-counter 'stepper-binding-type 'stepper-temp))
; syntax-pair-map (using the def'ns of the MzScheme docs):
; syntax-pair-map (using the def'ns of the Racket docs):
(define (syntax-pair-map pair fn)
(cons (fn (car pair))

View File

@ -1,7 +1,7 @@
;;; Written by Eli Barzilay: Maze is Life! (eli@barzilay.org)
;;> The `base' module defines some basic low-level syntactic extensions to
;;> MzScheme. It can be used by itself to get these extensions.
;;> Racket. It can be used by itself to get these extensions.
#lang mzscheme
@ -505,7 +505,7 @@
(rename string->keyword string->real-keyword))
;;>> (keyword? x)
;;> A predicate for keyword symbols (symbols that begin with a ":").
;;> (Note: this is different from MzScheme's keywords!)
;;> (Note: this is different from Racket's keywords!)
(define (keyword*? x)
(and (symbol? x) (not (eq? x '||))
(eq? (string-ref (symbol->string x) 0) #\:)))

View File

@ -195,7 +195,7 @@
;;> itself and the specializers will be used to check the arguments. This
;;> makes it easy to use `method' instead of `lambda' to get some type
;;> information, but note that the result is going to run slower since the
;;> type check only takes time but cannot be used by MzScheme to optimize
;;> type check only takes time but cannot be used by Racket to optimize
;;> the code.
;;>
;;> Note that the specializer argument are evaluated normally, which means

View File

@ -8,7 +8,7 @@
;;; ---------------------------------------------------------------------------
;;; A convenient `defstruct'
;; This makes it possible to create MzScheme structs using Swindle's `make' and
;; This makes it possible to create Racket structs using Swindle's `make' and
;; keyword arguments.
(define struct-to-slot-names (make-hash-table))
@ -57,7 +57,7 @@
;;> to make this a struct that we can access information on. Note that in
;;> method specifiers, the `struct:foo' which is defined by
;;> `define-struct' can be used just like `<foo>'. What all this means is
;;> that you can use MzScheme structs if you just want Swindle's generic
;;> that you can use Racket structs if you just want Swindle's generic
;;> functions, but use built in structs that are more efficient since they
;;> are part of the implementation. For example:
;;>
@ -88,7 +88,7 @@
;;> 3
;;>
;;> The `<struct-name>' identifier *must* be of this form -- enclosed in
;;> "<>"s. This restriction is due to the fact that defining an MzScheme
;;> "<>"s. This restriction is due to the fact that defining a Racket
;;> struct `foo', makes `foo' bound as a syntax object to something that
;;> cannot be used in any other way.
(defsyntax* (defstruct stx)
@ -598,7 +598,7 @@
(*echo-write-handler* write-object)
;;>> (install-swindle-printer)
;;> In MzScheme, output is configurable on a per-port basis. Use this
;;> In Racket, output is configurable on a per-port basis. Use this
;;> function to install Swindle's `display-object' and `write-object' on
;;> the current output and error ports whenever they are changed
;;> (`swindle' does that on startup). This makes it possible to see

View File

@ -151,7 +151,7 @@
;;>> (defmacro name body)
;;>> (defmacro* name body)
;;>> (letmacro ([name body] ...) letbody ...)
;;> These are just like MzScheme's define-macro (from mzlib/defmacro) with
;;> These are just like Racket's define-macro (from mzlib/defmacro) with
;;> two major extensions:
;;> * If `name' is a simple identifier then a symbol-macro is defined (as
;;> with `defsubst' above).
@ -584,7 +584,7 @@
;;>> (some predicate? list ...)
;;>> (every predicate? list ...)
;;> Similar to MzScheme's `ormap' and `andmap', except that when multiple
;;> Similar to Racket's `ormap' and `andmap', except that when multiple
;;> lists are given, the check stops as soon as the shortest list ends.
(define* (some pred? l . rest) ; taken from slib/comlist.scm,
@ -622,7 +622,7 @@
;; ----------------------------------------------------------------------------
;;>>... Multi-dimensional hash-tables
;; Using lists of `eq?' keys, based on MzScheme's hash tables (MzScheme doesn't
;; Using lists of `eq?' keys, based on Racket's hash tables (MzScheme doesn't
;; have custom hashes). Use weak hash-tables so no space is redundantly
;; wasted.
@ -630,7 +630,7 @@
;;>> (l-hash-table-get table keys [failure-thunk])
;;>> (l-hash-table-put! table keys value)
;;>> (set-l-hash-table-get! table key [default] value)
;;> These functions are similar to MzScheme's hash-table functions, except
;;> These functions are similar to Racket's hash-table functions, except
;;> that they work with a list of keys (compared with `eq?'). If it was
;;> possible to use a custom equality hash-table, then then would use
;;> something like
@ -1449,7 +1449,7 @@
;;>> *echo-display-handler* [h]
;;>> *echo-write-handler* [h]
;;> Currently, MzScheme's I/O can be customized only on a per port basis.
;;> Currently, Racket's I/O can be customized only on a per port basis.
;;> This means that installing the object printing generic later will
;;> change only the standard ports, and for new ports a handleres should
;;> always be installed. This means that `echos' will not work with

View File

@ -88,7 +88,7 @@ Swindle environment.
* misc.ss (module)
Lots of useful functionality bits, including everything from
frequently useful MzScheme standard libraries (`list.ss', `etc.ss',
frequently useful Racket standard libraries (`list.ss', `etc.ss',
and `string.ss').
* turbo.ss (language module)

View File

@ -2,7 +2,7 @@
;;> This module provides the forms `setf!', `psetf!', and `setf!-values' for
;;> generic setters, much like CL's `setf', and `psetf', and a form similar
;;> to MzScheme's `set!-values'. Note that when these are later re-exported
;;> to Racket's `set!-values'. Note that when these are later re-exported
;;> (by `turbo'), they are renamed as `set!', `pset!', and `set!-values'
;;> (overriding the built-in `set!' and `set!-values'). Also, note that
;;> this just defines the basic functionality, the `misc' module defines

View File

@ -105,7 +105,7 @@ whole Swindle environment.
macros.}
@item{@scheme[swindle/misc] (module) --- Lots of useful functionality
bits, including everything from frequently useful MzScheme legacy
bits, including everything from frequently useful Racket legacy
libraries (@schememodname[mzlib/list], @schememodname[mzlib/etc],
and @schememodname[mzlib/string]).}

View File

@ -2,7 +2,7 @@
;;> This module is the core object system. It is a heavily hacked version
;;> of the original Tiny-CLOS code from Xerox, but it has been fitted to
;;> MzScheme, optimized and extended. See the source file for a lot of
;;> Racket, optimized and extended. See the source file for a lot of
;;> details about how the CLOS magic is created.
;;>
;;> [There is one difference between Swindle and Tiny-CLOS: the meta object
@ -216,15 +216,15 @@
;;; implementation of instances and entities from people.
;;>> ???
;;> This is MzScheme's `unspecified' value which is used as the default
;;> This is Racket's `unspecified' value which is used as the default
;;> value for unbound slots. It is provided so you can check if a slot is
;;> unbound.
(define* ??? (letrec ([x x]) x)) ; this is MzScheme's #<undefined> value
(define* ??? (letrec ([x x]) x)) ; this is Racket's #<undefined> value
(define unspecified-initializer (lambda args ???))
(define false-func (lambda args #f))
;; Basic allocation follows, all was in a single let, but this is not needed
;; with MzScheme's modules. Also modified to use simple structs for
;; with Racket's modules. Also modified to use simple structs for
;; everything, including entities since PLT has applicable struct objects.
(define-values (struct:instance make-instance instance? inst-ref inst-set!)
@ -484,13 +484,13 @@
(define* singleton-value cadr)
;;>>...
;;> Also note that MzScheme struct types are converted to appropriate
;;> Also note that Racket struct types are converted to appropriate
;;> Swindle classes. This way, it is possible to have Swindle generic
;;> functions that work with struct type specializers.
;;>> (struct-type->class struct-type)
;;> This function is used to convert a struct-type to a corresponding
;;> Swindle subclass of `<struct>'. See the MzScheme manual for details
;;> Swindle subclass of `<struct>'. See the Racket manual for details
;;> on struct types.
(define struct-to-class-table (make-hash-table))
(define* (struct-type->class stype)
@ -1990,7 +1990,7 @@
;;>> <struct>
;;>> <opaque-struct>
;;> These are also classes for built-in objects, but they are classes for
;;> MzScheme structs -- which can be used like Swindle classes since they
;;> Racket structs -- which can be used like Swindle classes since they
;;> will get converted to appropriate Swindle subclasses of `<struct>'.
;;> `<opaque-struct>' is a class of structs that are hidden -- see the
;;> documentation for `struct-info' and the `skipped?' result. Note that
@ -2045,7 +2045,7 @@
(defprimclass <input-port> <port>)
(defprimclass <output-port> <port>)
(defprimclass <stream-port> <port>)
;; MzScheme stuff
;; Racket stuff
(defprimclass <input-stream-port> <input-port> <stream-port>)
(defprimclass <output-stream-port> <output-port> <stream-port>)
(defprimclass <void>)
@ -2097,7 +2097,7 @@
:direct-supers (list <builtin> <function>)
:direct-slots '()))
;;>> <primitive-procedure>
;;> The class of all primitive MzScheme procedures.
;;> The class of all primitive Racket procedures.
(define* <primitive-procedure>
(make <procedure-class>
:name '<primitive-procedure>

View File

@ -15,21 +15,21 @@ _stx.ss_: deconstructing syntax objects
> (stx-pair? v) - returns #t if `v' is either a pair or a syntax
object representing a pair. See also the definition of "syntax pair"
in the MzScheme manual.
in the Racket manual.
> (stx-list? v) - returns #t if `v' is a list, or if it is a sequence
of pairs leading to a syntax object such that `syntax->list' (from
MzScheme) would produce a list.
Racket) would produce a list.
> (stx->list stx-list) - produces a list by flatting out a trailing
syntax object using `syntax->list'. The `stx-list' argument must be
a value for which `stx-list?' would return #t.
> (stx-car v) - takes the car of a "syntax pair". See the definition
of "syntax pair" in the MzScheme manual.
of "syntax pair" in the Racket manual.
> (stx-cdr v) - takes the cdr of a "syntax pair". See the definition
of "syntax pair" in the MzScheme manual.
of "syntax pair" in the Racket manual.
> (module-or-top-identifier=? a-id b-id) - returns #t if `a-id' and
`b-id' are module-identifier=?, or if `a-id' and `b-id' have the
@ -37,11 +37,11 @@ _stx.ss_: deconstructing syntax objects
other than at the top level.
This procedure is useful in conjunction with `syntax-case*' to match
procedure names that are normally bound by MzScheme. For example,
procedure names that are normally bound by Racket. For example,
the `include' macro uses this procedure to recognize `build-path';
using `module-identifier=?' would not work well outside of
`module', since the top-level `build-path' is a distinct variable
from the MzScheme export (though it's bound to the same procedure,
from the Racket export (though it's bound to the same procedure,
initially).
======================================================================
@ -50,7 +50,7 @@ _kerncase.ss_: matching fully-expanded expressions
> (kernel-syntax-case stx-expr trans?-expr clause ...) - a syntactic
form like `syntax-case*', except that the literals are built-in as
the names of the primitive MzScheme forms. (The primitive syntactic
the names of the primitive Racket forms. (The primitive syntactic
forms must have their normal bindings in the context of the
`kernel-syntax-case' expression.)
@ -62,10 +62,10 @@ _kerncase.ss_: matching fully-expanded expressions
> (kernel-syntax-case* stx-expr trans?-expr (extras ...) clause ...) -
a syntactic form like `kernel-syntax-case', except that it takes an
additional list of extra literals that are used as well as the
primitive MzScheme forms.
primitive Racket forms.
> (kernel-form-identifier-list syntax) - returns a list of identifiers
for the names of the primitive MzScheme forms for expressions, with
for the names of the primitive Racket forms for expressions, with
the lexical context of `syntax'. This function is useful for
generating a list of stopping points to provide to `local-expand'.
@ -189,7 +189,7 @@ _struct.ss_: generating the same names as `define-struct'
> (struct-declaration-info? v) - returns #t if `x' has the shape of
expansion-time information for structure type declarations, #f
otherwise. See also the syntax chapter of the MzScheme manual.
otherwise. See also the syntax chapter of the Racket manual.
> (generate-struct-declaration orig-stx name-id super-id-or-false
field-id-list current-context
@ -282,7 +282,7 @@ _docprovide.ss_: attaching documentation to exports
> (lookup-documentation module-path-v label-sym) - returns
documentation for the specified module and label. The
`module-path-v' argument is a quoted module path, like the argument
to MzScheme's `dynamic-require'. The `label-sym' identifies a set of
to Racket's `dynamic-require'. The `label-sym' identifies a set of
documentation using the symbol as a label identifier in
`provide-and-document'.
@ -307,7 +307,7 @@ _modread.ss_: reading module source code
inspects `stx' to check whether evaluating it will declare a module
named `expected-module-sym' (plus a prefix, if
`current-module-name-prefix' is set) --- at least if `module' is
bound in the top-level to MzScheme's `module'. The syntax object
bound in the top-level to Racket's `module'. The syntax object
`stx' can contain a compiled expression. Also, `stx' can be an
end-of-file, on the grounds that `read-syntax' can produce an
end-of-file.
@ -332,7 +332,7 @@ _modcode.ss_: getting module compiled code
[#:notify notify-proc]) -
returns a compiled expression for the declaration of the module
specified by `module-path-v'. The `module-path-v' argument is a
quoted module path, as for MzScheme's `dynamic-require' using the
quoted module path, as for Racket's `dynamic-require' using the
default module path resolver.
The `compiled-subdir' argument defaults to "compiled"; it specifies
@ -389,7 +389,7 @@ _modresolve.ss_: resolving module paths to file paths
======================================================================
Interpretations of module paths in this library mimic that of the
default module path resolver in MzScheme (which means that the library
default module path resolver in Racket (which means that the library
is limited, but certainly useful as no other module path resolvers
currently exist).
@ -398,12 +398,12 @@ currently exist).
relative to `rel-to-path-string/thunk/#f' if it is a path string
(assumed to be for a file), to the directory result of calling the
thunk if it is a thunk, or to the current directory otherwise. The
`module-path-v' argument is a quoted module path, as for MzScheme's
`module-path-v' argument is a quoted module path, as for Racket's
`dynamic-require' using the default module path resolver.
> (resolve-module-path-index module-path-index rel-to-path-string/thunk/#f)
- like `resolve-module-path' but the input is a module path index
(see the MzScheme manual for details); in this case, the
(see the Racket manual for details); in this case, the
`rel-to-path-string/thunk/#f' base is used where the module path
index contains the "self" index. If `module-path-index' depends on
the "self" module path index, then an exception is raised unless
@ -414,7 +414,7 @@ _modcollapse.ss_: simplifying module paths
======================================================================
Interpretations of module paths in this library mimic that of the
default module path resolver in MzScheme (which means that the library
default module path resolver in Racket (which means that the library
is limited, but certainly useful as no other module path resolvers
currently exist).
@ -423,7 +423,7 @@ currently exist).
`rel-to-module-path', where the latter must have the form '(lib
....), '(file <string>), '(path ....) a path, or a thunk to generate
one of those. The `module-path-v' argument is a quoted module path,
as for MzScheme's `dynamic-require' using the default module path
as for Racket's `dynamic-require' using the default module path
resolver.
The result can be a path if `module-path-v' contains a path element
@ -433,7 +433,7 @@ currently exist).
> (collapse-module-path-index module-path-index rel-to-module-path-v)
- like `collapse-module-path', but the input is a module path index
(see the MzScheme manual for details); in this case, the
(see the Racket manual for details); in this case, the
`rel-to-module-path-v' base is used where the module path index
contains the "self" index.

View File

@ -17,7 +17,7 @@ DHTML test code
The file dhtmltests.ss contains a number of tests
for the Dynamic HTML capabilities of MysterX.
Simply load the file into MzScheme or DrScheme to run the
Simply load the file into Racket or DrRacket to run the
tests. Any errors will be printed in the REPL.
The behavior that appears in the window that is created
may be ignored.

View File

@ -5,7 +5,7 @@
;; Limitations of this test suite:
;; - It doesn't check reader-level parameterization, such as use of quotes
;; - It doesn't check format of printed results
;; - It doesn't check the absence of MzScheme forms
;; - It doesn't check the absence of Racket forms
;; Don't try to run other tests from the test suite after loading this
;; one into a particular namespace.

View File

@ -6,7 +6,7 @@
;; Limitations of this test suite:
;; - It doesn't check reader-level parameterization, such as use of quotes
;; - It doesn't check format of printed results
;; - It doesn't check the absence of MzScheme forms
;; - It doesn't check the absence of Racket forms
;; Don't try to run other tests from the test suite after loading this
;; one into a particular namespace.

View File

@ -15,9 +15,9 @@
run time, or stack overflow).</p>
<p>Run times are averaged over three runs. All reported times are CPU time (system plus user).
The times for MzScheme, Perl, and Python use the language's sime function to record the
The times for Racket, Perl, and Python use the language's sime function to record the
times before and after a loop within the language; the PCRE times are based on calls
a timed MzScheme loop using calling PCRE via <tt>(lib "foreign.ss")</tt>.</p>
a timed Racket loop using calling PCRE via <tt>(lib "foreign.ss")</tt>.</p>
<p>A benchmark name <tt><i>name</i>/<i>N</i>/<i>M</i></tt> means that the
input size was roughly 10<sup><i>N</i></sup> and roughly
@ -49,7 +49,7 @@
Perl lags significantly only on the <tt>stress-nopeci</tt> benchmarks, which
require lots of backtracking unless the implementation first
checks for the existence of a <i>case-insensitive</i> version of a
literal string; MzScheme checks only because the CL-PPCRE benchmark
literal string; Racket checks only because the CL-PPCRE benchmark
suite suggested the test.</dd>
<dt> Python: 2.3.5 <b>(old version!)</b></dt>
@ -67,7 +67,7 @@
infrastructure, which is available form the PLT SVN repository:</p>
<p align=center>
<a href="http://svn.plt-scheme.org/plt/trunk/collects/tests/mzscheme/benchmarks/rx/">http://svn.plt-scheme.org/plt/trunk/collects/tests/mzscheme/benchmarks/rx/</a></P>
<a href="http://git.racket-lang.org/plt/tree/HEAD:/collects/tests/racket/benchmarks/rx">http://git.racket-lang.org/plt/tree/HEAD:/collects/tests/racket/benchmarks/rx</a></P>
<H1>Results</H1>

View File

@ -191,7 +191,7 @@
(memcpy p 3 p 0 1 _int)
(test 5 ptr-ref (ptr-add p 3 _int) _int)
;; A MzScheme `int' is always 4 bytes.
;; A Racket `int' is always 4 bytes.
(memset p 1 17 9 _int)
(test 5 ptr-ref p _int)
(test #x11111111 ptr-ref (ptr-add p 4) _int)

View File

@ -1,5 +1,5 @@
; Test MzScheme's name inference
; Test Racket's name inference
(load-relative "loadtest.rktl")

View File

@ -1,5 +1,5 @@
; Test MzScheme's object system
; Test Racket's object system
(load-relative "loadtest.rktl")

View File

@ -1255,7 +1255,7 @@
;; ------------------------------------------------------------
;; Check arity reporting for methods.
;; (This is really a MzScheme test, not a class.s test.)
;; (This is really a Racket test, not a class.rkt test.)
(map
(lambda (jit?)

View File

@ -70,7 +70,7 @@
(test #f char-ready? r))
;; ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;; Based on the MzScheme manual...
;; Based on the Racket manual...
;; A port with no input...
;; Easy: \scheme{(open-input-bytes #"")}
@ -362,7 +362,7 @@
(go peek-bytes-avail!/enable-break))
;; ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;; Also based on the MzScheme manual...
;; Also based on the Racket manual...
(define should-be-breakable? #t)

View File

@ -2,8 +2,8 @@
(load-relative "loadtest.rktl")
;; Test that all SRFIs load. Run this in both DrScheme and
;; MzScheme for maximum coverage.
;; Test that all SRFIs load. Run this in both DrRacket and
;; Racket for maximum coverage.
;; We just require all the SRFIs and hope nothing bombs.
;; Keep an eye out for error messages!

View File

@ -1,4 +1,4 @@
;;; `test.scm' Test correctness of MzScheme implementations.
;;; `test.scm' Test correctness of Racket implementations.
;;; Copyright (C) 1991, 1992, 1993, 1994 Aubrey Jaffer.
;;; Modified for MzScheme by Matthew

View File

@ -1,5 +1,5 @@
;;; This file simply tests that all the SRFIs load. Just
;;; load it into MzScheme to perform this test. Remember it
;;; load it into Racket to perform this test. Remember it
;;; might not be up-to-date, so check before you run it!

View File

@ -1,6 +1,6 @@
(module mz-testing mzscheme
;;; `test.scm' Test correctness of MzScheme implementations.
;;; `test.scm' Test correctness of Racket implementations.
;;; Copyright (C) 1991, 1992, 1993, 1994 Aubrey Jaffer.
;;; Modified for MzScheme by Matthew

View File

@ -112,7 +112,7 @@
"\"-//W3C//DTD HTML 4.01 Transitional//EN\" "
"\"http://www.w3.org/TR/html4/loose.dtd\""))
(define *scheme-version* (string-append "MzScheme " (version)))
(define *scheme-version* (string-append "Racket " (version)))
(define *path-separator* (if (eqv? *operating-system* 'windows) #\; #\:))

View File

@ -1,6 +1,6 @@
_texpict_ is a MzScheme/MrEd library for creating pictures using a
MrEd dc<%> (including post-script-dc% for _PostScript_ output) or
_texpict_ is a Racket/GRacket library for creating pictures using a
GRacket dc<%> (including post-script-dc% for _PostScript_ output) or
_LaTeX_ as the back-end. The two back-ends are incompatible; picts
must be created for one or the other. The library was originally
designed for LaTeX output, hence the name.
@ -132,7 +132,7 @@ auxiliary file when LaTeX evaluates the expression. If you use
* Use the package "mztp.sty" at the start of your LaTeX
document "X.tex".
* In the MzScheme code creating `tex' picts, call
* In the Racket code creating `tex' picts, call
(read-in-sizes "X.mztp") before calling `tex'.
* Run the texpict-LaTeX cycle twice to get properly
draw pictures.
@ -1200,7 +1200,7 @@ The following four are for backward compatibility:
has no ascent.
> current-keyword-list - a parameter, a list of strings to color as
keywords; the default includes the MzScheme syntactic form names
keywords; the default includes the Racket syntactic form names
> current-const-list - a parameter, a list of strings to color as
constants; the default is empty
> current-literal-list - a parameter, a list of strings to color as

View File

@ -19,8 +19,8 @@
(export stacktrace^)
;; TEMPLATE FUNCTIONS:
;; these functions' definitions follow the data definitions presented in the Syntax
;; chapter of the MzScheme Manual.
;; these functions' definitions follow the data definitions presented in the
;; Syntax chapter of the Racket Manual.
(define (top-level-expr-iterator stx)
(kernel-syntax-case stx #f

View File

@ -148,7 +148,7 @@ tex2page runs on Scheme or Common Lisp. It may also make use
of the following programs: BibTeX, MakeIndex, Ghostscript,
Dvips, MetaPost, and the NetPBM library.
Out of the box, tex2page runs in MzScheme, but the distribution
Out of the box, tex2page runs in Racket, but the distribution
includes configuration information to allow tex2page to run on
a variety of Scheme and Common Lisp implementations. See file
INSTALL.

View File

@ -403,7 +403,7 @@ static Scheme_Object *foreign_ffi_obj_name(int argc, Scheme_Object *argv[])
/*****************************************************************************/
/* Type helpers */
/* These are not defined in MzScheme because:
/* These are not defined in Racket because:
* - SCHEME_UINT_VAL is not really a simple accessor like other SCHEME_X_VALs
* - scheme_make_integer_from_unsigned behaves the same as the signed version
*/
@ -425,7 +425,7 @@ static Scheme_Object *foreign_ffi_obj_name(int argc, Scheme_Object *argv[])
#else /* SIXTY_FOUR_BIT_INTEGERS defined */
/* These will make sense in MzScheme when longs are longer than ints (needed
/* These will make sense in Racket when longs are longer than ints (needed
* for libffi's int32 types). There is no need to deal with bignums because
* mzscheme's fixnums are longs. */
inline int scheme_get_realint_val(Scheme_Object *o, int *v)
@ -508,10 +508,10 @@ Scheme_Object *utf16_pointer_to_ucs4_string(unsigned short *utf)
* The following are the only primitive types.
* The tricky part is figuring out what width-ed types correspond to
* what internal types. Matthew says:
* MzScheme expects to be compiled such that sizeof(int) == 4,
* Racket expects to be compiled such that sizeof(int) == 4,
* sizeof(long) == sizeof(void*), sizeof(short) >= 2,
* sizeof(char) == 1, sizeof(float) == 4, and sizeof(double) == 8.
* So, on a 64-bit OS, MzScheme expects only `long' to change.
* So, on a 64-bit OS, Racket expects only `long' to change.
**********************************************************************/
/* returns #<void> when used as output type, not for input types. */
@ -783,7 +783,7 @@ Scheme_Object *utf16_pointer_to_ucs4_string(unsigned short *utf)
*/
/* This is used for passing and Scheme_Object* value as is. Useful for
* functions that know about Scheme_Object*s, like MzScheme's. */
* functions that know about Scheme_Object*s, like Racket's. */
#define FOREIGN_scheme (25)
/* Type Name: scheme
* LibFfi type: ffi_type_gcpointer

View File

@ -317,7 +317,7 @@ THREAD_LOCAL_DECL(static Scheme_Hash_Table *opened_libs);
/*****************************************************************************/
/* Type helpers */
/* These are not defined in MzScheme because:
/* These are not defined in Racket because:
* - SCHEME_UINT_VAL is not really a simple accessor like other SCHEME_X_VALs
* - scheme_make_integer_from_unsigned behaves the same as the signed version
*/
@ -339,7 +339,7 @@ THREAD_LOCAL_DECL(static Scheme_Hash_Table *opened_libs);
}{
/* These will make sense in MzScheme when longs are longer than ints (needed
/* These will make sense in Racket when longs are longer than ints (needed
* for libffi's int32 types). There is no need to deal with bignums because
* mzscheme's fixnums are longs. */
inline int scheme_get_realint_val(Scheme_Object *o, int *v)
@ -562,10 +562,10 @@ Scheme_Object *utf16_pointer_to_ucs4_string(unsigned short *utf)
* The following are the only primitive types.
* The tricky part is figuring out what width-ed types correspond to
* what internal types. Matthew says:
* MzScheme expects to be compiled such that sizeof(int) == 4,
* Racket expects to be compiled such that sizeof(int) == 4,
* sizeof(long) == sizeof(void*), sizeof(short) >= 2,
* sizeof(char) == 1, sizeof(float) == 4, and sizeof(double) == 8.
* So, on a 64-bit OS, MzScheme expects only `long' to change.
* So, on a 64-bit OS, Racket expects only `long' to change.
**********************************************************************/
/* returns #<void> when used as output type, not for input types. */
@ -730,7 +730,7 @@ Scheme_Object *utf16_pointer_to_ucs4_string(unsigned short *utf)
@; 'c->s (lambda (x) x))
@;
/* This is used for passing and Scheme_Object* value as is. Useful for
* functions that know about Scheme_Object*s, like MzScheme's. */
* functions that know about Scheme_Object*s, like Racket's. */
@(defctype 'scheme
'ftype "gcpointer"
'ctype "Scheme_Object*"

View File

@ -173,7 +173,7 @@ static MrQueueElem *first, *last;
* region manually (and then must reinstate it when it's
* time to handle the event. ick.
* 2. high level events. Dispatched immediately, and the
* handlers queue work in MzScheme threads.
* handlers queue work in Racket threads.
* 3. suspendResumeMessage. See comment at top.
*/

View File

@ -422,7 +422,7 @@ int wxEventTrampoline(HWND hWnd, UINT message, WPARAM wParam, LPARAM lParam,
For certain kinds of events, the callback queueing is most easily
implemented in Scheme within mred.ss. For those cases, we put
MzScheme into atomic mode while handling the event. The "mred.ss"
Racket into atomic mode while handling the event. The "mred.ss"
implementation promises to run quickly (and not call user code).
Scrolling is a special case. To implement interactive scrolling,

View File

@ -1507,7 +1507,7 @@ static Scheme_Object *wxSchemeGetPanelBackground(int, Scheme_Object **)
#ifdef wx_mac
# ifdef OS_X
/* In MzScheme in Classic, mredmac.cxx in OS X */
/* In Racket in Classic, mredmac.cxx in OS X */
extern int scheme_mac_path_to_spec(const char *filename, FSSpec *spec);
# endif
@ -2290,7 +2290,7 @@ static Scheme_Object *wxInAtomicRegion(int, Scheme_Object **argv)
{
if (SCHEME_SEMAP(argv[0])) {
scheme_wait_sema(argv[0], 0);
/* MzScheme promises that no break or kill will happen
/* Racket promises that no break or kill will happen
between receiving the semaphore post and returning to us. */
scheme_start_atomic();
} else
@ -2421,7 +2421,7 @@ static Scheme_Object *wLabelShortcutsVisible(int argc, Scheme_Object **argv)
#ifdef wx_mac
# ifdef OS_X
/* In MzScheme in Classic, mredmac.cxx in OS X */
/* In Racket in Classic, mredmac.cxx in OS X */
extern char *scheme_mac_spec_to_path(FSSpec *spec);
# endif
# ifndef OS_X

View File

@ -14,7 +14,7 @@ the Thread.Abort() method.
To use this code, the environment variable `Cor_Enable_Profiling' must
be set to "1", and the environment variable `Cor_Profiler' must be set
to "MysterX.DotnetProfiler" before starting the CLR. (They may be set
by calling the MzScheme function putenv.)
by calling the Racket function putenv.)
If correctly set, a message like the following will be printed when
the CLR is started:

View File

@ -146,7 +146,7 @@ void setupSchemeEnv(Scheme_Env *in_env)
ExitThread(0);
}
// set up collection paths, based on MzScheme startup
// set up collection paths, based on Racket startup
mod = GetModuleHandle("mzcom.exe");
GetModuleFileName(mod,exeBuff,sizeof(exeBuff));
@ -192,7 +192,7 @@ static int do_evalLoop(Scheme_Env *env, int argc, char **_args)
BSTR *pOutput, po;
MSG msg;
// make sure all MzScheme calls are in this thread
// make sure all Racket calls are in this thread
setupSchemeEnv(env);
@ -275,7 +275,7 @@ static int do_evalLoop(Scheme_Env *env, int argc, char **_args)
scheme_gc_ptr_ok(narrowInput);
if (*pErrorState) {
wideError = wideStringFromSchemeObj(outputObj,"MzScheme error: ~a",18);
wideError = wideStringFromSchemeObj(outputObj,"Racket error: ~a",18);
po = SysAllocString(L"");
*pOutput = po;
*pHr = E_FAIL;

Some files were not shown because too many files have changed in this diff Show More