many typos
svn: r8045
This commit is contained in:
parent
e050a30cdb
commit
c71d064da6
|
@ -30,7 +30,7 @@ will try all of them.
|
|||
|
||||
If @scheme[path] is @scheme[#f], then the resulting foreign-library
|
||||
value represents all libraries loaded in the current process,
|
||||
including libraries previouly opened with @scheme[ffi-lib]. In
|
||||
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|).
|
||||
|
||||
|
|
|
@ -86,7 +86,7 @@ pointer, such as supplying the pointer to a foreign function. In
|
|||
particular, the pointer and offset are not combined until after all
|
||||
allocation leading up to a foreign-function call; if the called
|
||||
function does not itself call anything that can trigger a garbage
|
||||
collection, it can safey use pointers that are offset into the middle
|
||||
collection, it can safely use pointers that are offset into the middle
|
||||
of a GCable object.}
|
||||
|
||||
|
||||
|
@ -219,7 +219,7 @@ see @|InsideMzScheme|.
|
|||
|
||||
Allocates a memory block of a specified size using a specified
|
||||
allocation. The result is a @scheme[cpointer] to the allocated
|
||||
memory. Alhough not reflected above, the four arguments can appear in
|
||||
memory. Although not reflected above, the four arguments can appear in
|
||||
any order since they are all different types of Scheme objects; a size
|
||||
specification is required at minimum:
|
||||
|
||||
|
|
|
@ -18,7 +18,7 @@ along with conversion functions to and from the existing types.
|
|||
@defproc[(make-ctype [type ctype?]
|
||||
[scheme-to-c (or/c false/c (any/c . -> . any))]
|
||||
[c-to-scheme (or/c false/c (any/c . -> . any))])
|
||||
cttype?]{
|
||||
ctype?]{
|
||||
|
||||
Creates a new @tech{C type} value, with the given conversions
|
||||
functions. The conversion functions can be @scheme[#f] meaning that
|
||||
|
@ -136,7 +136,7 @@ inputs.}
|
|||
|
||||
@subsection{Primitive String Types}
|
||||
|
||||
The five primitive string types corerspond to cases where a C
|
||||
The five primitive string types correspond to cases where a C
|
||||
representation matches MzScheme's representation without encodings.
|
||||
|
||||
The form @scheme[_bytes] form can be used type for Scheme byte
|
||||
|
@ -173,7 +173,7 @@ Return values using this type are interned as symbols.}
|
|||
[_string/locale ctype?])]{
|
||||
|
||||
Types that correspond to (character) strings on the Scheme side and
|
||||
@cpp{char*} strings on the C side. The brige between the two requires
|
||||
@cpp{char*} strings on the C side. The bridge between the two requires
|
||||
a transformation on the content of the string. As usual, the types
|
||||
treat @scheme[#f] as @cpp{NULL} and vice-versa.}
|
||||
|
||||
|
@ -205,7 +205,7 @@ the parameter should be set before any interface definition that uses
|
|||
|
||||
@defparam[default-_string-type type ctype?]{
|
||||
|
||||
A parameter that determines the current meanging of @scheme[_string].
|
||||
A parameter that determines the current meaning of @scheme[_string].
|
||||
It is initially set to @scheme[_string/*utf-8]. If you change it, do
|
||||
so @italic{before} interfaces are defined.}
|
||||
|
||||
|
@ -630,7 +630,7 @@ way to store pointers to GC-managed objects in structs (even if you
|
|||
keep a reference to avoid collecting the referenced objects, a the 3m
|
||||
variant's GC will invalidate the pointer's value). Thus, only
|
||||
non-pointer values and pointers to memory that is outside the GC's
|
||||
control can be lpaced into struct fields.
|
||||
control can be placed into struct fields.
|
||||
|
||||
As an example, consider the following C code:
|
||||
|
||||
|
|
|
@ -9,7 +9,7 @@
|
|||
|
||||
@declare-exporting['#%foreign]
|
||||
|
||||
Parts of the @schememodname[scheme/foreign] libray are implemented by
|
||||
Parts of the @schememodname[scheme/foreign] library are implemented by
|
||||
the MzScheme built-in @schememodname['#%foreign] module. The
|
||||
@schememodname['#%foreign] module is not intended for direct use, but
|
||||
it exports the following procedures. If you find any of these useful,
|
||||
|
|
|
@ -3,7 +3,7 @@
|
|||
|
||||
@defclass/title[button% object% (control<%>)]{
|
||||
|
||||
Whenever a button is clicked by the user, the buttons's callback
|
||||
Whenever a button is clicked by the user, the button's callback
|
||||
procedure is invoked. A callback procedure is provided as an
|
||||
initialization argument when each button is created.
|
||||
|
||||
|
|
|
@ -43,7 +43,7 @@ Under Windows, if @scheme[extension] is not @scheme[#f], the returned path
|
|||
ignored on other platforms.
|
||||
|
||||
The @scheme[style] list can contain @scheme['common], a
|
||||
platform-independant version of the dialog is used instead of a
|
||||
platform-independent version of the dialog is used instead of a
|
||||
native dialog. Under Mac OS X, if the @scheme[style] list
|
||||
contains @scheme['packages], a user is allowed to select a package
|
||||
directory, which is a directory with a special suffix (e.g.,
|
||||
|
@ -116,12 +116,12 @@ Under Windows, if @scheme[extension] is not @scheme[#f], the returned path
|
|||
@scheme[filters] argument has the same format and auxiliary role as for
|
||||
@scheme[get-file]. In particular, if the only pattern in @scheme[filters]
|
||||
is @scheme[(string-append "*." extension)], then the result pathname is guaranteed
|
||||
to have an extenson mapping @scheme[extension].
|
||||
to have an extension mapping @scheme[extension].
|
||||
|
||||
Under Mac OS X, if @scheme[extension] is not @scheme[#f]
|
||||
and @scheme[filters] contains the single
|
||||
pattern @scheme[(string-append "*." extension)], then the result pathname is
|
||||
guaranteed to have an extenson mapping @scheme[extension]. Otherwise,
|
||||
guaranteed to have an extension mapping @scheme[extension]. Otherwise,
|
||||
@scheme[extension] and @scheme[filters] are ignored.
|
||||
|
||||
The @scheme[extension] argument is ignored under X, and @scheme[filters]
|
||||
|
|
|
@ -5,7 +5,7 @@
|
|||
@title{Dynamic Loading}
|
||||
|
||||
@defmodule[scheme/gui/dynamic]{The @schememodname[scheme/gui/dynamic]
|
||||
library provides functiosn for dynamically accessing the PLT Scheme
|
||||
library provides functions for dynamically accessing the PLT Scheme
|
||||
GUI toolbox, instead of directly requiring @scheme[scheme/gui] or
|
||||
@scheme[scheme/gui/base].}
|
||||
|
||||
|
|
|
@ -328,7 +328,7 @@ Shows or hides the snip's border.
|
|||
boolean?]{
|
||||
|
||||
Returns @scheme[#t] if the snip uses its style's background and
|
||||
transparency informaiton when drawing, @scheme[#f] otherwise.
|
||||
transparency information when drawing, @scheme[#f] otherwise.
|
||||
|
||||
See also @method[editor-snip% use-style-background].
|
||||
|
||||
|
|
|
@ -277,7 +277,7 @@ The icon is used in a platform-specific way:
|
|||
|
||||
@item{Windows --- the small icon is used for the frame's icon (in the
|
||||
top-left) and in the task bar, and the large icon is used for
|
||||
the Atl-Tab task switcher.}
|
||||
the Alt-Tab task switcher.}
|
||||
|
||||
@item{Mac OS X --- both icons are ignored.}
|
||||
|
||||
|
|
|
@ -276,7 +276,7 @@ For a special keyword, the capitalization does not matter. However,
|
|||
capitalization is important for single-letter keynames. Furthermore,
|
||||
single-letter ASCII keynames are treated specially: @litchar["A"] and
|
||||
@litchar["s:a"] are both treated as @litchar["s:A"]. However, when
|
||||
@litchar["c:"] is inclued under Windows without @litchar["m:"], or when
|
||||
@litchar["c:"] is included under Windows without @litchar["m:"], or when
|
||||
@litchar["d:"] is included under Mac OS X, then ASCII letters are not
|
||||
upcased with @litchar["s:"], since the upcasing behavior of the Shift key
|
||||
is cancelled by Control without Alt (under Windows) or by Command
|
||||
|
|
|
@ -187,7 +187,7 @@ See also @scheme[write-resource].}
|
|||
Strips shortcut ampersands from @scheme[label], removes parenthesized
|
||||
ampersand--character combinations along with any surrounding space,
|
||||
and removes anything after a tab. Overall, it returns the label as it would
|
||||
appear on a button on a platform without support for menmonics.
|
||||
appear on a button on a platform without support for mnemonics.
|
||||
|
||||
}
|
||||
|
||||
|
|
|
@ -8,7 +8,7 @@ A @scheme[printer-dc%] object is a Windows or Mac OS X printer
|
|||
@scheme[exn:misc:unsupported] exception is raised).
|
||||
|
||||
Under Mac OS X, a newly created @scheme[printer-dc%] object obtains
|
||||
orientation (portrait versus landspace) and scaling information from
|
||||
orientation (portrait versus landscape) and scaling information from
|
||||
the current @scheme[ps-setup%] object, as determined by the
|
||||
@scheme[current-ps-setup] parameter. This information can be
|
||||
configured by the user through a dialog shown by
|
||||
|
|
|
@ -14,7 +14,7 @@ A @scheme[selectable-menu-item<%>] object is a
|
|||
@defmethod[(command [event (is-a?/c control-event%)])
|
||||
void?]{
|
||||
|
||||
Invoke's the menu item's callback procedure, which is supplied when an
|
||||
Invokes the menu item's callback procedure, which is supplied when an
|
||||
instance of
|
||||
@scheme[menu-item%] or
|
||||
@scheme[checkable-menu-item%] is created.
|
||||
|
@ -78,7 +78,7 @@ The shortcut key, as determined by @method[selectable-menu-item<%>
|
|||
|
||||
An empty list can be used for a shortcut prefix. However, the default
|
||||
@xmethod[frame% on-menu-char] method checks for menu shortcuts only
|
||||
when the key event includes either a non-Shift modifer or a Function
|
||||
when the key event includes either a non-Shift modifier or a Function
|
||||
key. Thus, an empty shortcut prefix is normally useful only if the
|
||||
shortcut key is a Function key.
|
||||
|
||||
|
|
|
@ -111,7 +111,7 @@ Returns @scheme[#f].
|
|||
void?]{
|
||||
|
||||
Tells the snip to blink the selection caret. This method is called
|
||||
periodically when the snips's editor's @techlink{display} has the
|
||||
periodically when the snip's editor's @techlink{display} has the
|
||||
keyboard focus, and the snip has the editor-local focus.
|
||||
|
||||
The drawing context and snip's @techlink{location}s in drawing context
|
||||
|
|
|
@ -1825,7 +1825,7 @@ Sets a paragraph-specific horizontal alignment. The alignment is only
|
|||
|
||||
@italic{This method is experimental.} It works reliably only when the
|
||||
paragraph is not merged or split. Merging or splitting a paragraph
|
||||
with alignment settings causes the settings to be transfered
|
||||
with alignment settings causes the settings to be transferred
|
||||
unpredictably (although other paragraphs in the editor can be safely
|
||||
split or merged). If the last paragraph in an editor is empty,
|
||||
settings assigned to it are ignored.
|
||||
|
|
|
@ -11,7 +11,7 @@ where doublequote and backslash characters within the string are
|
|||
escaped with backslashes. Other common string escapes are supported,
|
||||
including @litchar["\\n"] for a linefeed, @litchar["\\r"] for a
|
||||
carriage return, octal escapes using @litchar["\\"] followed by up
|
||||
to three octal digits, and hexadimal escapes with @litchar["\\u"]
|
||||
to three octal digits, and hexadecimal escapes with @litchar["\\u"]
|
||||
(up to four digits). Unprintable characters in a string are normally
|
||||
shown with @litchar["\\u"] when the string is printed.
|
||||
|
||||
|
|
|
@ -21,7 +21,7 @@ between scalar-value numbers and the corresponding character.
|
|||
|
||||
A printable character normally prints as @litchar["#\\"] followed
|
||||
by the represented character. An unprintable character normally prints
|
||||
as @litchar{#\u} followed by the scalar value as hexdecimal
|
||||
as @litchar{#\u} followed by the scalar value as hexadecimal
|
||||
number. A few characters are printed specially; for example, the space
|
||||
and linefeed characters print as @scheme[#\space] and
|
||||
@scheme[#\newline], respectively.
|
||||
|
|
|
@ -17,7 +17,7 @@ just like a @scheme[lambda] expression:
|
|||
|
||||
The @scheme[_superclass-expr] determines the superclass for the new
|
||||
class. Each @scheme[_decl-or-expr] is either a declaration related to
|
||||
methods, fields, and intialization arguments, or it is an expression
|
||||
methods, fields, and initialization arguments, or it is an expression
|
||||
that is evaluated each time that the class is instantiated. In other
|
||||
words, instead of a method-like constructor, a class has
|
||||
initialization expressions interleaved with field and method
|
||||
|
|
|
@ -140,7 +140,7 @@ constant propagation, constant folding, and inlining optimizations.
|
|||
@section[#:tag "tools"]{More Tools}
|
||||
|
||||
In the @seclink["intro"]{introduction}, we mentioned that PLT Scheme
|
||||
includes more tools bsides DrScheme and MzScheme:
|
||||
includes more tools besides DrScheme and MzScheme:
|
||||
|
||||
@itemize{
|
||||
|
||||
|
|
|
@ -186,7 +186,7 @@ through parallel lists in the first two (by-position) arguments,
|
|||
and then all by-position arguments from an application as the
|
||||
remaining by-position arguments.
|
||||
|
||||
@guideother{@secref["apply"] inroduces @scheme[keyword-apply].}
|
||||
@guideother{@secref["apply"] introduces @scheme[keyword-apply].}
|
||||
|
||||
@defexamples[
|
||||
(define (trace-wrap f)
|
||||
|
|
|
@ -177,7 +177,7 @@ results in a definition (see @secref["multiple-values"]),
|
|||
@specform[(letrec-values ([(id ...) expr] ...)
|
||||
body ...+)]
|
||||
|
||||
Each @scheme[_expr] must produce as many values as coresponding
|
||||
Each @scheme[_expr] must produce as many values as corresponding
|
||||
@scheme[_id]s. The binding rules are the same for the forms
|
||||
without @schemekeywordfont{-values} forms: the @scheme[_id]s of
|
||||
@scheme[let-values] are bound only in the @scheme[_body]s, the
|
||||
|
|
|
@ -25,7 +25,7 @@ parentheses wrapped around the printed form of the list
|
|||
elements. There's an opportunity for confusion here, because
|
||||
parentheses are used for both expressions, such as @scheme[(list "red"
|
||||
"green" "blue")], and printed results, such as @schemeresult[("red"
|
||||
"green" "blue")]. Rememeber that, in the documentation and in
|
||||
"green" "blue")]. Remember that, in the documentation and in
|
||||
DrScheme, parentheses for results are printed in blue, whereas
|
||||
parentheses for expressions are brown.
|
||||
|
||||
|
@ -107,7 +107,7 @@ functions. One reason is that @scheme[map], @scheme[ormap],
|
|||
@scheme[andmap], and @scheme[filter] cover the most common kinds of
|
||||
list loops.
|
||||
|
||||
Scheme provides a general @defterm{list compherension} form
|
||||
Scheme provides a general @defterm{list comprehension} form
|
||||
@scheme[for/list], which builds a list by iterating through
|
||||
@defterm{sequences}. List comprehensions and related iteration forms
|
||||
are described in see @secref["for"].
|
||||
|
@ -200,7 +200,7 @@ imagining how @scheme[(my-length (list "a" "b" "c"))] must evaluate:
|
|||
#,step 3
|
||||
]
|
||||
|
||||
For a list with @math{n} elements, evalution will stack up @math{n}
|
||||
For a list with @math{n} elements, evaluation will stack up @math{n}
|
||||
@scheme[(+ 1 ...)] additions, and then finally add them up when the
|
||||
list is exhausted.
|
||||
|
||||
|
|
|
@ -13,10 +13,10 @@ A Scheme @defterm{number} is either exact or inexact:
|
|||
|
||||
@itemize{
|
||||
|
||||
@item{an aribrarily large or small integer, such as @scheme[5],
|
||||
@item{an arbitrarily large or small integer, such as @scheme[5],
|
||||
@scheme[99999999999999999], or @scheme[-17];}
|
||||
|
||||
@item{a rational that is exactly the ratio of two arbitraily
|
||||
@item{a rational that is exactly the ratio of two arbitrarily
|
||||
small or large integers, such as @scheme[1/2],
|
||||
@scheme[99999999999999999/2], or @scheme[-3/4]; or}
|
||||
|
||||
|
@ -32,7 +32,7 @@ A Scheme @defterm{number} is either exact or inexact:
|
|||
|
||||
@item{an IEEE floating-point representation of a number, such
|
||||
as @scheme[2.0] or @scheme[3.14e87], where the IEEE
|
||||
infinitities and not-a-number are written
|
||||
infinities and not-a-number are written
|
||||
@scheme[+inf.0], @scheme[-inf.0], and @scheme[+nan.0]
|
||||
(or @schemevalfont{-nan.0}); or}
|
||||
|
||||
|
@ -50,8 +50,8 @@ exact numbers print as integers and fractions. The same conventions
|
|||
apply for reading number constants, but @litchar{#e} or
|
||||
@litchar{#i} can prefix a number to force its parsing as an exact
|
||||
or inexact number. The prefixes @litchar{#b}, @litchar{#o}, and
|
||||
@litchar{#x} specificy binary, octal, and hexadecimal
|
||||
interprertation of digits.
|
||||
@litchar{#x} specify binary, octal, and hexadecimal
|
||||
interpretation of digits.
|
||||
|
||||
@refdetails/gory["parse-number"]{the syntax of numbers}
|
||||
|
||||
|
|
|
@ -62,7 +62,7 @@ p
|
|||
p
|
||||
]
|
||||
|
||||
Among the most important predefined proecdures on lists are those that
|
||||
Among the most important predefined procedures on lists are those that
|
||||
iterate through the list's elements:
|
||||
|
||||
@interaction[
|
||||
|
|
|
@ -15,9 +15,9 @@ always human-readable, and not all sequences can be decoded to Unicode
|
|||
scalar values.
|
||||
|
||||
Despite the occasional encoding problems, most paths can be converted
|
||||
to and fom strings. Thus, procedures that accept a path argument
|
||||
to and from strings. Thus, procedures that accept a path argument
|
||||
always accept a string, and the printed form of a path uses the string
|
||||
decodin of the path inside @litchar{#<path:} and @litchar{>}. The
|
||||
decoding of the path inside @litchar{#<path:} and @litchar{>}. The
|
||||
@scheme[display] form of a path is the same as the @scheme[display]
|
||||
form of its string encodings.
|
||||
|
||||
|
@ -38,7 +38,7 @@ values, instead of strings.
|
|||
Although it's sometimes tempting to directly manipulate strings that
|
||||
represent filesystem paths, correctly manipulating a path can be
|
||||
surprisingly difficult. For example, if you start under Unix with the
|
||||
aboslute path @file{/tmp/~} and take just the last part, you end up
|
||||
absolute path @file{/tmp/~} and take just the last part, you end up
|
||||
with @file{~}---which looks like a reference to the current user's
|
||||
home directory, instead of a relative path to a file of directory
|
||||
named @file{~}. Windows path manipulation, furthermore, is far
|
||||
|
|
|
@ -14,7 +14,7 @@ optional, and it defaults to either the @defterm{current input port}
|
|||
or @defterm{current output port}. For @exec{mzscheme}, the current
|
||||
ports are initialized to the process's stdin and stdout. The
|
||||
@scheme[current-input-port] and @scheme[current-output-port]
|
||||
procedures, whien called with no arguments, return the current output
|
||||
procedures, when called with no arguments, return the current output
|
||||
and input port, respectively.
|
||||
|
||||
@examples[
|
||||
|
|
|
@ -95,7 +95,7 @@ not:
|
|||
(eval:alts (#, @scheme[quote] (0 #, @schemeparenfont{.} (1 . 2))) '(0 . (1 . 2)))
|
||||
]
|
||||
|
||||
Naturaly, lists can be nested:
|
||||
Naturally, lists can be nested:
|
||||
|
||||
@interaction[
|
||||
(list (list 1 2 3) 5 (list "a" "b" "c"))
|
||||
|
@ -110,7 +110,7 @@ that looks like an identifier:
|
|||
]
|
||||
|
||||
A value that prints like an identifier is a @defterm{symbol}. In the
|
||||
same way that parentehsized output should not be confused with
|
||||
same way that parenthesized output should not be confused with
|
||||
expressions, a printed symbol should not be confused with an
|
||||
identifier. In particular, the symbol @scheme[(#, @scheme[quote] #,
|
||||
@schemeidfont{map})] has nothing to do with the @schemeidfont{map}
|
||||
|
@ -238,7 +238,7 @@ conversion enables a kind of general infix notation:
|
|||
'(1 . < . 2)
|
||||
]
|
||||
|
||||
This two-dot convension is non-traditional, and it has essentially
|
||||
This two-dot convention is non-traditional, and it has essentially
|
||||
nothing to do with the dot notation for non-list pairs. PLT Scheme
|
||||
programmers use the infix convension sparingly---mostly for asymmetric
|
||||
programmers use the infix convention sparingly---mostly for asymmetric
|
||||
binary operators such as @scheme[<] and @scheme[is-a?].
|
||||
|
|
|
@ -5,7 +5,7 @@
|
|||
|
||||
@title[#:tag "vectors"]{Vectors}
|
||||
|
||||
A @defterm{vector} is a fixed-length array of arbitarary
|
||||
A @defterm{vector} is a fixed-length array of arbitrary
|
||||
values. Unlike a list, a vector supports constant-time access and
|
||||
update of its elements.
|
||||
|
||||
|
|
Loading…
Reference in New Issue
Block a user