typos
svn: r66
This commit is contained in:
parent
317e7fd1f8
commit
daa18fcba0
|
@ -25,7 +25,7 @@ specification in the following minor ways:
|
|||
* identifiers cannot contain whitespace;
|
||||
|
||||
* argument separators are constrained to be identifiers (i.e., they
|
||||
cannot be keywords, and they cannot consistnt of multiple
|
||||
cannot be keywords, and they cannot consistent of multiple
|
||||
identifiers separated by whitespace); and
|
||||
|
||||
* numbers containing exponents (using the "10" subscript) are not
|
||||
|
|
|
@ -105,7 +105,7 @@ The html-eval-ok parameter controls the evaluation of
|
|||
----------------------------------------
|
||||
|
||||
> (hyper-text-mixin text%) - Extends the given text% class. The
|
||||
initializtion arguments are extended with a four new first
|
||||
initialization arguments are extended with a four new first
|
||||
arguments: a url or a port to be loaded into the text% object, a
|
||||
top-level-window or #f to use as a parent for status dialogs, a
|
||||
progress procedure used as for `get-url', and either #f or a post
|
||||
|
@ -185,7 +185,7 @@ The html-eval-ok parameter controls the evaluation of
|
|||
|
||||
> hyper-text% = (hyper-text-mixin text:keymap%)
|
||||
|
||||
This is an extension of the keymap class, to support standard keybindings
|
||||
This is an extension of the keymap class, to support standard key bindings
|
||||
in the browser window. It adds the following method:
|
||||
|
||||
> get-hyper-keymap :: (send o get-hyper-keymap) -> keymap% object
|
||||
|
@ -195,7 +195,7 @@ The html-eval-ok parameter controls the evaluation of
|
|||
----------------------------------------
|
||||
|
||||
> (hyper-canvas-mixin editor-canvas%) - Extends the given
|
||||
editor-canvas% class. The intialization arguments are unchanged.
|
||||
editor-canvas% class. The initialization arguments are unchanged.
|
||||
|
||||
The canvas's parent should be an instance of a class derived with
|
||||
`hyper-panel-mixin' (described below).
|
||||
|
@ -215,7 +215,7 @@ The html-eval-ok parameter controls the evaluation of
|
|||
editor-canvas may not be an instance of this class.
|
||||
|
||||
> current-page :: (send o current-page)
|
||||
Returns a reprsentation of the currently displayed page, which
|
||||
Returns a representation of the currently displayed page, which
|
||||
includes a particular editor and a visible range within the
|
||||
editor.
|
||||
|
||||
|
@ -273,7 +273,7 @@ The html-eval-ok parameter controls the evaluation of
|
|||
|
||||
|
||||
> make-control-bar-panel :: (send o make-control-bar-panel container)
|
||||
Create's the panel's sub-container for the control bar containing
|
||||
Creates the panel's sub-container for the control bar containing
|
||||
the navigation buttons. If #f is returned, the panel will have no
|
||||
control bar. The default method instantiates horizontal-panel%.
|
||||
|
||||
|
@ -295,7 +295,7 @@ The html-eval-ok parameter controls the evaluation of
|
|||
This method is called by the hypertext canvas to notify the
|
||||
panel that the hypertext page changed. The `page' is #f
|
||||
if `new-page' is the first page for the canvas. See also
|
||||
`page->editor' (decsribed below).
|
||||
`page->editor' (described below).
|
||||
|
||||
> filter-notes :: (send o filter-notes list-of-strings)
|
||||
Given the notes from a page as a list of strings (where
|
||||
|
@ -352,7 +352,7 @@ init arg text to follow the corresponding link.
|
|||
|
||||
The _browser-unit.ss_ library in the "browser" collection is a
|
||||
unitized version of the code documented above. It imports unit
|
||||
matching thefollowing signatures:
|
||||
matching the following signatures:
|
||||
|
||||
setup:plt-installer^
|
||||
mred^
|
||||
|
@ -405,7 +405,7 @@ An interface that extends text% with the following methods:
|
|||
> (html-text-mixin text%-subclass) -> html-text<%> implementation
|
||||
|
||||
Extends the given text% class with implementations of the html-text<%>
|
||||
methods. Hyperlinks are attched to clickbacks that use `send-url'
|
||||
methods. Hyperlinks are attached to clickbacks that use `send-url'
|
||||
(from the "sendurl.ss" library of the "net" collection).
|
||||
|
||||
> (render-html-to-text input-port html-text<%>-obj load-img? eval-mz?)
|
||||
|
|
|
@ -208,7 +208,7 @@ The compiler unit loads certain tools on demand via `dynamic-require'
|
|||
and `get-info'. If the namespace used during compilation is different
|
||||
from the namespace used to load the compiler, or if other load-related
|
||||
parameters are set, then the following parameter can be used to
|
||||
restore settings for `dyanmic-require'.
|
||||
restore settings for `dynamic-require'.
|
||||
|
||||
> current-compiler-dynamic-require-wrapper
|
||||
|
||||
|
@ -249,7 +249,7 @@ _option.ss_ module. Options are set by the following parameters:
|
|||
Default = #f.
|
||||
|
||||
> propagate-constants - #t improves the code by
|
||||
propogating constants. Default = #t.
|
||||
propagating constants. Default = #t.
|
||||
|
||||
> assume-primitives - #t equates X with #%X when
|
||||
#%X exists. This is useful only with non-unitized code.
|
||||
|
@ -260,8 +260,8 @@ _option.ss_ module. Options are set by the following parameters:
|
|||
|
||||
> vehicles - Controls how closures are compiled. The
|
||||
possible values are: 'vehicles:automatic - auto-groups
|
||||
'vehicles:functions - groups by procedue
|
||||
'vechicles:units - groups by unit
|
||||
'vehicles:functions - groups by procedure
|
||||
'vehicles:units - groups by unit
|
||||
'vehicles:monolithic - groups randomly
|
||||
Default = 'vehicles:automatic.
|
||||
|
||||
|
@ -304,7 +304,7 @@ The _compiler-unit.ss_ library provides a unit/sig
|
|||
matching the signature
|
||||
> compiler^
|
||||
which provides the compiler.ss functions. This signature and all
|
||||
auxilliary signatures needed by compiler@ are defined by the
|
||||
auxiliary signatures needed by compiler@ are defined by the
|
||||
_sig.ss_ library.
|
||||
|
||||
The signed unit requires the following imports:
|
||||
|
@ -402,20 +402,20 @@ _embedr-sig.ss_ library provides the signature, _compiler:embed^_.
|
|||
See the mzc documentation for a simpler interface that is
|
||||
well-suited to programs defined with `module'.
|
||||
|
||||
The embeddeding executable is written to `dest', which is
|
||||
The embedding executable is written to `dest', which is
|
||||
overwritten if it exists already (as a file or directory).
|
||||
|
||||
The embedded code consists of module declaratons followed by
|
||||
The embedded code consists of module declarations followed by
|
||||
additional (arbitrary) code. When a module is embedded, every module
|
||||
that it imports is also embedded. Library modules are embedded so
|
||||
that they are accessible via their `lib' paths in the initial
|
||||
namespace' except as specified in `mod-list', other modules
|
||||
(accessed via local paths and absolte paths) are embedded with a
|
||||
(accessed via local paths and absolute paths) are embedded with a
|
||||
generated prefix, so that they are not directly accessible.
|
||||
|
||||
The `mod-list' argument designates modules to be embedded, as
|
||||
described below. The `literal-file-list' and `literal-sexp'
|
||||
arguments specifiy literal code to be copied into the executable:
|
||||
arguments specify literal code to be copied into the executable:
|
||||
the content of each file in `literal-file-list' is copied in order
|
||||
(with no intervening space), followed by `literal-sexp'. The
|
||||
`literal-file-list' files or `literal-sexp' can contain compiled
|
||||
|
@ -451,7 +451,7 @@ _embedr-sig.ss_ library provides the signature, _compiler:embed^_.
|
|||
executable has a chance to see an embedded declaration of (lib
|
||||
"mred.ss" "mred"). Then, if the literal code expect to have MrEd and
|
||||
the class library required into the top-level namespace, literal
|
||||
`require's for thoselibraries should be included at the start.
|
||||
`require's for those libraries should be included at the start.
|
||||
|
||||
The optional `aux' argument is an association list for
|
||||
platform-specific options (i.e., it is a list of pairs where the
|
||||
|
|
|
@ -167,7 +167,7 @@ _file.ss_
|
|||
|
||||
> (extract-base-filename/ss s program) - strips the Scheme file suffix
|
||||
from the path/string s and returns a stripped path. If s is not a
|
||||
Scheme file name and `program' is a symbol, and error is signalled.
|
||||
Scheme file name and `program' is a symbol, and error is signaled.
|
||||
If s is not a Scheme file and `program' is #f, #f is returned. The
|
||||
`program' argument is optional and defaults to #f.
|
||||
|
||||
|
|
|
@ -6,7 +6,7 @@
|
|||
|
||||
The embedded gui collection provides a class hierarchy for
|
||||
creating graphical boxes within mred's editors with geometry
|
||||
managment that mirrors that of vertical-panel% and
|
||||
management that mirrors that of vertical-panel% and
|
||||
horizontal-panel%
|
||||
|
||||
============================================================
|
||||
|
@ -125,7 +125,7 @@ Whether or not the snip can be stretched in the Y dimension
|
|||
============================================================
|
||||
|
||||
_dllist<%>_ is an interface which makes a class a
|
||||
doublly-linked list and requires the following methods
|
||||
doubly-linked list and requires the following methods
|
||||
|
||||
> (send a-dlllist next) -> (is-a?/c dllist<%>)
|
||||
|
||||
|
@ -159,7 +159,7 @@ of the dllist.
|
|||
============================================================
|
||||
|
||||
_vertical-alignment%_ and _horizontal-alignment%_ are
|
||||
geometry managment classes of the embedded-gui toolkit. They
|
||||
geometry management classes of the embedded-gui toolkit. They
|
||||
implement alignment<%> and alignment-parent<%> and are
|
||||
instantiated as follows
|
||||
|
||||
|
@ -248,7 +248,7 @@ wide as is required to display the longest string in labels.
|
|||
_vline%_ and _hline%_ are two graphical elements of the
|
||||
alignment<%> hierarchy that display a vertical or horizontal
|
||||
line across the region they are inserted into. They implement
|
||||
alingment<%>.
|
||||
alignment<%>.
|
||||
|
||||
> (new vline% (parent _))
|
||||
parent : (is-a?/c alignment-parent<%>)
|
||||
|
@ -286,7 +286,7 @@ The thunk to execute when tabbing back
|
|||
============================================================
|
||||
|
||||
_tabbable-text-mixin_ gives a text% the tabbable-text<%>
|
||||
interface and gives it keybindings to tab ahead and back.
|
||||
interface and gives it key bindings to tab ahead and back.
|
||||
|
||||
============================================================
|
||||
|
||||
|
@ -308,13 +308,13 @@ and must be locked separately.
|
|||
============================================================
|
||||
|
||||
The _single-line-text-mixin_ restricts a text to one line by
|
||||
overriding its keybidings to do nothing on enter.
|
||||
overriding its key bindings to do nothing on enter.
|
||||
|
||||
============================================================
|
||||
|
||||
The _cue-text-mixin_ gives a text% an instantiation argument
|
||||
of a string that is displayed in the text% initially in grey.
|
||||
This text dissappears when the text gets focus. This is
|
||||
This text disappears when the text gets focus. This is
|
||||
useful for labeling texts without needing to take up space.
|
||||
|
||||
_cue-text%_ is (cue-text-mixin text%)
|
||||
|
@ -359,7 +359,7 @@ The pasteboard that contains the snip
|
|||
snip : (is-a?/c snip%)
|
||||
|
||||
The application of f on all snips from snip to the end in a
|
||||
foldl foldr mannor
|
||||
foldl foldr manner
|
||||
|
||||
> (for-each-snip f first-snip init-lists ...) -> void
|
||||
f : ((is-a?/c snip%) . -> . void)
|
||||
|
@ -378,9 +378,9 @@ A list of f applied to each snip
|
|||
> (stretchable-width? snip) -> boolean?
|
||||
snip : (is-a?/c snip%)
|
||||
|
||||
True if the snip can be resized in the x dimention
|
||||
True if the snip can be resized in the x dimension
|
||||
|
||||
> (stretchable-height? snip) -> boolean?
|
||||
snip : (is-a?/c snip%)
|
||||
|
||||
True if the snip can be resized in the y dimention
|
||||
True if the snip can be resized in the y dimension
|
||||
|
|
|
@ -13,7 +13,7 @@ Differences from the book:
|
|||
expressions. This constraint enables better and earlier error
|
||||
reporting.
|
||||
|
||||
Some examples in the book's code (or at least the code dstributed
|
||||
Some examples in the book's code (or at least the code distributed
|
||||
for the book) must be changed by moving datatype definitions
|
||||
earlier.
|
||||
|
||||
|
@ -108,7 +108,7 @@ Differences from the book:
|
|||
> eopl:error-stop
|
||||
|
||||
Defined only in the top-level namespace (i.e., not in a module);
|
||||
mutate this varable to install an exception-handling
|
||||
mutate this variable to install an exception-handling
|
||||
thunk. Typically, the handler thunk escapes through a continuation.
|
||||
|
||||
The "eopl.ss" module sets this variable to #f in the current
|
||||
|
|
|
@ -145,7 +145,7 @@ To retrieve all profiling information accumulated so far, call
|
|||
|
||||
* a list of call paths, recorded while `profile-paths-enabled' is
|
||||
set to #t. Each call path is a list containing two-element lists;
|
||||
each two-element list contains the calling proceure's name or
|
||||
each two-element list contains the calling procedure's name or
|
||||
source expression and the calling procedure's source file or #f.
|
||||
|
||||
Depending of the source program, profiling usually induces a factor of
|
||||
|
@ -173,7 +173,7 @@ counting):
|
|||
instrumentation
|
||||
|
||||
> (get-execute-counts) - returns a list of pairs, one for each
|
||||
instrucmented expression. The first element of the pair is a syntax
|
||||
instrumented expression. The first element of the pair is a syntax
|
||||
object (usually containing source location information) for the
|
||||
original expression, and the second element of the pair is the
|
||||
number of times that the expression has been evaluated.
|
||||
|
@ -241,7 +241,7 @@ expression (#f).
|
|||
The `st-mark-source' and `st-mark-bindings' functions extract
|
||||
information from a particular kind of value. The value must
|
||||
be created by `make-st-mark'. `st-mark-source' extracts
|
||||
the value originally provided to the expresion-maker, and
|
||||
the value originally provided to the expression-maker, and
|
||||
`st-mark-bindings' returns local binding information (if available).
|
||||
|
||||
The import signature contains these names:
|
||||
|
|
|
@ -1,5 +1,5 @@
|
|||
|
||||
Finish Install is for Mac OS X.
|
||||
Finish Install is for Mac OS X and Windows.
|
||||
|
||||
The launcher (which does not embed a path to the original executable) runs the
|
||||
"install" script in the same directory as the launcher. The collection itself
|
||||
|
|
|
@ -1,6 +1,6 @@
|
|||
** To play _Aces_, run the "Games" application. **
|
||||
|
||||
Aces is a solitare card game. The object is to remove all of the cards
|
||||
Aces is a solitaire card game. The object is to remove all of the cards
|
||||
from the board, except the four Aces.
|
||||
|
||||
Remove a card by clicking it. You may remove a card when two
|
||||
|
|
|
@ -10,7 +10,7 @@ The _cards.ss_ module defines the following procedures:
|
|||
> (make-table [title-string] [w] [h]) returns a table named by
|
||||
`title-string' that is `w' cards wide and `h' cards high. A
|
||||
table is an frame% object, with extra methods described
|
||||
below. The table is not intially shown; (send table show #t)
|
||||
below. The table is not initially shown; (send table show #t)
|
||||
shows it. The arguments are optional, with the default values
|
||||
being "Cards", 7, and 3.
|
||||
|
||||
|
@ -178,7 +178,7 @@ Table methods: [in addition to standard frame% methods]
|
|||
for animation)
|
||||
|
||||
> unhilite-region :: (send t unhilite-region r) - manual unhilite
|
||||
(usually for anaimation)
|
||||
(usually for animation)
|
||||
|
||||
|
||||
> set-button-action :: (send t set-button-action which action) - sets
|
||||
|
@ -211,7 +211,7 @@ Table methods: [in addition to standard frame% methods]
|
|||
> set-single-click-action :: (send t set-single-click-action proc) -
|
||||
sets the procedure to be called when a card is single-clicked,
|
||||
after the button action is initiated. (If the card is
|
||||
double-clicked, this action is inoked for the first click,
|
||||
double-clicked, this action is invoked for the first click,
|
||||
then the double-click action is invoked.) The default action
|
||||
does nothing.
|
||||
|
||||
|
|
|
@ -92,11 +92,11 @@ used:
|
|||
unit (see MzLib's `unit' form); the unit is invoked with no
|
||||
imports to start the game.
|
||||
|
||||
* `name' [defauls to the collection name] : used to label the
|
||||
* `name' [defaults to the collection name] : used to label the
|
||||
game-starting button in the game console.
|
||||
|
||||
* `game-icon' [defaults to collection name with ".png"] : used as a
|
||||
path to a bitmap file taht is used for the game button's label;
|
||||
path to a bitmap file that is used for the game button's label;
|
||||
this image should be 32 x 32 and have a mask.
|
||||
|
||||
* `game-set' [defaults to "Other Games"] : a label used to group
|
||||
|
@ -135,6 +135,6 @@ displaying a help window.
|
|||
- Any line that contains only "-"s and is as long as the previous
|
||||
line causes the previous line to be formatted as a title.
|
||||
|
||||
- Other lines are pargraph-flowed to fit the window.
|
||||
- Other lines are paragraph-flowed to fit the window.
|
||||
|
||||
The `verbatim?' argument is optional, and it defaults to #f.
|
||||
|
|
|
@ -61,7 +61,7 @@ A gl-board object is constructed as follows:
|
|||
The min-x, max-x, min-y, and max-y parameters all specify the dimensions of
|
||||
the board. They are used to setup viewing parameters. The board is viewed
|
||||
centered around the center of the coordinates, and the view attempts to fill
|
||||
the window to them. The optional theta and phi arguments determine the intitial
|
||||
the window to them. The optional theta and phi arguments determine the initial
|
||||
rotation of the board, with respective defaults 45 and 0; theta corresponds to
|
||||
the up and down keys, and phi corresponds to the left and right keys.
|
||||
|
||||
|
|
|
@ -16,7 +16,7 @@ Game Rules
|
|||
The 3x3 game is a generalization of tic-tac-toe:
|
||||
|
||||
* The object of the game is to get three in a row of your color,
|
||||
vetically, horizontally, or diagonally. Size doesn't matter for
|
||||
vertically, horizontally, or diagonally. Size doesn't matter for
|
||||
determining a winner.
|
||||
|
||||
* Each player (red or yellow) starts with 6 pieces: two large, two
|
||||
|
@ -30,7 +30,7 @@ The 3x3 game is a generalization of tic-tac-toe:
|
|||
placed/moved on top of a smaller piece already on the board,
|
||||
"gobbling" the smaller piece. The smaller piece does not have to be
|
||||
an opponent's piece, and the smaller piece may itself have gobbled
|
||||
another piece previouly.
|
||||
another piece previously.
|
||||
|
||||
* Only visible pieces can be moved, and only visible pieces count
|
||||
toward winning. Gobbled pieces stay on the board, however, and when
|
||||
|
@ -82,8 +82,8 @@ slightly different way than zooming.) Depending on how keyboard focus
|
|||
works on your machine, you may have to click the board area to make
|
||||
these controls work.
|
||||
|
||||
The button labelled "<" at the bottom of the window rewinds the game
|
||||
by one turn. The button labelled ">" re-plays one turn in a rewound
|
||||
The button labeled "<" at the bottom of the window rewinds the game
|
||||
by one turn. The button labeled ">" re-plays one turn in a rewound
|
||||
game. An alternate move can be made at any point in a rewound game,
|
||||
replacing the old game from that point on.
|
||||
|
||||
|
|
|
@ -17,7 +17,7 @@ turn, click on one of the numbers surrounding the board to move.
|
|||
The left and right arrows above the board undo and redo moves,
|
||||
respectively. The right side of the window shows the game played so
|
||||
far, including undone moves that have not yet been replaced. The most
|
||||
recent move is hilighted in blue.
|
||||
recent move is highlighted in blue.
|
||||
|
||||
When a player loses by repeating a previous board configuration, the
|
||||
player's pieces turn red and no further moves are allowed (although
|
||||
|
|
|
@ -1,6 +1,6 @@
|
|||
** To play _Spider_, run the "Games" application. **
|
||||
|
||||
Spider is a solitare card game played with 104 cards. The cards can
|
||||
Spider is a solitaire card game played with 104 cards. The cards can
|
||||
include either a single suit, two suits, or four suites. (Choose your
|
||||
variant through the "Options" item in the "Edit" menu.)
|
||||
|
||||
|
|
|
@ -154,7 +154,7 @@ host the server. This directory contains the following files and
|
|||
sub-directories:
|
||||
|
||||
* server-cert.pem --- the server's certificate. To create a
|
||||
ceritificate and key with openssl:
|
||||
certificate and key with openssl:
|
||||
|
||||
openssl req -new -nodes -x509 -days 365 -out server-cert.pem
|
||||
-keyout private-key.pem
|
||||
|
@ -182,7 +182,7 @@ sub-directories:
|
|||
the default is 300
|
||||
|
||||
'session-memory-limit : maximum size in bytes of memory allowed
|
||||
for per-session comuptation, if per-session limits are
|
||||
for per-session computation, if per-session limits are
|
||||
supported (i.e., when using MrEd3m and MzScheme3m with memory
|
||||
accounting); the default is 40000000
|
||||
|
||||
|
@ -247,7 +247,7 @@ sub-directories:
|
|||
contains a copy of the student's definitions and interactions
|
||||
windows. The file is in a binary format (to support non-text
|
||||
code), and opening the file directly in DrScheme shows the
|
||||
definitions part. To get both the defintions and interactions
|
||||
definitions part. To get both the definitions and interactions
|
||||
parts, the file can be parsed with `unpack-submission' from
|
||||
"utils.ss" (see below).
|
||||
|
||||
|
@ -280,7 +280,7 @@ sub-directories:
|
|||
* log.ss (created if not present, appended otherwise) --- records
|
||||
connections and actions, where each entry is of the form
|
||||
(id time-str msg-str)
|
||||
and `id' is an integer reprsenting the connection (numbered
|
||||
and `id' is an integer representing the connection (numbered
|
||||
consecutively from 1 when the server starts) or 0 for a message
|
||||
for server without a connection.
|
||||
|
||||
|
@ -304,7 +304,7 @@ requires MrEd (which means that `checker' modules will likely require
|
|||
the server to run under MrEd).
|
||||
|
||||
The server currently provides no mechanism for a graceful shutdown,
|
||||
but terminiating the server is no worse than a network outage. (In
|
||||
but terminating the server is no worse than a network outage. (In
|
||||
particular, no data should be lost.) To reconfigure the server (e.g.,
|
||||
to change the set of active assignments), stop it and restart it.
|
||||
|
||||
|
@ -332,7 +332,7 @@ that runs concurrently with the handin server. The starting URL is
|
|||
|
||||
https://SERVER:PORT/servlets/status.ss
|
||||
|
||||
to obtain a list of all assingments, or
|
||||
to obtain a list of all assignments, or
|
||||
|
||||
https://SERVER:PORT/servlets/status.ss?handin=ASSIGNMENT
|
||||
|
||||
|
@ -428,7 +428,7 @@ The _utils.ss_ module provides utilities helpful in implementing
|
|||
|
||||
> (current-run-status string-or-#f) - registers information about the
|
||||
current actions of the checker, in case the session is terminated
|
||||
due to excessive memory consumption. For example, a cccchecker might
|
||||
due to excessive memory consumption. For example, a checker might
|
||||
set the status to indicate which instructor-supplied test was being
|
||||
executed when the session ran out of memory. This status is only
|
||||
used when per-session memory limits are supported (i.e., under
|
||||
|
|
|
@ -147,7 +147,7 @@ _Search functions_
|
|||
|
||||
> do-search : search-string num bool bool val f1 f2 f3 f4 -> (union string #f)
|
||||
|
||||
Peforms a search for `search-string' in the documentation, and returns either
|
||||
Performs a search for `search-string' in the documentation, and returns either
|
||||
a string containing HTML or #f. More details are provided in the file
|
||||
search.ss in the private subdirectory of the help collection.
|
||||
|
||||
|
@ -180,7 +180,7 @@ documentation.
|
|||
> (finddoc manual index-key label)
|
||||
This procedure accepts three strings. The first is the name of
|
||||
a doc collection, the second is an index entry in that manual, and
|
||||
the final is a desriptive string. It returns a string representation
|
||||
the final is a descriptive string. It returns a string representation
|
||||
of an anchor (in HTML) that points to that index entry in the manual.
|
||||
If the manual is not found, or the index-key is not in the manual,
|
||||
it returns html code that shows an error. Because the link is
|
||||
|
@ -228,7 +228,7 @@ _Creating Help Desk Documentation in doc.txt files_
|
|||
===================================================
|
||||
|
||||
Help Desk reads doc.txt files that are named by info.ss
|
||||
files (in PLaneT, or in collections or thier
|
||||
files (in PLaneT, or in collections or their
|
||||
subcollections). The info.ss file should have a line:
|
||||
|
||||
(define doc.txt "filename.txt")
|
||||
|
@ -271,7 +271,7 @@ Note that a search on "list" will not reveal this entry, because
|
|||
"cons" is used as the key, not the whole S-expression.
|
||||
|
||||
To create a keyword entry where the key is *not* the leftmost symbol
|
||||
in the S-expression, use the follwing form:
|
||||
in the S-expression, use the following form:
|
||||
|
||||
> keyword :: S-expression
|
||||
|
||||
|
@ -296,7 +296,7 @@ Help Desk looks for html documentation in two places:
|
|||
for html documentation (the paths are treated as
|
||||
relative to the location of the info.ss file)Ï
|
||||
|
||||
2) Help Desk aslo looks inside each sub-directory in any
|
||||
2) Help Desk also looks inside each sub-directory in any
|
||||
`doc' collection (Help Desk searches all doc
|
||||
collections, not just the first one, unlike
|
||||
`collection-path'). For example, the MzScheme manual is
|
||||
|
@ -331,7 +331,7 @@ five values:
|
|||
* HTML file - a file name relative to the manual's directory, e.g.,
|
||||
"node198.htm"
|
||||
|
||||
* HTML label - a string reprsenting a label within the HTML file
|
||||
* HTML label - a string representing a label within the HTML file
|
||||
|
||||
* page title - a string presenting the title of the HTML page, e.g.,
|
||||
"List Procedures"
|
||||
|
@ -350,7 +350,7 @@ Each index entry is a list of four values:
|
|||
* HTML file - a file name (represented as a bytes)
|
||||
relative to the manual's directory, e.g., #"node198.htm"
|
||||
|
||||
* HTML label - a string reprsenting a label within the HTML file
|
||||
* HTML label - a string representing a label within the HTML file
|
||||
|
||||
* page title - a string presenting the title of the HTML page, e.g.,
|
||||
"How to Create Help Desk Documents"
|
||||
|
@ -373,5 +373,5 @@ The _'help-desk-message field_ of the _info.ss_ file
|
|||
This field must be a string that is displayed at the top of the Help Desk
|
||||
results window, in green, when the doc.txt file of this collection is displayed.
|
||||
It should be a single line, describing how to load the library with a prefix
|
||||
specifing the applicable language levels.
|
||||
specifying the applicable language levels.
|
||||
|
||||
|
|
|
@ -29,7 +29,7 @@ New methods:
|
|||
|
||||
> new-item :: (send a-list new-item mixin) - creates and returns
|
||||
a new (empty) hierarchical-list-item<%>, but first, applies
|
||||
`mixin' to a class implemeting hierarchical-list-item<%> and uses
|
||||
`mixin' to a class implementing hierarchical-list-item<%> and uses
|
||||
the result as the class for the new hierarchical-list-item<%>
|
||||
object.
|
||||
|
||||
|
@ -43,7 +43,7 @@ New methods:
|
|||
|
||||
> new-list :: (send a-list new-list mixin) - creates and returns
|
||||
a new (empty) hierarchical-list-compound-item<%>, but first,
|
||||
applies `mixin' to a class implemeting
|
||||
applies `mixin' to a class implementing
|
||||
hierarchical-list-compound-item<%> and uses the result as the
|
||||
class for the new hierarchical-list-compound-item<%> object.
|
||||
|
||||
|
@ -138,7 +138,7 @@ New methods:
|
|||
|
||||
> get-clickable-snip :: (send an-item get-clickable-snip) -
|
||||
returns the snip that (when clicked) selects this element in
|
||||
the list. This is intended for use with the autmatic test
|
||||
the list. This is intended for use with the automatic test
|
||||
suite.
|
||||
|
||||
> get-allow-selection? :: (send an-item get-allow-selection?) -
|
||||
|
@ -147,7 +147,7 @@ New methods:
|
|||
to be selected.
|
||||
|
||||
> set-allow-selection :: (send an-item set-allow-selection boolean) -
|
||||
deteremines if this item is allowed to be selected
|
||||
determines if this item is allowed to be selected
|
||||
|
||||
--------------------------------------------------
|
||||
|
||||
|
@ -161,7 +161,7 @@ New methods:
|
|||
|
||||
> new-item :: (send a-list-item new-item mixin) - creates and returns
|
||||
a new (empty) hierarchical-list-item<%>, but first, applies
|
||||
`mixin' to a class implemeting hierarchical-list-item<%> and uses
|
||||
`mixin' to a class implementing hierarchical-list-item<%> and uses
|
||||
the result as the class for the new hierarchical-list-item<%>
|
||||
object.
|
||||
|
||||
|
@ -175,7 +175,7 @@ New methods:
|
|||
|
||||
> new-list :: (send a-list-item new-list mixin) - creates and returns
|
||||
a new (empty) hierarchical-list-compound-item<%>, but first,
|
||||
applies `mixin' to a class implemeting
|
||||
applies `mixin' to a class implementing
|
||||
hierarchical-list-compound-item<%> and uses the result as the
|
||||
class for the new hierarchical-list-compound-item<%> object.
|
||||
|
||||
|
|
|
@ -51,7 +51,7 @@ executables.
|
|||
one for each type of file handled by the application;
|
||||
each association is a 2-element list, where the first (key)
|
||||
element is a string recognized by Finder, and the second
|
||||
element is a plist value (see doc.tx in the "xml" collection);
|
||||
element is a plist value (see doc.txt in the "xml" collection);
|
||||
see plt/collects/drscheme/drscheme.filetypes for an example.
|
||||
|
||||
-'resource-files_ (Mac OS X) - extra files to copy into the
|
||||
|
@ -107,12 +107,12 @@ executables.
|
|||
|
||||
|
||||
> (install-mred-program-launcher file collection name) - Calls
|
||||
`make-mred-launcher' with the destintation returned by
|
||||
`make-mred-launcher' with the destination returned by
|
||||
(mred-program-launcher-path name); the `file' and `collection'
|
||||
arguments are passed on to `make-mred-launcher'.
|
||||
|
||||
> (install-mzscheme-program-launcher file collection name) - Calls
|
||||
`make-mzscheme-launcher' with the destintation returned by
|
||||
`make-mzscheme-launcher' with the destination returned by
|
||||
(mzscheme-program-launcher-path name); the `file' and `collection'
|
||||
arguments are passed on to `make-mzscheme-launcher'.
|
||||
|
||||
|
@ -123,7 +123,7 @@ executables.
|
|||
".exe" suffix is automatically appended to `name'. For Unix, `name'
|
||||
is changed to lowercase, whitespace is changed to `-', and the path
|
||||
includes the bin subdirectory of the PLT home directory. For Mac OS
|
||||
X, the ".app" suffix is appened to `name'.
|
||||
X, the ".app" suffix is appended to `name'.
|
||||
|
||||
> (mzscheme-program-launcher-path name) returns the same pathname as
|
||||
(mred-program-launcher-path name) for Unix, Windows, and Mac OS Classic.
|
||||
|
|
|
@ -1,9 +1,9 @@
|
|||
_Overview of make_
|
||||
------------------
|
||||
|
||||
This library provides a Scheme version of the standard unix
|
||||
This library provides a Scheme version of the standard Unix
|
||||
`make' utility. Its syntax is intended to simulate regular
|
||||
unix make in Scheme.
|
||||
Unix make in Scheme.
|
||||
|
||||
If you are already familiar with make, skip down the precise
|
||||
details of the make collection. This section contains a
|
||||
|
@ -11,7 +11,7 @@ brief overview of make. The idea is to explain how to
|
|||
generate some project you have from a collection of source
|
||||
files that go through several stages of processing.
|
||||
|
||||
For example, lets say that you are writing soem project that
|
||||
For example, lets say that you are writing some project that
|
||||
has three input files (that you create and maintain) called
|
||||
a.input, b.input, and c.input. Further, there are two stages
|
||||
of processing -- first you run a particular tool
|
||||
|
@ -39,7 +39,7 @@ several lines that tell `make' how to create each piece. The
|
|||
first two lines say that a.output depends on a.input and the
|
||||
command for making a.output from a.input is
|
||||
|
||||
make-output a.input a.ouput
|
||||
make-output a.input a.output
|
||||
|
||||
The point of this exercise is that the `make' utility looks
|
||||
at the file creation dates of the various files and only
|
||||
|
@ -59,9 +59,9 @@ Here's the equivalent Scheme program:
|
|||
...)
|
||||
|
||||
(make
|
||||
(("a.ouput" ("a.input") (make-output "a.output" "a.input"))
|
||||
("b.ouput" ("b.input") (make-output "b.output" "b.input"))
|
||||
("c.ouput" ("c.input") (make-output "c.output" "c.input"))
|
||||
(("a.output" ("a.input") (make-output "a.output" "a.input"))
|
||||
("b.output" ("b.input") (make-output "b.output" "b.input"))
|
||||
("c.output" ("c.input") (make-output "c.output" "c.input"))
|
||||
("total" ("a.output" "b.output" "c.output")
|
||||
(combine-total "a.output" "b.output" "c.output")))
|
||||
|
||||
|
@ -119,20 +119,20 @@ the target(s), and the `orig-exn' field is the original
|
|||
exception.
|
||||
|
||||
The maker.ss library is a signed unit that requires no
|
||||
imports and provdes `make/proc'.
|
||||
imports and provides `make/proc'.
|
||||
|
||||
make.ss also provides the following parameters:
|
||||
|
||||
> (make-print-checking [on?]) - If #f, make only prints when
|
||||
it is making a target. Otherwise, it prints when it is
|
||||
checking the dependancies of a target. Defaultly #t.
|
||||
checking the dependencies of a target. Default: #t.
|
||||
|
||||
> (make-print-dep-no-line [on?]) - If #f, make only prints
|
||||
"checking..." lines for dependancies that have a
|
||||
corresponding make line. Defaultly #f.
|
||||
"checking..." lines for dependencies that have a
|
||||
corresponding make line. Default: #f.
|
||||
|
||||
> (make-print-reasons [on?]) If #t, make prints the reason
|
||||
for each dependancy that fires. Defaultly #t.
|
||||
for each dependency that fires. Default: #t.
|
||||
|
||||
_collection.ss_
|
||||
---------------
|
||||
|
@ -154,9 +154,9 @@ compiled. `argv' is passed on to `make'.
|
|||
The resulting extension "_loader" is compiled to the current
|
||||
directory's "compiled/native/PLATFORM" subdirectory, where `PLATFORM'
|
||||
is replaced by the system name of the current platform. Intermediate
|
||||
.c amd .kp files are placed into "compiled/native", and intermediate
|
||||
.c and .kp files are placed into "compiled/native", and intermediate
|
||||
object files are also placed into "compiled/native/PLATFORM". The .c
|
||||
and .kp files are preserved so that thay can be generated once for
|
||||
and .kp files are preserved so that they can be generated once for
|
||||
compiling across multiple platforms with the same filesystem.
|
||||
|
||||
Make rules are also generated for compiling .zo files, placed in the
|
||||
|
@ -240,7 +240,7 @@ The arguments are as follows:
|
|||
This one environment variable applies to all extensions manged
|
||||
by `pre-install'.
|
||||
|
||||
* include-subdirs --- a list of relative paths in which incldue
|
||||
* include-subdirs --- a list of relative paths in which include
|
||||
files will be found; the path of the path will be determined
|
||||
through a search, in case it's not in a standard place like
|
||||
/usr/include.
|
||||
|
|
|
@ -1151,7 +1151,7 @@ _Remote COM servers_
|
|||
large x-large xx-large); 2) a symbol in the list '(larger smaller),
|
||||
indicating a size relative to a parent element; 3) an instance
|
||||
of the css-length structure, or 4) an instance of the css-percentage
|
||||
structure, where the perecentage is relative to the parent element's
|
||||
structure, where the percentage is relative to the parent element's
|
||||
font-size.
|
||||
|
||||
> set-font-size-native! :: (send an-mx-element set-font-size-native! fs)
|
||||
|
|
|
@ -181,8 +181,8 @@ Contact us
|
|||
If you need more information on using MzCOM, please
|
||||
contact us at scheme@plt-scheme.org.
|
||||
|
||||
Acknowledgements
|
||||
----------------
|
||||
Acknowledgments
|
||||
---------------
|
||||
|
||||
MzCOM was developed in response to a query by
|
||||
Andre Van Meulebrouck. Andre also did extensive
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
This is the proposed pattern grammer.
|
||||
This is the proposed pattern grammar.
|
||||
|
||||
Asterisks mark rules that have changed.
|
||||
|
||||
|
|
|
@ -18,7 +18,7 @@ _URL_ posting, _web clients_, _WWW_
|
|||
To load directly: (require (lib "url.ss" "net"))
|
||||
Module files: _url.ss_ - provides the procedures documented below
|
||||
_url-unit.ss_ - provides unit net:url@
|
||||
_url-sig.ss_ - provides signalture net:url^
|
||||
_url-sig.ss_ - provides signature net:url^
|
||||
|
||||
|
||||
ABSTRACT -------------------------------------------------------------
|
||||
|
@ -62,7 +62,7 @@ TYPES ----------------------------------------------------------------
|
|||
`url->string' translate things like %20 into spaces and back again.
|
||||
|
||||
By default, query associations are parsed with either ";" or "&" as
|
||||
a separator, and they are generated with ";" as a separtor. The
|
||||
a separator, and they are generated with ";" as a separator. The
|
||||
`current-alist-separator-mode' parameter for "uri-codec.ss" adjusts
|
||||
this default.
|
||||
|
||||
|
@ -101,7 +101,7 @@ PROCEDURES -----------------------------------------------------------
|
|||
Parses the url specified by the string into a url struct. The
|
||||
`string->url' procedure uses `form-urlencoded->alist' when parsing
|
||||
the query, so it is sensitive to the `current-alist-separator-mode'
|
||||
parameter for determining the association separtor.
|
||||
parameter for determining the association separator.
|
||||
|
||||
> (combine-url/relative url string) -> url
|
||||
|
||||
|
@ -159,7 +159,7 @@ PROCEDURES -----------------------------------------------------------
|
|||
The `url->string' procedure uses `alist->form-urlencoded' when
|
||||
formatting the query, so it it sensitive to the
|
||||
`current-alist-separator-mode' parameter for determining the
|
||||
association separtor. In particular, the default is to separate
|
||||
association separator. In particular, the default is to separate
|
||||
associations with ";" (based on modern recommendations) instead of
|
||||
"&".
|
||||
|
||||
|
@ -201,7 +201,7 @@ PROCEDURES -----------------------------------------------------------
|
|||
Purifies a port, returning the MIME headers, plus a leading line
|
||||
for the form
|
||||
|
||||
HTTP/<vers> <code> <messsage>
|
||||
HTTP/<vers> <code> <message>
|
||||
|
||||
where <vers> is something like 1.0 or 1.1, <code> is an exact
|
||||
integer for the response code, and <message> is arbitrary text
|
||||
|
@ -316,7 +316,7 @@ _CGI_ backends, _WWW_
|
|||
To load directly: (require (lib "cgi.ss" "net"))
|
||||
Module files: _cgi.ss_ - provides the procedures documented below
|
||||
_cgi-unit.ss_ - provides unit net:cgi@
|
||||
_cgi-sig.ss_ - provides signalture net:cgi^
|
||||
_cgi-sig.ss_ - provides signature net:cgi^
|
||||
|
||||
ABSTRACT -------------------------------------------------------------
|
||||
|
||||
|
@ -420,7 +420,7 @@ PROCEDURES -----------------------------------------------------------
|
|||
> (generate-link-text string html-string) -> html-string
|
||||
|
||||
Takes a string representing a URL, a html-string for the anchor
|
||||
text, and generates HTML corresponding to an achor.
|
||||
text, and generates HTML corresponding to an anchor.
|
||||
|
||||
> (generate-error-output list-of-html-strings) -> <exit>
|
||||
|
||||
|
@ -445,7 +445,7 @@ _sending mail_, _sendmail_
|
|||
To load directly: (require (lib "sendmail.ss" "net"))
|
||||
Module files: _sendmail.ss_ - provides the procedures documented below
|
||||
_sendmail-unit.ss_ - provides unit net:sendmail@
|
||||
_sendmail-sig.ss_ - provides signalture net:sendmail^
|
||||
_sendmail-sig.ss_ - provides signature net:sendmail^
|
||||
|
||||
|
||||
ABSTRACT -------------------------------------------------------------
|
||||
|
@ -501,7 +501,7 @@ _sending mail_, _SMTP_
|
|||
To load directly: (require (lib "smtp.ss" "net"))
|
||||
Module files: _smtp.ss_ - provides the procedures documented below
|
||||
_smtp-unit.ss_ - provides unit net:smtp@
|
||||
_smtp-sig.ss_ - provides signalture net:smtp^
|
||||
_smtp-sig.ss_ - provides signature net:smtp^
|
||||
|
||||
ABSTRACT -------------------------------------------------------------
|
||||
|
||||
|
@ -520,7 +520,7 @@ TYPES ----------------------------------------------------------------
|
|||
|
||||
EXCEPTIONS -----------------------------------------------------------
|
||||
|
||||
Communication errors are signalled via exn:fail structure instances.
|
||||
Communication errors are signaled via exn:fail structure instances.
|
||||
|
||||
PROCEDURES -----------------------------------------------------------
|
||||
|
||||
|
@ -545,7 +545,7 @@ PROCEDURES -----------------------------------------------------------
|
|||
|
||||
> (smtp-sending-end-of-message [proc])
|
||||
|
||||
Parameter that detemines a send-done procedure to be called after
|
||||
Parameter that determines a send-done procedure to be called after
|
||||
`smtp-send-message' has completely sent the message. Before the
|
||||
send-done procedure is called, breaking the thread that is executing
|
||||
`smtp-send-message' cancels the send. After the send-done procedure
|
||||
|
@ -559,7 +559,7 @@ _NNTP_, _newsgroups_
|
|||
To load directly: (require (lib "nntp.ss" "net"))
|
||||
Module files: _nntp.ss_ - provides the procedures documented below
|
||||
_nntp-unit.ss_ - provides unit net:nntp@
|
||||
_nntp-sig.ss_ - provides signalture net:nntp^
|
||||
_nntp-sig.ss_ - provides signature net:nntp^
|
||||
|
||||
ABSTRACT -------------------------------------------------------------
|
||||
|
||||
|
@ -706,7 +706,7 @@ _POP-3_, _reading mail_
|
|||
To load directly: (require (lib "pop3.ss" "net"))
|
||||
Module files: _pop3.ss_ - provides the procedures documented below
|
||||
_pop3-unit.ss_ - provides unit net:pop3@
|
||||
_pop3-sig.ss_ - provides signalture net:pop3^
|
||||
_pop3-sig.ss_ - provides signature net:pop3^
|
||||
|
||||
ABSTRACT -------------------------------------------------------------
|
||||
|
||||
|
@ -885,7 +885,7 @@ _IMAP_, _reading mail_
|
|||
To load directly: (require (lib "imap.ss" "net"))
|
||||
Module files: _imap.ss_ - provides the procedures documented below
|
||||
_imap-unit.ss_ - provides unit net:imap@
|
||||
_imap-sig.ss_ - provides signalture net:imap^
|
||||
_imap-sig.ss_ - provides signature net:imap^
|
||||
|
||||
ABSTRACT -------------------------------------------------------------
|
||||
|
||||
|
@ -897,7 +897,7 @@ TYPES ----------------------------------------------------------------
|
|||
|
||||
> imap
|
||||
|
||||
An opaque record reprsenting an IMAP connection.
|
||||
An opaque record representing an IMAP connection.
|
||||
|
||||
> imap-flag
|
||||
|
||||
|
@ -907,7 +907,7 @@ TYPES ----------------------------------------------------------------
|
|||
|
||||
EXCEPTIONS -----------------------------------------------------------
|
||||
|
||||
Communication errors are signalled via exn:fail structure instances.
|
||||
Communication errors are signaled via exn:fail structure instances.
|
||||
|
||||
PROCEDURES -----------------------------------------------------------
|
||||
|
||||
|
@ -925,7 +925,7 @@ PROCEDURES -----------------------------------------------------------
|
|||
See also `imap-port-number', below.
|
||||
|
||||
A user's primary mailbox is always called "INBOX". (Capitalization
|
||||
doesn't matther for that keyword.)
|
||||
doesn't matter for that keyword.)
|
||||
|
||||
Updated message-count and recent-count values are available through
|
||||
`imap-messages' and `imap-recent'. See also `imap-new?' and
|
||||
|
@ -1086,11 +1086,11 @@ PROCEDURES -----------------------------------------------------------
|
|||
reports the result of previous communication. It also clears the
|
||||
update information from the connection after reporting it.
|
||||
|
||||
When a server reports information that supercedes old reported
|
||||
When a server reports information that supersedes old reported
|
||||
information for a message, or if the server reports that a message
|
||||
has been deleted, then old information for the message is
|
||||
dropped. Similarly, if `imap-get-messages' is used to explicitly
|
||||
obtain information, any redudant (or out-of-date) information is
|
||||
obtain information, any redundant (or out-of-date) information is
|
||||
dropped.
|
||||
|
||||
A client need not use `imap-get-updates' ever, but accumulated
|
||||
|
@ -1109,7 +1109,7 @@ PROCEDURES -----------------------------------------------------------
|
|||
Downloads information for a set of messages. The `msg-num-list'
|
||||
argument specifies a set of messages by their message positions (not
|
||||
their uids). The `field-list' argument specifies the type of
|
||||
information to download for each message. The avilable fields are:
|
||||
information to download for each message. The available fields are:
|
||||
|
||||
* 'uid - value is an integer
|
||||
* 'header - value is a header (string; see the head package)
|
||||
|
@ -1134,7 +1134,7 @@ PROCEDURES -----------------------------------------------------------
|
|||
|
||||
An imap flag is a symbol, but it is generally not a convenient one
|
||||
to use within a Scheme program, because it usually starts with a
|
||||
backslash and flag comparisions are case-insensitive. The
|
||||
backslash and flag comparisons are case-insensitive. The
|
||||
`imap-flag->symbol' and `symbol->imap-flag' procedures convert IMAP
|
||||
flags to convenient symbols and vice-versa:
|
||||
|
||||
|
@ -1163,7 +1163,7 @@ PROCEDURES -----------------------------------------------------------
|
|||
flags are set:
|
||||
|
||||
* '+ - add the given flags to each message
|
||||
* '- - remove the given flags from each emssage
|
||||
* '- - remove the given flags from each message
|
||||
* '! - set each message's flags to the given set
|
||||
|
||||
The `msg-num-list' argument specifies a set of messages by their
|
||||
|
@ -1260,18 +1260,18 @@ _mime headers_, _mail headers_, _http headers_
|
|||
To load directly: (require (lib "head.ss" "net"))
|
||||
Module files: _head.ss_ - provides the procedures documented below
|
||||
_head-unit.ss_ - provides unit net:head@
|
||||
_head-sig.ss_ - provides signalture net:head^
|
||||
_head-sig.ss_ - provides signature net:head^
|
||||
|
||||
ABSTRACT -------------------------------------------------------------
|
||||
|
||||
Implements utlities for RFC 822 headers and mail addresses.
|
||||
Implements utilities for RFC 822 headers and mail addresses.
|
||||
|
||||
TYPES ----------------------------------------------------------------
|
||||
|
||||
> header
|
||||
|
||||
A string that is an RFC-882-compliant header. A header string
|
||||
contains a series of CRLF-delimitted fields, and ends with two CRLFs
|
||||
contains a series of CRLF-delimited fields, and ends with two CRLFs
|
||||
(the first one terminates the last field, and the second terminates
|
||||
the header).
|
||||
|
||||
|
@ -1279,7 +1279,7 @@ PROCEDURES -----------------------------------------------------------
|
|||
|
||||
> empty-header
|
||||
|
||||
A string correcponding to the empty header, useful for building up
|
||||
A string corresponding to the empty header, useful for building up
|
||||
headers with `insert-field' and `append-headers'.
|
||||
|
||||
> (validate-header candidate-header-string) -> void
|
||||
|
@ -1318,7 +1318,7 @@ PROCEDURES -----------------------------------------------------------
|
|||
Creates a new header by prefixing the given header with the given
|
||||
field-value pair. `value-string' should not contain a terminating
|
||||
CRLF, but a multi-line value (perhaps created with
|
||||
`data-lines->data') may contain seperator CRLFs.
|
||||
`data-lines->data') may contain separator CRLFs.
|
||||
|
||||
> (replace-field field-string value-string header) -> header
|
||||
|
||||
|
@ -1331,7 +1331,7 @@ PROCEDURES -----------------------------------------------------------
|
|||
|
||||
Creates a standard mail header given the sender, various lists of
|
||||
recipients, a subject, and the current date. (The BCC recipients do
|
||||
not acually appear in the header, but they're accepted anyway to
|
||||
not actually appear in the header, but they're accepted anyway to
|
||||
complete the abstraction.)
|
||||
|
||||
> (data-lines->data list-of-strings) -> string
|
||||
|
@ -1368,7 +1368,7 @@ PROCEDURES -----------------------------------------------------------
|
|||
" doe@localhost (Johnny Doe)" => "doe@localhost (Johnny Doe)"
|
||||
"doe@localhost" => "doe@localhost"
|
||||
|
||||
* 'all - a list containing each of the three posibilities:
|
||||
* 'all - a list containing each of the three possibilities:
|
||||
free-form name, address, and full address (in that
|
||||
order)
|
||||
|
||||
|
@ -1388,7 +1388,7 @@ _DNS_, _domain name service_
|
|||
To load directly: (require (lib "dns.ss" "net"))
|
||||
Module files: _dns.ss_ - provides the procedures documented below
|
||||
_dns-unit.ss_ - provides unit net:dns@
|
||||
_dns-sig.ss_ - provides signalture net:dns^
|
||||
_dns-sig.ss_ - provides signature net:dns^
|
||||
|
||||
ABSTRACT -------------------------------------------------------------
|
||||
|
||||
|
@ -1403,7 +1403,7 @@ PROCEDURES -----------------------------------------------------------
|
|||
> (dns-get-address nameserver-string address-string) -> address-string
|
||||
|
||||
Consults the specified nameserver (normally a numerical address like
|
||||
"128.42.1.30") to obtain a numerical address for the given internet
|
||||
"128.42.1.30") to obtain a numerical address for the given Internet
|
||||
address.
|
||||
|
||||
The query record sent to the DNS server includes the "recursive"
|
||||
|
@ -1436,7 +1436,7 @@ Module files: _mime.ss_ - provides the procedures documented below
|
|||
_mime-unit.ss_ - provides unit net:mime@
|
||||
imports net:base64^ from "base64-sig.ss"
|
||||
and net:qp^ from "qp-sig.ss"
|
||||
_mime-sig.ss_ - provides signalture net:mime^
|
||||
_mime-sig.ss_ - provides signature net:mime^
|
||||
|
||||
ABSTRACT -------------------------------------------------------------
|
||||
|
||||
|
@ -1462,7 +1462,7 @@ EXCEPTIONS -----------------------------------------------------------
|
|||
|
||||
missing-multipart-boundary-parameter
|
||||
|
||||
A multipart type is signalled, but no `boundary' parameter is
|
||||
A multipart type is signaled, but no `boundary' parameter is
|
||||
given, also an error on the producer end of the message.
|
||||
|
||||
malformed-multipart-entity
|
||||
|
@ -1473,7 +1473,7 @@ EXCEPTIONS -----------------------------------------------------------
|
|||
empty-mechanism
|
||||
|
||||
No transport encoding mechanism was provided with the
|
||||
Conent-Transfer-Encoding field.
|
||||
Content-Transfer-Encoding field.
|
||||
|
||||
empty-type
|
||||
|
||||
|
@ -1746,7 +1746,7 @@ _Base 64 Encoding_, _base64_
|
|||
To load directly: (require (lib "base64.ss" "net"))
|
||||
Module files: _base64.ss_ - provides the procedures documented below
|
||||
_base64-unit.ss_ - provides unit net:base64@
|
||||
_base64-sig.ss_ - provides signalture net:base64^
|
||||
_base64-sig.ss_ - provides signature net:base64^
|
||||
|
||||
ABSTRACT -------------------------------------------------------------
|
||||
|
||||
|
@ -1788,7 +1788,7 @@ _Quoted Printable Encoding_, _qp__
|
|||
To load directly: (require (lib "qp.ss" "net"))
|
||||
Module files: _qp.ss_ - provides the procedures documented below
|
||||
_qp-unit.ss_ - provides unit net:qp@
|
||||
_qp-sig.ss_ - provides signalture net:qp^
|
||||
_qp-sig.ss_ - provides signature net:qp^
|
||||
|
||||
ABSTRACT -------------------------------------------------------------
|
||||
|
||||
|
@ -1855,7 +1855,7 @@ _FTP client_
|
|||
To load directly: (require (lib "ftp.ss" "net"))
|
||||
Module files: _ftp.ss_ - provides the procedures documented below
|
||||
_ftp-unit.ss_ - provides unit net:ftp@
|
||||
_ftp-sig.ss_ - provides signalture net:ftp^
|
||||
_ftp-sig.ss_ - provides signature net:ftp^
|
||||
|
||||
ABSTRACT -------------------------------------------------------------
|
||||
|
||||
|
@ -1869,7 +1869,7 @@ PROCEDURES -----------------------------------------------------------
|
|||
|
||||
Establishes an FTP connection with the given server using the
|
||||
supplied username and password. The result is an opaque `ftp-conn'
|
||||
structure reprsenting the connection.
|
||||
structure representing the connection.
|
||||
|
||||
The username and password strings are encoded to bytes using the
|
||||
current locale's encoding.
|
||||
|
@ -1899,7 +1899,7 @@ PROCEDURES -----------------------------------------------------------
|
|||
`ftp-make-file-seconds', below. The third string is the name of the
|
||||
file or directory.
|
||||
|
||||
All strings are decoded frombytes using the current locale's
|
||||
All strings are decoded from bytes using the current locale's
|
||||
encoding.
|
||||
|
||||
> (ftp-make-file-seconds ftp-date-string)
|
||||
|
@ -1912,7 +1912,7 @@ PROCEDURES -----------------------------------------------------------
|
|||
Downloads `filename-string' from the server's current directory and
|
||||
puts it in `local-directory-path' using the same name. If the file
|
||||
already exists in the local directory, it is replaced, but only
|
||||
after the transfer suceeds (i.e., the file is first downloaded to a
|
||||
after the transfer succeeds (i.e., the file is first downloaded to a
|
||||
temporary file, then moved into place on success).
|
||||
|
||||
==========================================================================
|
||||
|
@ -1972,12 +1972,12 @@ PROCEDURES -----------------------------------------------------------
|
|||
(lib "mzssl.ss" "openssl"). The arguments to `make-ssl-tcp@' control
|
||||
the certificates and keys uses by server and client connections:
|
||||
|
||||
`server-cert-file' - a PEM file for a server's certyificate; #f means
|
||||
`server-cert-file' - a PEM file for a server's certificate; #f means
|
||||
no certificate (which is unlikely to work with any SSL client)
|
||||
`server-key-file' - a private key PEM to go with `server-cert-file';
|
||||
#f means no key (which is likely renders a certificate useless)
|
||||
`server-root-cert-files' - a list of PEM files for trusted root
|
||||
ceritifcates; #f disables verification of peer client certificates
|
||||
certificates; #f disables verification of peer client certificates
|
||||
|
||||
`server-suggest-auth-file' - PEM file for root certificates to be
|
||||
suggested to peer clients that must supply certificates
|
||||
|
@ -1987,7 +1987,7 @@ PROCEDURES -----------------------------------------------------------
|
|||
`client-key-file' - a private key PEM to go with `client-cert-file';
|
||||
#f means no key (which is likely renders a certificate useless)
|
||||
`client-root-cert-files' - a list of PEM files for trusted root
|
||||
ceritifcates; #f disables verification of peer server certificates
|
||||
certificates; #f disables verification of peer server certificates
|
||||
|
||||
==========================================================================
|
||||
_cookies_, HTTP _State Management_
|
||||
|
@ -1996,7 +1996,7 @@ _cookies_, HTTP _State Management_
|
|||
To load directly: (require (lib "cookie.ss" "net"))
|
||||
Module files: _cookie.ss_ - provides the procedures documented below
|
||||
_cookie-unit.ss_ - provides unit net:cookie@
|
||||
_cookie-sig.ss_ - provides signalture net:cookie^
|
||||
_cookie-sig.ss_ - provides signature net:cookie^
|
||||
|
||||
|
||||
ABSTRACT -------------------------------------------------------------
|
||||
|
@ -2010,7 +2010,7 @@ EXCEPTIONS -----------------------------------------------------------
|
|||
> cookie-error
|
||||
struct (cookie-error exn) ()
|
||||
|
||||
All errors are signalled by raising a cookie-error
|
||||
All errors are signaled by raising a cookie-error
|
||||
|
||||
TYPES ----------------------------------------------------------------
|
||||
|
||||
|
@ -2135,7 +2135,7 @@ _URL encoding_, _URL decoding_, _application/x-www-form-urlencoded_
|
|||
To load directly: (require (lib "uri-codec.ss" "net"))
|
||||
Module files: _uri-codec.ss_ - provides the procedures documented below
|
||||
_uri-codec-unit.ss_ - provides unit net:uri-codec@
|
||||
_uri-codec-sig.ss_ - provides signalture net:uri-codec^
|
||||
_uri-codec-sig.ss_ - provides signature net:uri-codec^
|
||||
|
||||
|
||||
ABSTRACT -------------------------------------------------------------
|
||||
|
@ -2246,7 +2246,7 @@ PROCEDURES -----------------------------------------------------------
|
|||
separator when encoding. The other modes use/recognize only of the
|
||||
separators.
|
||||
|
||||
Exmaples for '((name . "shriram") (host "nw")):
|
||||
Examples for '((name . "shriram") (host "nw")):
|
||||
|
||||
Mode Parse Generate
|
||||
------ -------------------- --------------------
|
||||
|
|
|
@ -53,7 +53,7 @@ Like `ssl-connect', but breaking is enabled while trying to connect.
|
|||
> (ssl-make-client-context [protocol-symbol])
|
||||
|
||||
Creates a context to be supplied to `ssl-connect'. The context
|
||||
identifis a communication protocol (as selected by `protocol-symbol'),
|
||||
identifies a communication protocol (as selected by `protocol-symbol'),
|
||||
and also holds certificate information (i.e., the client's identity,
|
||||
its trusted certificate authorities, etc.). See the "Certificate
|
||||
procedures" section below for more information on certificates.
|
||||
|
@ -155,7 +155,7 @@ certificate authorities with `ssl-load-verify-root-certificates!'.
|
|||
|
||||
Loads a PEM-format file containing trusted certificates that are used
|
||||
to verify the certificates of a connection peer. Call this procedure
|
||||
multiple times to load multiple sets of trusted certifactes.
|
||||
multiple times to load multiple sets of trusted certificates.
|
||||
|
||||
The file "test.pem" is suitable for testing purposes where the peer
|
||||
identifies itself using "test.pem". Since "test.pem" is public, such
|
||||
|
@ -169,7 +169,7 @@ server. The certificate list is sent to a client when the server
|
|||
requests a certificate as an indication of which certificates the
|
||||
server trusts.
|
||||
|
||||
Loading the suggested certifcicates does not imply trust, however; any
|
||||
Loading the suggested certificates does not imply trust, however; any
|
||||
certificate presented by the client will be checked using the trusted
|
||||
roots loaded by `ssl-load-verify-root-certificates!'.
|
||||
|
||||
|
@ -217,7 +217,7 @@ Per-platform notes:
|
|||
do not produce DLLs.
|
||||
|
||||
Bonus hack: If "{lib,ssl}easy32xxxxxxx.lib" exist in the lib
|
||||
directory, they are used (instead of "{liib,ssl}eay32.lib") with
|
||||
directory, they are used (instead of "{lib,ssl}eay32.lib") with
|
||||
the expectation that the resulting extension will link to
|
||||
"{lib,ssl}eay32xxxxxxx.dll". This enables the name-mangling version
|
||||
hack for distributing DLLs.
|
||||
|
|
|
@ -190,7 +190,7 @@ The following require imports the _lexer generator_.
|
|||
|
||||
When peeking from the input port raises an exception (such as by an
|
||||
embedded XML editor with malformed syntax), the exception can be
|
||||
raised before all tokens preceeding the exception have been
|
||||
raised before all tokens preceding the exception have been
|
||||
returned.
|
||||
|
||||
|
||||
|
@ -275,9 +275,9 @@ operators:
|
|||
> (+ re ...) repetition of regexps 1 or more times
|
||||
> (? re ...) 0 or 1 occurrence of regexps
|
||||
> (= natural-number re ...)
|
||||
exactly n occurences of regexps
|
||||
exactly n occurrences of regexps
|
||||
> (>= natural-number re ...)
|
||||
at least n occurences of regexps
|
||||
at least n occurrences of regexps
|
||||
> (** natural-number natural-number-or-#f-or-+inf.0 re ...)
|
||||
between m and n of regexps, inclusive
|
||||
#f and +inf.0 both indicate no upper limit
|
||||
|
|
|
@ -234,7 +234,7 @@ home/
|
|||
|
||||
There are no strict requirements for what sorts of files can go in
|
||||
your package, but for it to work well with PLT Scheme's module
|
||||
system you should arrange your Schme code into modules.
|
||||
system you should arrange your Scheme code into modules.
|
||||
|
||||
2. CREATE INFO.SS AND DOC.TXT FILES [OPTIONAL]
|
||||
|
||||
|
@ -278,7 +278,7 @@ categorized as "Miscellaneous."
|
|||
The _'doc.txt field_
|
||||
|
||||
If present, the doc.txt field should be a string corresponding to the
|
||||
name (without path) of the text documentatation file for your
|
||||
name (without path) of the text documentation file for your
|
||||
package. If this field is the value "doc.txt" and a file called
|
||||
"doc.txt" exists in your package's root directory, it will be used as
|
||||
the online documentation visitors to the planet.plt-scheme.org website
|
||||
|
|
|
@ -63,7 +63,7 @@ PLoT collection: Quick Start
|
|||
|
||||
To fit a particular function to a curve:
|
||||
1. Set up the independent and dependent variable data. The first item
|
||||
in each vector is the independant var, the second is the result.
|
||||
in each vector is the independent var, the second is the result.
|
||||
The last item must is the weight of the error - we can leave it as
|
||||
1 since all the items weigh the same.
|
||||
(define data '(#(0 3 1)
|
||||
|
@ -73,7 +73,7 @@ PLoT collection: Quick Start
|
|||
#(4 11 1)))
|
||||
|
||||
2. Set up the function to be fitted using fit. This particular
|
||||
function looks like a line. The independant variables must come
|
||||
function looks like a line. The independent variables must come
|
||||
before the parameters.
|
||||
(define fit-fun
|
||||
(lambda (x m b) (+ b (* m x))))
|
||||
|
|
|
@ -9,7 +9,7 @@ The interactions window accepts variable declaration, statements and
|
|||
expressions legal for the language level. If the text is not sending,
|
||||
type Alt+Enter.
|
||||
|
||||
The definitions window expects class and interface defintions,
|
||||
The definitions window expects class and interface definitions,
|
||||
interaction boxes, and test-suite boxes. (i.e. what would be given to
|
||||
javac plus two graphical boxes). Descriptions of these boxes can be
|
||||
found in the DrScheme manual.
|
||||
|
|
|
@ -40,7 +40,7 @@ this tool:
|
|||
a bounded term size.
|
||||
|
||||
_threads.ss_: shows how non-deterministic choice can be
|
||||
modelled in a reduction semantics. Contains an example use
|
||||
modeled in a reduction semantics. Contains an example use
|
||||
of a simple alternative pretty printer.
|
||||
|
||||
_semaphores.ss_: a simple threaded language with semaphores
|
||||
|
@ -85,7 +85,7 @@ variables.
|
|||
|
||||
The _hole_ pattern matches anything when inside a matching
|
||||
in-hole pattern. The (hole <symbol>) variation on that
|
||||
pattern is used in conjuction with in-named-hole to support
|
||||
pattern is used in conjunction with in-named-hole to support
|
||||
languages that require multiple patterns in a hole.
|
||||
|
||||
The _<symbol>_ pattern stands for a literal symbol that must
|
||||
|
@ -143,7 +143,7 @@ The (pattern ...) pattern matches a sexpression list, where
|
|||
each pattern matches an element of the list. In addition, if
|
||||
a list pattern contains an ellipses that is not treated as a
|
||||
literal, instead it matches any number of duplications of the
|
||||
pattern that came before the ellipses (including 0). Furthemore,
|
||||
pattern that came before the ellipses (including 0). Furthermore,
|
||||
each (name <symbol> <pattern>) in the duplicated pattern
|
||||
binds a list of matches to <symbol>, instead of a single match.
|
||||
(A nested duplicated pattern creates a list of list matches,
|
||||
|
@ -427,7 +427,7 @@ instead invoked with a single argument, the s-expression to
|
|||
render, and it must return a string which the GUI will use
|
||||
as a representation of the given expression for display.
|
||||
|
||||
The default pp uses mzlib's pretty-print function. See
|
||||
The default pp uses MzLib's pretty-print function. See
|
||||
threads.ss in the examples directory for an example use
|
||||
of the one-argument form of this argument and
|
||||
ho-contracts.ss in the examples directory for an example
|
||||
|
@ -475,15 +475,15 @@ The _subst.ss_ library provides these names:
|
|||
> (subst (match-pattern subst-rhs ...) ...) SYNTAX
|
||||
|
||||
The result of this form is a function that performs capture
|
||||
avoiding substition for a particular (sexp-based)
|
||||
avoiding substitution for a particular (sexp-based)
|
||||
language. The function accepts three arguments, a variable,
|
||||
a term to substitue and a term to substitute into.
|
||||
a term to substitute and a term to substitute into.
|
||||
|
||||
Each of the `match-pattern's specify the forms of
|
||||
the language and the `subst-rhs's specify what kind of form
|
||||
it is. Each of the match-patterns are in (lib "match.ss"
|
||||
"match)'s pattern language and any variable that they bind
|
||||
are avaialbe in the <scheme-expression>'s described below.
|
||||
"match")'s pattern language and any variable that they bind
|
||||
are available in the <scheme-expression>'s described below.
|
||||
|
||||
The language of the subst-rhs follows.
|
||||
|
||||
|
@ -495,7 +495,7 @@ The language of the subst-rhs follows.
|
|||
|
||||
> (constant)
|
||||
|
||||
this means that the rhs for thsi form is a constant that
|
||||
this means that the rhs for this form is a constant that
|
||||
cannot be renamed. Nothing may follow this.
|
||||
|
||||
> (all-vars <scheme-expression>)
|
||||
|
@ -539,7 +539,7 @@ corresponding to one of the subexpressions of this
|
|||
expression (matched by the match-patten for this clause of
|
||||
subst).
|
||||
|
||||
Consider this example of a substition procedure for the
|
||||
Consider this example of a substitution procedure for the
|
||||
lambda calculus:
|
||||
|
||||
(define lc-subst
|
||||
|
@ -575,7 +575,7 @@ subterms declaration says that all of the arguments are
|
|||
subterms and that they do not introduce any new terms.
|
||||
|
||||
In this program, lc-subst is bound to a function that does
|
||||
the substition. The first argument is the variable to
|
||||
the substitution. The first argument is the variable to
|
||||
substitute for, the second is the term to substitute and the
|
||||
final argument is the term to substitute into. For example,
|
||||
this call:
|
||||
|
@ -720,10 +720,10 @@ The _helper.ss_ module provides additional helper functions and syntax.
|
|||
|
||||
> (define-memoized (f arg ...) expr ...) SYNTAX
|
||||
|
||||
Like `define' for function defitions, except that the function is
|
||||
Like `define' for function definitions, except that the function is
|
||||
"memoized": it automatically remembers each result, and when `eq?'
|
||||
arguments are provided later, the same result is returned
|
||||
immeduately.
|
||||
immediately.
|
||||
|
||||
> (lambda-memoized (arg ...) expr) SYNTAX
|
||||
|
||||
|
@ -788,7 +788,7 @@ Aggregates potential results for future exploration.
|
|||
computation proceeds bey generating each successful result from
|
||||
`backtrackable-expr', and then feeding the result to the
|
||||
`body-expr's to refine the results. Naturally, `body-expr' can
|
||||
contain futher uses of `explore-results' or `many-results' which are
|
||||
contain further uses of `explore-results' or `many-results' which are
|
||||
folded into the backtracking exploration.
|
||||
|
||||
> (explore-parallel-results (results-id) backtrackable-list-expr
|
||||
|
@ -816,10 +816,10 @@ Aggregates potential results for future exploration.
|
|||
|
||||
A poor-man's `gui' for test interaction. The first argument
|
||||
represents a set of reductions that define a function; the second
|
||||
argument is the starting expression; the thrid argument is a
|
||||
argument is the starting expression; the third argument is a
|
||||
predicate to recognize ending expressions; the fourth argument
|
||||
limits the number of steps taken. The function applies the
|
||||
reductions repeatedly until an ending expression os found, or until
|
||||
reductions repeatedly until an ending expression is found, or until
|
||||
the reduction gets stuck. (If the reduction produces multiple
|
||||
results, an exception is raised.) The result is the list of
|
||||
expressions leading to the ending expression.
|
||||
|
@ -835,7 +835,7 @@ Aggregates potential results for future exploration.
|
|||
|
||||
> all-of : (any? (any? . -> . any) . -> . (listof any?))
|
||||
|
||||
Takes an arbirary S-expression as the first argument, and a
|
||||
Takes an arbitrary S-expression as the first argument, and a
|
||||
predicate as the second argument. all-of' then traverses the pairs
|
||||
that make up the S-expression, calling the predicate on every pair
|
||||
and every value within a pair. The result is the list of values for
|
||||
|
@ -844,7 +844,7 @@ Aggregates potential results for future exploration.
|
|||
|
||||
> transitive-closure : ((listof pair?) . -> . (listof (listof any?))
|
||||
|
||||
Given the reprsentation of a function as a list of pairs,
|
||||
Given the representation of a function as a list of pairs,
|
||||
`transitive-closure' produces the transitive closure as a list of
|
||||
lists. Each nested list begins with a domain item and continues
|
||||
with a list of range items.
|
||||
|
@ -888,7 +888,7 @@ a grammar non-terminal.
|
|||
. -> . any)
|
||||
|
||||
The first argument is a procedure to call with a series of generated
|
||||
grammar instances and each term's size. Instances are generatedfrom
|
||||
grammar instances and each term's size. Instances are generated from
|
||||
smallest to largest; the size of an instance is roughly the size of
|
||||
the proof tree that demonstrates grammar membership.
|
||||
|
||||
|
@ -904,6 +904,6 @@ a grammar non-terminal.
|
|||
symbol?
|
||||
. -> . any)
|
||||
|
||||
Like `for-each-generated', except minimum and maxiumum sizes are
|
||||
Like `for-each-generated', except minimum and maximum sizes are
|
||||
provided, and the order of generation is arbitrary (i.e., some
|
||||
larger instances may be generated before smaller instances).
|
||||
|
|
|
@ -3,4 +3,4 @@ in normal releases. (It's existence indicates a checked out tree.)
|
|||
|
||||
The stamp.ss module provides one definition: `stamp' that is bound to
|
||||
a string representing the current day. The time-stamp.ss file is a
|
||||
tool, used by drscheme to set the version based on the time stamp.
|
||||
tool, used by DrScheme to set the version based on the time stamp.
|
||||
|
|
|
@ -121,7 +121,7 @@ Additional "info.ss" fields trigger additional setup actions:
|
|||
relative to the collection. The module must provide `installer' as
|
||||
a procedure that accepts either one or two arguments. The first
|
||||
argument is a directory path to the PLT installation directory; the
|
||||
second argument, if accecpted, is a path to the collection's own
|
||||
second argument, if accepted, is a path to the collection's own
|
||||
directory. The procedure should perform collection-specific
|
||||
installation work, and it should avoid unnecessary work in the case
|
||||
that it is called multiple times for the same installation.
|
||||
|
@ -181,7 +181,7 @@ installing a single .plt file:
|
|||
|
||||
The `get-dir-proc' procedure is called if the installer needs a
|
||||
target directory for installation, and a #f result means that the
|
||||
user cancelled the installation. Typically, `get-dir-proc' is
|
||||
user canceled the installation. Typically, `get-dir-proc' is
|
||||
`current-directory'.
|
||||
|
||||
Setup PLT as a Unit
|
||||
|
@ -219,7 +219,7 @@ parameters that control the setup process:
|
|||
> call-install - #t => call collection "info.ss"-specified setup code
|
||||
[default: #t]
|
||||
> force-unpack - #t => ignore version and already-installed errors
|
||||
when upacking a .plt archive [default: #f]
|
||||
when unpacking a .plt archive [default: #f]
|
||||
> pause-on-errors - #t => in the event of an error, prints a summary error
|
||||
and waits for stdin input before terminating
|
||||
[default: #f]
|
||||
|
@ -244,7 +244,7 @@ parameters that control the setup process:
|
|||
Thus, to unpack a single .plt archive "x.plt", set the `archives'
|
||||
parameter to (list "x.plt") and leave `specific-collections' as null.
|
||||
|
||||
Beware that the current namespace might intefere with setup
|
||||
Beware that the current namespace might interfere with setup
|
||||
actions. For example, if setup is supposed to compile a module `(lib
|
||||
"foo.ss")' that imports `(lib "bar.ss")', but `(lib "bar.ss")' is
|
||||
already loaded in the current namespace, then compilation will use the
|
||||
|
@ -302,7 +302,7 @@ The _getinfo.ss_ module defines the following functions:
|
|||
directory (as determined by the PLT_COLLECTION_PATHS environment variable,
|
||||
etc.) and the file "cache.ss" in the user addon dir.
|
||||
|
||||
The result is in a cannonical order (sorted lexographically by directory
|
||||
The result is in a canonical order (sorted lexicographically by directory
|
||||
name), and the paths it returns are suitable for providing to
|
||||
get-info/full.
|
||||
|
||||
|
|
|
@ -41,7 +41,7 @@ Vertex arrays (GL 1.5, Section 2.8)
|
|||
Buffer objects (GL 1.5, Section 2.9)
|
||||
glGetPointerv (GL 1.5, Section 6.1.11)
|
||||
Buffer object queries (GL 1.5, Section 6.1.13)
|
||||
Polygon tessalation (GLU 1.3, Section 5)
|
||||
Polygon tessellation (GLU 1.3, Section 5)
|
||||
gluQuadricCallback (GLU 1.3, Section 6.2)
|
||||
NURBS (GLU 1.3, Section 7)
|
||||
|
||||
|
|
|
@ -44,7 +44,7 @@ Reading panel:
|
|||
|
||||
which specifies where messages should be autofiled based on
|
||||
regular expression matching of various headers in the email. For
|
||||
any email, if it has a header named `field-string' that mathces
|
||||
any email, if it has a header named `field-string' that matches
|
||||
`regexp-string', it is filed into `mailbox-name-string'.
|
||||
|
||||
- Shown Header Fields: Names header fields to to (in order_ when
|
||||
|
@ -80,7 +80,7 @@ Sending panel:
|
|||
|
||||
(list-of (list string (union string (list-of string))))
|
||||
|
||||
specifing a mapping from names to one or more email
|
||||
specifying a mapping from names to one or more email
|
||||
addresses. These names can be used in the "To", "cc", or "bcc"
|
||||
headers of your email address.
|
||||
|
||||
|
@ -93,16 +93,16 @@ Sending panel:
|
|||
Internal options that still need preference-panel support:
|
||||
|
||||
- biff-delay-seconds: (union #f number); when number specifies how long
|
||||
between sirmail waits before polling the mailbox. Only polls when
|
||||
between SirMail waits before polling the mailbox. Only polls when
|
||||
connected.
|
||||
|
||||
- sort-by: (union #f 'date 'subject 'from 'id); specifies the
|
||||
initial storting of opened mailboxes.
|
||||
initial sorting of opened mailboxes.
|
||||
'id indicates sorting by order received and #f means no sorting.
|
||||
These should produce the same ordering, but 'id is probably a bit slower.
|
||||
|
||||
- show-urls: (union 'on 'off), defaults to 'on
|
||||
If this is 'on, it hilights urls in the text. Clicking on the
|
||||
If this is 'on, it highlights urls in the text. Clicking on the
|
||||
urls will open a web browser, pointing it at that url.
|
||||
|
||||
-------------------------------------------------------------------
|
||||
|
@ -123,6 +123,6 @@ entry is a list of at least two elements:
|
|||
Rice. Nothing in SirMail ever writes new options into "mailboxes"; I
|
||||
add them by hand, and SirMail preserves them.
|
||||
|
||||
The overidding-options feature was a quick hack for what I needed, and
|
||||
The overriding-options feature was a quick hack for what I needed, and
|
||||
it should be replaced eventually. There's a lot of duplication of
|
||||
information in the current format.
|
||||
|
|
|
@ -16,7 +16,7 @@ defined, or if SLIB is installed as an "slib" collection (i.e., in an
|
|||
"slib" directory in the same location as the "mzlib" directory).
|
||||
|
||||
|
||||
SLIB is not integerated with MzScheme's module system. Instead, SLIB
|
||||
SLIB is not integrated with MzScheme's module system. Instead, SLIB
|
||||
works in the top-level environment, and it provides its own "feature"
|
||||
system using the function `require'. Unfortunately, that function name
|
||||
conflicts with MzScheme's own `require' form. In an attempt to work
|
||||
|
@ -40,7 +40,7 @@ initialize the installation with
|
|||
|
||||
The initialization file contains one system-dependent setting:
|
||||
`most-positive-fixnum' is bound to a value that is precisely correct
|
||||
for 32-bit architectures. The precise value for a 64-bit architcture
|
||||
for 32-bit architectures. The precise value for a 64-bit architecture
|
||||
is in the file, but commented out. The only problem with using the
|
||||
32-bit value for a 64-bit architecture is a decrease in performance.
|
||||
|
||||
|
|
|
@ -119,7 +119,7 @@ Alt-q (or Meta-q) to end the slides. More controls:
|
|||
|
||||
In general, each element after the title string for `slide/title' is a
|
||||
pict that will be centered on the slide. The picts are stacked
|
||||
verically and top-aligned, with `gap-size' separation between each
|
||||
vertically and top-aligned, with `gap-size' separation between each
|
||||
pict.
|
||||
|
||||
(module hello-world (lib "slideshow.ss" "slideshow")
|
||||
|
@ -137,7 +137,7 @@ instead of putting them at the top of the slide:
|
|||
(t "Hello World!")
|
||||
(t "Goodbye Dlrow!")))
|
||||
|
||||
Various functions format paragraphs and generate bullted items for
|
||||
Various functions format paragraphs and generate bulleted items for
|
||||
lists. For example, `item/page' creates a bulleted paragraph that
|
||||
spaces the width of the slide:
|
||||
|
||||
|
@ -174,24 +174,24 @@ multi-slide patterns. Each element argument to `slide/title' after the
|
|||
title is usually a pict, but there are a few other possibilities:
|
||||
|
||||
* If an element is 'next, then a slide is generated containing only
|
||||
the preceeding elements, and then the <elems> are re-processed
|
||||
the preceding elements, and then the <elems> are re-processed
|
||||
without the 'next. Multiple 'next elements generate multiple slides.
|
||||
|
||||
* If an element is 'alts, then the next element must be a list of
|
||||
element lists. Each list up to the last one is appended to the
|
||||
elements before 'alts and the resulting list of elements is
|
||||
processed. The last lists is appended to the preceeding elements
|
||||
processed. The last lists is appended to the preceding elements
|
||||
along with the remaining elements (after the list of lists) and the
|
||||
result is re-processed.
|
||||
|
||||
* A 'nothing element is ignored (useful as a result of a branching
|
||||
expression).
|
||||
|
||||
* 'next! is like 'next, except that it is preserved when consensing
|
||||
* 'next! is like 'next, except that it is preserved when condensing
|
||||
(see below on the --condense flag).
|
||||
|
||||
* 'alts~ is like 'alts, except that it is *not* preserved when
|
||||
consensing (see below on the --condense flag).
|
||||
condensing (see below on the --condense flag).
|
||||
|
||||
* A comment produced by `comment' is ignored, except when commentary
|
||||
is displayed.
|
||||
|
@ -427,7 +427,7 @@ Procedure Reference
|
|||
|
||||
> (start-at-recent-slide) - Sets the starting slide for the talk to
|
||||
the most recently created slide. If this function is used multiple
|
||||
times, the last use overrides the realier uses.
|
||||
times, the last use overrides the earlier uses.
|
||||
|
||||
> (scroll-transition x y w h dx dy [secs steps-k]) - inserts a scroll
|
||||
animation that shifts the screen rectangle (x, y, x+w, y+h) by `dx'
|
||||
|
@ -470,7 +470,7 @@ Procedure Reference
|
|||
|
||||
> current-font-size - Parameter for the font size used by `t', etc.,
|
||||
initialized to `font-size'.
|
||||
> line-sep - Amount of seperating between paragraph lines.
|
||||
> line-sep - Amount of separating between paragraph lines.
|
||||
> title-size - Font size used for slide titles, derived from `font-size'.
|
||||
> main-font - Font specification used for `t' by default
|
||||
> current-main-font - Parameter for the font specification
|
||||
|
@ -482,7 +482,7 @@ Procedure Reference
|
|||
`current-main-font' set to `f', which must be a
|
||||
text-style (see texpict for details)
|
||||
|
||||
> red - a color name like "red", possibiliy selected by the user.
|
||||
> red - a color name like "red", possibly selected by the user.
|
||||
> green - a color name like "green"
|
||||
> blue - ...
|
||||
> purple - ...
|
||||
|
@ -491,10 +491,10 @@ Procedure Reference
|
|||
> bullet - a bullet pict
|
||||
> o-bullet - a hollow bullet pict
|
||||
|
||||
> client-w - (syntax) useable width of the screen
|
||||
> client-h - (syntax) useable height of the screen
|
||||
> get-client-w - returns useable width of the screen
|
||||
> get-client-h - returns useable height of the screen
|
||||
> client-w - (syntax) usable width of the screen
|
||||
> client-h - (syntax) usable height of the screen
|
||||
> get-client-w - returns usable width of the screen
|
||||
> get-client-h - returns usable height of the screen
|
||||
|
||||
> full-page - (syntax) an empty pict that is the same size as the
|
||||
client area
|
||||
|
@ -530,7 +530,7 @@ Procedure Reference
|
|||
> set-page-numbers-visible! - determines whether slide numbers are
|
||||
initially visible
|
||||
|
||||
> printing? - #t if the slides are begin durected to PostScript output
|
||||
> printing? - #t if the slides are being directed to PostScript output
|
||||
> condense? - #t if slides are being condensed (see overview)
|
||||
> (skip-slides n) - increment the slide counter by `n' without adding
|
||||
any slides.
|
||||
|
@ -585,7 +585,7 @@ Meanwhile, `runnable-id' is bound to a syntax object that wraps the
|
|||
used to comment out an expression from the pict, but have it present
|
||||
in the syntax object for evaluation.
|
||||
|
||||
The `string-id' is bound to a string reprsentation of the code that is
|
||||
The `string-id' is bound to a string representation of the code that is
|
||||
in the pict. This string is useful for copying to the clipboard with
|
||||
`(send the-clipboard set-clipboard-string string-id 0)'.
|
||||
|
||||
|
|
|
@ -19,7 +19,7 @@ To load a SRFI, use the following form:
|
|||
(require (lib "N.ss" "srfi"))
|
||||
|
||||
if you know the number of the SRFI you want to load. This is the
|
||||
prefered method, or this one:
|
||||
preferred method, or this one:
|
||||
|
||||
(require (lib "NAME.ss" "srfi" "N"))
|
||||
|
||||
|
@ -51,7 +51,7 @@ and should be required like this:
|
|||
|
||||
(require (lib "list.ss" "srfi" "1"))
|
||||
|
||||
which supplies the collading names with a prefix of 's:'
|
||||
which supplies the colliding names with a prefix of 's:'
|
||||
(e.g. "s:map", "s:reverse!") and is therefore suitable for requires in
|
||||
a module.
|
||||
|
||||
|
@ -60,7 +60,7 @@ like this:
|
|||
|
||||
(require (lib "time.ss" "srfi" "19"))
|
||||
|
||||
which supplies the collading names with a prefix of 'srfi:'
|
||||
which supplies the colliding names with a prefix of 'srfi:'
|
||||
(e.g. "srfi:date?", "srfi:date-second") and is therefore suitable for
|
||||
requires in a module.
|
||||
|
||||
|
@ -120,7 +120,7 @@ Notes:
|
|||
|
||||
,--------------------
|
||||
| *2 The time module does not export its time structure (you have to
|
||||
| use the time-* procedures.) It renames all the date-* accesors to
|
||||
| use the time-* procedures.) It renames all the date-* accessors to
|
||||
| tm:date-* so that you won't get errors when including this code in
|
||||
| other modules. Care most be taken NOT to confuse the internal date
|
||||
| structure with the PLT Scheme one, they are not the same, and all
|
||||
|
|
|
@ -242,7 +242,7 @@
|
|||
|
||||
ODBC 3.0.
|
||||
|
||||
Frees `handle', which may be an environment, connection, statment,
|
||||
Frees `handle', which may be an environment, connection, statement,
|
||||
or descriptor handle. Returns the value of `handle'.
|
||||
|
||||
> (free-stmt hstmt option)
|
||||
|
@ -408,7 +408,7 @@
|
|||
connection handle `hdbc'. The type of the return value depends
|
||||
on the symbol `infotype', which indicates the information requested.
|
||||
The optional argument `handle' is either a statement handle
|
||||
or a descript handle, and may be used only with certain
|
||||
or a descriptor handle, and may be used only with certain
|
||||
values of `infotype', as described below.
|
||||
|
||||
The significance of the values returned by get-info is beyond the
|
||||
|
@ -781,7 +781,7 @@
|
|||
sql-ad-drop-domain-default
|
||||
sql-ad-add-constraint-deferrable
|
||||
sql-ad-add-constraint-non-deferrable
|
||||
sql-ad-add-constraint-inititally-deferred
|
||||
sql-ad-add-constraint-initially-deferred
|
||||
sql-ad-add-constraint-initially-immediate)
|
||||
'sql-async-mode 'sql-am-connection, or
|
||||
'sql-am-statement, or
|
||||
|
@ -1236,7 +1236,7 @@
|
|||
|
||||
For a connection handle `hdbc', returns the value of the
|
||||
connection option specified by the symbol `option'.
|
||||
The permisible values of `option' are
|
||||
The permissible values of `option' are
|
||||
|
||||
'sql-access-mode
|
||||
'sql-autocommit
|
||||
|
@ -1300,7 +1300,7 @@
|
|||
|
||||
For a connection handle `hdbc', sets the option indicated by the
|
||||
symbol `option' to be `val'. The type of `val' depends on `attr'.
|
||||
The permisible values of `option' are:
|
||||
The permissible values of `option' are:
|
||||
|
||||
'sql-access-mode
|
||||
'sql-autocommit
|
||||
|
@ -1916,7 +1916,7 @@
|
|||
|
||||
Associates the sql-buffer `buff' and sql-indicator `ind'
|
||||
with a column of data denoted by the statement handle `hstmt'
|
||||
and column numer `colnum', an integer. Returns the value
|
||||
and column number `colnum', an integer. Returns the value
|
||||
of `hstmt'.
|
||||
|
||||
> (fetch hstmt)
|
||||
|
|
|
@ -20,7 +20,7 @@ into two parts; those added for the beginner macros, and those added
|
|||
for the mzscheme macros. However, since it is harder to alter the
|
||||
macro expansion which occurs in mzscheme, the latter set are added not
|
||||
during the actual macro expansion in mzscheme but as part of a pass
|
||||
over the code that occurs in the annotater between expansion and the
|
||||
over the code that occurs in the annotator between expansion and the
|
||||
main annotation. This procedure is called 'top-level-rewrite'.
|
||||
|
||||
Therefore, the stepper's syntax-property additions occur in two
|
||||
|
@ -181,7 +181,7 @@ stepper-and/or-clauses-consumed :
|
|||
(Transferred.)
|
||||
|
||||
stepper-skipto :
|
||||
this instructs the annotater to look inside the current expression
|
||||
this instructs the annotator to look inside the current expression
|
||||
along a given path for the expression to be annotated. In
|
||||
particular, the value bound to stepper-skipto must be a list whose
|
||||
elements are car, cdr, or syntax-e. (Not transferred)
|
||||
|
@ -191,7 +191,7 @@ Some uses:
|
|||
- applied to the spurious 'let' that's wrapped around a local.
|
||||
|
||||
Where it's used: the stepper-skipto label is used by the 2nd-pass
|
||||
macro-labeler and the annotater. Both are in annotate.ss. In addition
|
||||
macro-labeler and the annotator. Both are in annotate.ss. In addition
|
||||
to skipping inward, a stepper hint
|
||||
|
||||
stepper-else :
|
||||
|
@ -211,7 +211,7 @@ stepper-define-struct-hint :
|
|||
|
||||
stepper-test-suite-hint :
|
||||
this expression was the expression being tested in a test-suite-tool
|
||||
test. this hint indicates to the annotater that the expression should
|
||||
test. this hint indicates to the annotator that the expression should
|
||||
be annotated, even though it's not in one of the expected top-level
|
||||
shapes.
|
||||
|
||||
|
|
|
@ -1,6 +1,6 @@
|
|||
_String Constants_
|
||||
|
||||
This library provides the facility for multiple langauges in
|
||||
This library provides the facility for multiple languages in
|
||||
DrScheme's GUI. These are the exported syntactic forms and
|
||||
procedures from
|
||||
|
||||
|
@ -52,7 +52,7 @@ translation in the appropriate language.
|
|||
|
||||
The english-string-constants.ss is considered the master
|
||||
file -- string constants will be set there and translated
|
||||
into each of the other langauge files. In addition, the
|
||||
into each of the other language files. In addition, the
|
||||
english-string-constants.ss file should contain hints about
|
||||
the context of the strings whose symbol name might not be
|
||||
clear.
|
||||
|
@ -64,7 +64,7 @@ _STRINGCONSTANTS_ environment variable
|
|||
|
||||
If either of these environment variables are set, DrScheme
|
||||
shows you, during startup, which string constants are not
|
||||
yet defined for each langauge.
|
||||
yet defined for each language.
|
||||
|
||||
You can also specify which languages you are interested
|
||||
in. If either environment variable is bound to a symbol (as
|
||||
|
@ -75,4 +75,4 @@ messages for all the languages in the list. If either is
|
|||
bound to anything else, you see all of the languages.
|
||||
|
||||
The PLTSTRINGCONSTANTS environment variable takes precedence
|
||||
of the STRINGCONSTANTS environment variaable.
|
||||
of the STRINGCONSTANTS environment variable.
|
||||
|
|
|
@ -333,7 +333,7 @@ HTML values are almost any Scheme values.
|
|||
|4/3
|
||||
+----------
|
||||
|
||||
* Lists are iterated over, general pairs get recoursed too.
|
||||
* Lists are iterated over, general pairs get recursed too.
|
||||
+----------
|
||||
|> (output-html (list 1 'foo "foo" 0.10 (/ 4 3)))
|
||||
|1foofoo0.14/3
|
||||
|
@ -673,7 +673,7 @@ there is therefore a lot of related functionality.
|
|||
for the Scheme reader for the begin/end of a meta
|
||||
string, or a pair for different begin/end values.
|
||||
* `:split-lines?' if true, then generated strings that span several
|
||||
lines will be split so that each line is a seperate
|
||||
lines will be split so that each line is a separate
|
||||
string in the result (and a a space prefix for
|
||||
these lines is eliminated). (Default: #f).
|
||||
If "y" contains:
|
||||
|
@ -689,7 +689,7 @@ there is therefore a lot of related functionality.
|
|||
| :scheme? #t))))
|
||||
|<big><a href="c:\foo.htm">foo ?</a><b>FOO</b></big>
|
||||
+----------
|
||||
Finally, if there is a squence of two such meta-open tags, then a
|
||||
Finally, if there is a sequence of two such meta-open tags, then a
|
||||
sequence of two closing ones is expected, all on one line with an even
|
||||
number of characters between them. The two parts of the section
|
||||
between them are used as the new tokens. If "z" contains:
|
||||
|
@ -716,7 +716,7 @@ there is therefore a lot of related functionality.
|
|||
Attempt to relativize the given path according to the current path.
|
||||
This is used in case you want to create HTML objects in directories,
|
||||
refer to them according to their normal path and get it relative to
|
||||
the currect object. For example, in the source for the `a/b' object,
|
||||
the correct object. For example, in the source for the `a/b' object,
|
||||
a reference to `c/d' will turn to "../d.html". Search for this name
|
||||
below for more details.
|
||||
|
||||
|
@ -1132,7 +1132,7 @@ inheritance except when specified.
|
|||
processing so it is better to disable processing only for one
|
||||
attribute, for example: `::arg-funcs (list* :href #f (*arg-funcs*))'.
|
||||
This keyword is inherited, so you can do this at any form to modify
|
||||
evrything in it.
|
||||
everything in it.
|
||||
|
||||
* `::literal?' -- If true, then HTML post-processing is disabled for the
|
||||
body (see above for more details). Default: #f. This meta-keyword is
|
||||
|
@ -1528,7 +1528,7 @@ options:
|
|||
|
||||
(button*: ...)
|
||||
this is the actual HTML "button" wrapper, unlike the above `button:'
|
||||
which is just a shor for (input: :type 'button ...).
|
||||
which is just a short for (input: :type 'button ...).
|
||||
|
||||
(label~: label ...)
|
||||
a "label" wrapper, with a value for the `:for' attribute.
|
||||
|
@ -1633,7 +1633,7 @@ applet-params:, object-params:
|
|||
========================================================================
|
||||
4. Making it work
|
||||
|
||||
Now that woring with all the above should be clear, we reach the point
|
||||
Now that working with all the above should be clear, we reach the point
|
||||
of putting it all together in a script.
|
||||
|
||||
|
||||
|
@ -1653,13 +1653,13 @@ What I found most convenient is the following prefix:
|
|||
This will make it a /bin/sh script that will just execute mzscheme with
|
||||
the correct command-line arguments: `-r' is for running a script: short
|
||||
for `-fmv-' which stands for `-f' for loading an argument, `-m' for
|
||||
supressing the banner, `-v' for no interactive read-eval-print loop, and
|
||||
suppressing the banner, `-v' for no interactive read-eval-print loop, and
|
||||
`--' to specify that more arguments are passed to the script without
|
||||
further processing. The first "$0" argument is consumed by the `-f' --
|
||||
this is the actual script (the double-quotes are to protect file name
|
||||
with spaces from exploding to multiple arguments), and "$@" are other
|
||||
arguments that are passed to the script because of the `--' (again "$@"
|
||||
will send each argument, handeling spaces in them correctly). When
|
||||
will send each argument, handling spaces in them correctly). When
|
||||
MzScheme starts, it ignores the /bin/sh stuff and will happily proceed
|
||||
to execute the file. Stick to this template and be safe.
|
||||
|
||||
|
@ -1840,7 +1840,7 @@ bound to an HTML object with the given argument name, or an HTML object
|
|||
with a `:name' attribute equal to the given argument, or an HTML object
|
||||
whose processed name (the `:name' value with `*html-target-dir*' and
|
||||
`*html-suffix*') is equal to the given argument. All this makes it
|
||||
convenient to run on script inputs: with arguments it will genrate only
|
||||
convenient to run on script inputs: with arguments it will generate only
|
||||
the requested pages, and without it will create all defined pages.
|
||||
Thing you should know if you use this approach:
|
||||
|
||||
|
|
|
@ -54,9 +54,9 @@ _kerncase.ss_: matching fully-expanded expressions
|
|||
forms must have their normal bindings in the context of the
|
||||
`kernel-syntax-case' expression.)
|
||||
|
||||
The `trans?-expr' boolean expression replaces the comparision
|
||||
The `trans?-expr' boolean expression replaces the comparison
|
||||
procedure, and instead selects simply between normal-phase
|
||||
comparisions or transformer-phase comparisions. The `clause's are
|
||||
comparisons or transformer-phase comparisons. The `clause's are
|
||||
the same as in `syntax-case*'.
|
||||
|
||||
> (kernel-form-identifier-list syntax) - returns a list of identifiers
|
||||
|
@ -79,8 +79,8 @@ _toplevel.ss_: helper for moduleless compilation and expansion
|
|||
expanding a `begin' is the same as expanding separate top-level
|
||||
expressions.)
|
||||
|
||||
The `stx' argument should have a context already, possibily
|
||||
introduced with `namespacae-inroduce-syntax'.
|
||||
The `stx' argument should have a context already, possibly
|
||||
introduced with `namespacae-introduce-syntax'.
|
||||
|
||||
> (expand-top-level-with-compile-time-evals/flatten stx) -
|
||||
Just like expand-top-level-with-compile-time-evals,
|
||||
|
@ -90,8 +90,8 @@ _toplevel.ss_: helper for moduleless compilation and expansion
|
|||
|
||||
> (expand-syntax-top-level-with-compile-time-evals stx)
|
||||
Like `expand-top-level-with-compile-time-evals', but `stx' should
|
||||
have a context already, possibily introduced with
|
||||
`namespacae-inroduce-syntax'.
|
||||
have a context already, possibly introduced with
|
||||
`namespacae-introduce-syntax'.
|
||||
|
||||
> (eval-compile-time-part-of-top-level stx) - evaluates
|
||||
expansion-time code in the fully expanded top-level expression
|
||||
|
@ -115,7 +115,7 @@ _define.ss_: handling all the same function forms as `define'
|
|||
possibly with a different keyword) and returns two values: the
|
||||
defined identifier and the right-hand side expression.
|
||||
|
||||
To generate the right-hand side, this funciton may need to insert
|
||||
To generate the right-hand side, this function may need to insert
|
||||
uses of `lambda'. The `lambda-id-stx' argument provides a suitable
|
||||
`lambda' identifier.
|
||||
|
||||
|
@ -189,7 +189,7 @@ _struct.ss_: generating the same names as `define-struct'
|
|||
continue-macro-id continue-data-stx)
|
||||
> (generate-delayed-struct-declaration stx make-make-make-struct-type)
|
||||
|
||||
These two procedurs cooperate to implement the core of a
|
||||
These two procedures cooperate to implement the core of a
|
||||
`define-struct' expansion that works for embedded definition
|
||||
contexts (where lookup of supertype information may need to be
|
||||
delayed).
|
||||
|
@ -257,7 +257,7 @@ _docprovide.ss_: attaching documentation to exports
|
|||
exports names and records documentation information.
|
||||
|
||||
!! IMPORTANT: For now, the exporting module must be required with a
|
||||
`lib' or `file' form. Releatiuve paths do no work correctly !!
|
||||
`lib' or `file' form. Relative paths do no work correctly !!
|
||||
|
||||
The `doc-label-id' identifier is used as a key for accessing the
|
||||
documentation through `lookup-documentation'. The actual
|
||||
|
@ -385,7 +385,7 @@ currently exist).
|
|||
import hierarchy starting from a given module path.
|
||||
|
||||
======================================================================
|
||||
_readerr.ss_: signalling parse errors
|
||||
_readerr.ss_: signaling parse errors
|
||||
======================================================================
|
||||
|
||||
> (raise-read-error msg-string source-v line-k col-k pos-k span-k)
|
||||
|
@ -400,7 +400,7 @@ _readerr.ss_: signalling parse errors
|
|||
the source location --- usually a file path string. Each of the
|
||||
`line-k', `pos-k' arguments is #f or a positive exact integer
|
||||
representing the location within `source-name' (as much as known),
|
||||
`col-k' is a non-negaytive exact integer for the source column (if
|
||||
`col-k' is a non-negative exact integer for the source column (if
|
||||
known), and `span-k' is #f or a non-negative exact integer for an
|
||||
item range starting from the indicated position.
|
||||
|
||||
|
@ -408,7 +408,7 @@ _readerr.ss_: signalling parse errors
|
|||
|
||||
Like `raise-read-error', but raises
|
||||
> exn:read:eof
|
||||
insteda of `exn:read'.
|
||||
instead of `exn:read'.
|
||||
|
||||
======================================================================
|
||||
_boundmap.ss_: mapping identifiers based on bound-identifier=? and module-identifier=?
|
||||
|
|
|
@ -2,7 +2,7 @@
|
|||
Overview
|
||||
--------
|
||||
|
||||
This canvas test frame is for checking the behvaiour of the
|
||||
This canvas test frame is for checking the behavior of the
|
||||
scrollbars. Canvas scrollbars work in one of two modes:
|
||||
1) Managing: the scrollbar determines the size and offset of
|
||||
the canvas's drawing area.
|
||||
|
@ -13,9 +13,9 @@ In the test frame, the top canvas is initially unmanaged, and the
|
|||
bottom is managed.
|
||||
|
||||
An HVCanvas has both horizontal and vertical scrollbars, but the
|
||||
scrollbars are initially disabled. Clikcing the "Enable Vertical"
|
||||
scrollbars are initially disabled. Clicking the "Enable Vertical"
|
||||
checkbox enables the vertical scroll. A VCanvas has only a vertical
|
||||
scrollbar; clicking "ENable Horizontal" in this case has no effect.
|
||||
scrollbar; clicking "Enable Horizontal" in this case has no effect.
|
||||
When a canvas is managed by its scrollbars and a scrollbar is missing
|
||||
in a particular direction, it should act the same as an unmanaged
|
||||
canvas in that direction.
|
||||
|
@ -37,7 +37,7 @@ On each canvas, the following are painted at 0,0:
|
|||
bottom canvas's boundaries are probably beyond the visible region.)
|
||||
When the canvas is managed with a vertical scrollbar, the bottom
|
||||
boundary line might not be visible, i.e., it might be clipped - but
|
||||
it must be clipped eactly in that case.
|
||||
it must be clipped exactly in that case.
|
||||
|
||||
As the scroll is changed for the managed canvas, the information will
|
||||
move, because the scrolls automatically adjust the offset of the
|
||||
|
|
|
@ -10,7 +10,7 @@ If there are no items:
|
|||
* Click on the choice box. Make sure that nothing prints to the
|
||||
console as a result.
|
||||
|
||||
* Click "Append"; "Extra 1" should appear in the list of tiems.
|
||||
* Click "Append"; "Extra 1" should appear in the list of items.
|
||||
For a choice, it should be immediately selected.
|
||||
|
||||
* Click "Append" again. The selection should not change.
|
||||
|
@ -28,7 +28,7 @@ If there are no items:
|
|||
For a multi-selection list, jump down to "Multiple Selections".
|
||||
|
||||
If there are items, select each once in order (single-click for
|
||||
lists). After each solection, "Changed N" should appear in the
|
||||
lists). After each selection, "Changed N" should appear in the
|
||||
console (where N is the position of the item, counting from 0) for a
|
||||
choice item, "Change (N)" for a list box; in either case, the
|
||||
"Changed" line is followed by "Callback Ok". This should be printed
|
||||
|
@ -40,14 +40,14 @@ For a choice, click to pop-up the menu, but don't select anything. for
|
|||
both cases, the selection should not change and nothing should print
|
||||
in the console.
|
||||
|
||||
Click the "Append" button. The seletion should not change, but a new
|
||||
Click the "Append" button. The selection should not change, but a new
|
||||
item "Extra 1" should appear.
|
||||
|
||||
Click the "Append" button again.
|
||||
|
||||
Select the first newly added item.
|
||||
|
||||
Click on the "check" button. In the console, "content: " whould be
|
||||
Click on the "check" button. In the console, "content: " would be
|
||||
printed along with a list of strings. That list should match the
|
||||
items in the choice/list.
|
||||
|
||||
|
@ -89,7 +89,7 @@ Click on all parts of the control. The callback should never be
|
|||
|
||||
Click on all the "Select" buttons. For the top buttons and "by
|
||||
Simulate" buttons (but not the "bad" ones), an exception should be
|
||||
reported. Nothing should happend for the "by Name" buttons.
|
||||
reported. Nothing should happened for the "by Name" buttons.
|
||||
|
||||
Click on "Check". The empty item list should be reported in the
|
||||
console.
|
||||
|
@ -126,7 +126,7 @@ Scroll to the top and select the first item. Click "Visible
|
|||
item. If an item is only partly visible, it should not be counted.
|
||||
|
||||
Scroll down exactly one item's height without changing the
|
||||
selection. Click "Visible Incices" again. The top should change to 1
|
||||
selection. Click "Visible Indices" again. The top should change to 1
|
||||
but the count should be the same.
|
||||
|
||||
On some platforms, you can scroll to partially show the first item.
|
||||
|
@ -139,7 +139,7 @@ Make the window taller to show at least one more item. Try "Visible
|
|||
Click "Select Last". The list should scroll to the end. Try "Visible
|
||||
Indices" again.
|
||||
|
||||
Make the list box taller than all its items. (It may be necssary to
|
||||
Make the list box taller than all its items. (It may be necessary to
|
||||
delete some items by selecting them and hitting the "Delete" button.)
|
||||
Click "Visible Indices" and make sure that the visible count is still
|
||||
more than the number of items.
|
||||
|
@ -149,7 +149,7 @@ Deleting >> Lists Only <<
|
|||
|
||||
Select an item in the middle of the list.
|
||||
|
||||
Hit "Delete". The item should disappear, and nothing shold be
|
||||
Hit "Delete". The item should disappear, and nothing should be
|
||||
selected.
|
||||
|
||||
Append a new item.
|
||||
|
|
|
@ -1,7 +1,7 @@
|
|||
The drawing area should have the following features:
|
||||
|
||||
At the top-left, when the window is opened for the first time, you
|
||||
shoudl see a hollow box with a line sticking out to the bottom
|
||||
should see a hollow box with a line sticking out to the bottom
|
||||
left. Repainting the canvas should produce instead a solid box and
|
||||
no line. Repainting with Pixmap or Bitmap should always produce
|
||||
the hollow box and line.
|
||||
|
@ -30,18 +30,18 @@ The drawing area should have the following features:
|
|||
|
||||
Toward the right should be three columns of boxes, with a fourth
|
||||
column that starts with a box. All boxes should have a red border.
|
||||
In the first thre columns, the boxes shold contain lines on a
|
||||
In the first three columns, the boxes should contain lines on a
|
||||
background that matches the normal background (i.e., either white
|
||||
or cyan). The lines should be black for the left colum, and green
|
||||
or cyan). The lines should be black for the left column, and green
|
||||
for the second and third columns. In the fourth column, the shapes
|
||||
should be filled with the platform-specific panel background
|
||||
pattern; the third shape should be a semi-circle with no outline
|
||||
on the bottm edge.
|
||||
on the bottom edge.
|
||||
|
||||
Further right (to the the right of the columns) should appear an
|
||||
X, a cross, and an narrow X tilted NW. Each should be drawn in
|
||||
green (5 pixels wide) with a thin black line centered along each
|
||||
green line. Scaling the piture should make the green line thicker,
|
||||
green line. Scaling the picture should make the green line thicker,
|
||||
but not the black line, and the black line should stay centered.
|
||||
|
||||
Under the columns of boxes, a black box should be filled with an 25%
|
||||
|
@ -97,7 +97,7 @@ The drawing area should have the following features:
|
|||
|
||||
Arcs: The leftmost should be the top half of an ellipse (it's
|
||||
formed via two arcs); the rightmost should be a filled wedge
|
||||
from 90 degrees to 180 degress. The arcs are part of an
|
||||
from 90 degrees to 180 degrees. The arcs are part of an
|
||||
ellipse 40 tall and 30 wide (i.e., stretched slightly in the
|
||||
vertical direction from a circle).
|
||||
|
||||
|
@ -108,13 +108,13 @@ The drawing area should have the following features:
|
|||
Also, it's drawn in xor mode, so it should flip black to
|
||||
white wherever the octagon line runs over the shapes of the
|
||||
middle section. The bitmaps of the bottom region are drawn
|
||||
afterwards, and wil therefore hide parts of the octagon
|
||||
afterwards, and will therefore hide parts of the octagon
|
||||
line, although the MrEd logo is also drawn in XOR mode so it
|
||||
shouldn't obscure the octagon line.
|
||||
|
||||
Bottom section:
|
||||
|
||||
Images: MrEd logo (b & w), drawn in XOR mode, so the octagin line
|
||||
Images: MrEd logo (b & w), drawn in XOR mode, so the octagon line
|
||||
should be toggled where the black part of the MrEd logo
|
||||
intersects with the line. This changes with the
|
||||
"MrEd XOR" choice control (see below).
|
||||
|
@ -135,7 +135,7 @@ The drawing area should have the following features:
|
|||
Stippled boxes, in a blue box w/black border, four black-outlined
|
||||
shapes:
|
||||
Sqaure - green down-arrows on blue field
|
||||
Cirle - green down-arrows on background (cyan or white) field
|
||||
Circle - green down-arrows on background (cyan or white) field
|
||||
Square - bb logo
|
||||
Square - green cross-hatch on blue
|
||||
|
||||
|
@ -161,7 +161,7 @@ The drawing area should have the following features:
|
|||
as paths.
|
||||
|
||||
Four lines (to right of red shapes): in 'unsmoothed or 'aligned
|
||||
mode, the lines should appear euqally spaced at scale 1, but
|
||||
mode, the lines should appear equally spaced at scale 1, but
|
||||
scale 2 should show the middle lines closer by two pixels; the
|
||||
'smoothed mode should approximate this at scale 1. At scale 2,
|
||||
'unsmoothed and 'aligned should look the same.
|
||||
|
@ -172,8 +172,8 @@ The drawing area should have the following features:
|
|||
'smoothed mode, but in 'smoothed mode or at scale 2, they should
|
||||
touch.
|
||||
|
||||
Four suqares with overbar (bottom of drawing): the suqares,
|
||||
which are strteched bitmaps, should touch, and the four squares
|
||||
Four squares with overbar (bottom of drawing): the squares,
|
||||
which are stretched bitmaps, should touch, and the four squares
|
||||
should have the same span as the overbar line.
|
||||
|
||||
The image should look the same regardless of the top radio button
|
||||
|
@ -201,14 +201,14 @@ Clipping should slip the drawing to a particular shape:
|
|||
rectangle - a 10-pixel strip 100 pixels from the left
|
||||
|
||||
octagon - the content of the big outlined octagon; some
|
||||
part of the octagone outline is clipped
|
||||
part of the octagon outline is clipped
|
||||
|
||||
circle - a circle inscribed in the octagon's bounding
|
||||
box
|
||||
|
||||
wedge - pi/4 to 3pi/4 of circle
|
||||
|
||||
round rectangle - a rounded rect inscrobed in the the blue box for
|
||||
round rectangle - a rounded rect inscribed in the the blue box for
|
||||
testing stipples
|
||||
|
||||
unions, intersects, subtracts - hopefully obvious
|
||||
|
@ -243,9 +243,9 @@ The "Clock" button tests a range of wedges. Each wedge has a 1-pixel
|
|||
the wedge part and empty part (so the wedge starts small and grows
|
||||
larger this time around).
|
||||
The orange wedge is drawn just before the bitmaps, so they appear on
|
||||
top of the orange wedge, but the wegde paints over other things. If
|
||||
top of the orange wedge, but the wedge paints over other things. If
|
||||
the "Pixmap" box is checked and the "Polka" clipping region is
|
||||
selected, the result is an animtation where you can only see the
|
||||
selected, the result is an animation where you can only see the
|
||||
wedge grow and move through the polka-dot holes in the purple field.
|
||||
|
||||
The "Clip Clock" button is similar to "Clock", except that all drawing
|
||||
|
@ -293,7 +293,7 @@ The "MrEd XOR" menu selects a icon:
|
|||
|
||||
Finally, print these instructions by hitting the "Print" button at the
|
||||
top of the "What Should I See?" window. The following lines are for
|
||||
the printing test; they should wrap aroundneatly on the printed
|
||||
the printing test; they should wrap around neatly on the printed
|
||||
page. (Don't add any newlines.) Check to make sure no lines are
|
||||
skipped or duplicated across page breaks. Try different page
|
||||
orientations.
|
||||
|
|
|
@ -74,7 +74,7 @@ Window Resizing
|
|||
Stretch the window vertically. Stretch it horizontally. Unless the
|
||||
frame was created with "all stechy" on, then messages, buttons, check
|
||||
boxes, and radio boxes should not stretch. Choice and text items
|
||||
should only strech horizontally. Sliders and gauges should only
|
||||
should only stretch horizontally. Sliders and gauges should only
|
||||
resize in the major direction.
|
||||
|
||||
If "all stretchy" was on, then everything in the left column should
|
||||
|
@ -131,9 +131,9 @@ disabled.
|
|||
* enable/disable all the controls through each panel
|
||||
checkbox
|
||||
|
||||
* click each checkbox to disble an item; click on the
|
||||
* click each checkbox to disable an item; click on the
|
||||
item to make sure it's disabled; recheck the checkbox;
|
||||
make sure the item is re-enebaled
|
||||
make sure the item is re-enabled
|
||||
|
||||
* disable all the controls; disable and re-enable the
|
||||
whole panel; make sure the controls are still disabled
|
||||
|
@ -142,14 +142,14 @@ disabled.
|
|||
make sure the controls are still not enabled; re-enable
|
||||
the panel and check that the controls are enabled
|
||||
|
||||
* disbale the panel; diable all the controls; enable the
|
||||
* disable the panel; disable all the controls; enable the
|
||||
panel and make sure the controls are still disabled;
|
||||
enable all the controls
|
||||
|
||||
* repeat the three steps above with the other panel checkbox
|
||||
|
||||
* repeat the three steps for radioboxes and radio items,
|
||||
sintead of panels and controls
|
||||
instead of panels and controls
|
||||
|
||||
Relabeling
|
||||
----------
|
||||
|
@ -162,9 +162,9 @@ it depends:
|
|||
|
||||
- message: <down-right arrow>
|
||||
- button: <down-left arrow>
|
||||
- checbox: <BB icon>
|
||||
- checkbox: <BB icon>
|
||||
|
||||
Note that radio items can't be relabelled.
|
||||
Note that radio items can't be relabeled.
|
||||
|
||||
Be sure to click each button twice, to make sure that the original
|
||||
label is restored.
|
||||
|
@ -216,7 +216,7 @@ same panel as the "New Deleted" control, but each subwindow<%> is
|
|||
created with the 'deleted style, which means that the subwindow<%> is
|
||||
initially hidden and deleted. The "*Activate Last*" item activates
|
||||
the last-created subwindow<%>, i.e., it shows the subwindow<%> and
|
||||
adjusts the panel size to accomodate the activated window<%>. The key
|
||||
adjusts the panel size to accommodate the activated window<%>. The key
|
||||
part of this test is that no deleted subwindow<%> is shown, and no
|
||||
deleted subwindow<%> affects the panel's geometry.
|
||||
|
||||
|
@ -262,20 +262,20 @@ under windows, the key info is immediately replaced with mouse info.)
|
|||
Event Filtering
|
||||
---------------
|
||||
|
||||
When "Drop Mouse Events" is checked at the bottom of the thrid column,
|
||||
When "Drop Mouse Events" is checked at the bottom of the third column,
|
||||
all other controls (except "Drop Mouse Events" and "Drop Key Events")
|
||||
shold cease to respond to mouse events. The event indicator will still
|
||||
should cease to respond to mouse events. The event indicator will still
|
||||
work. Keyboard events should not be affected (though it may be hard to
|
||||
get the focus somewhere interesting).
|
||||
|
||||
Try every control with mouse events dropped.
|
||||
|
||||
"Drop Key Events" does the obvious thing. Try every keybord-responding
|
||||
"Drop Key Events" does the obvious thing. Try every keyboard-responding
|
||||
control with events dropped. Try dialog navigation keys on other
|
||||
controls, such as TAB or left-arrow.
|
||||
|
||||
Different Configuations
|
||||
-----------------------
|
||||
Different Configurations
|
||||
------------------------
|
||||
|
||||
Each Frame can be created in several different configurations (32 or
|
||||
64 of them!).
|
||||
|
|
|
@ -8,7 +8,7 @@ Change the slider value in each way allowed by the control (dragging,
|
|||
intermediate callbacks may be reported.
|
||||
|
||||
Click "Up" until the slider is at the top; a mismatch exception should
|
||||
be reported. Click "Down" once aand verify that the slider is at 10.
|
||||
be reported. Click "Down" once and verify that the slider is at 10.
|
||||
|
||||
Repeat the above step for "Down" (checking for an exception when the
|
||||
slider is already at its minimum value).
|
||||
|
|
|
@ -38,7 +38,7 @@ which accepts a string of arbitrary LaTeX code, and the MrEd set
|
|||
includes `dc', which accepts an arbitrary Scheme procedure for drawing
|
||||
to a dc<%>.
|
||||
|
||||
When creating pictures with the obsolte `picture' or `cons-picture'
|
||||
When creating pictures with the obsolete `picture' or `cons-picture'
|
||||
functions, or when finding relative picture locations with the
|
||||
obsolete `find-lt', etc., the coordinate system is upside-down: (0, 0)
|
||||
is in the lower left.
|
||||
|
@ -497,7 +497,7 @@ Bounding-Box Adjusters:
|
|||
> (inset pict li ti ri bi) -> pict
|
||||
|
||||
Extends picture size by adding the give amounts to the
|
||||
corersponding side; ascent and descent are extended, too.
|
||||
corresponding side; ascent and descent are extended, too.
|
||||
|
||||
> (clip-descent pict) -> pict
|
||||
|
||||
|
@ -549,7 +549,7 @@ Finders:
|
|||
> (ctl-find pict pict-path) -> dx dy
|
||||
> (cbl-find pict pict-path) -> dx dy
|
||||
|
||||
Finds an embedded pictur.
|
||||
Finds an embedded picture.
|
||||
A pict-path is either
|
||||
pict
|
||||
non-empty-pict-path-list
|
||||
|
@ -767,7 +767,7 @@ Obsolete functions
|
|||
|
||||
> (picture w h command-list) -> pict
|
||||
|
||||
Obsolte: describes a picture with low-level commands; see below.
|
||||
Obsolete: describes a picture with low-level commands; see below.
|
||||
|
||||
> (cons-picture pict command-list) -> pict
|
||||
> (cons-picture* pict command-list) -> pict
|
||||
|
@ -814,7 +814,7 @@ Obsolete functions
|
|||
> (arrow-line dx dy size) -> pict
|
||||
> (arrows-line dx dy size) -> pict
|
||||
|
||||
Obsolte versions of the `line+arrow[s]' functions,
|
||||
Obsolete versions of the `line+arrow[s]' functions,
|
||||
where the vertical delta is negated.
|
||||
[MrEd only, in utils.ss]
|
||||
|
||||
|
|
|
@ -135,7 +135,7 @@ Parameters
|
|||
> read-comments : Bool
|
||||
Default: #f
|
||||
Comments, by definition, should be ignored by programs. However,
|
||||
interoperating with ad hoc extentions to other languages sometimes
|
||||
interoperating with ad hoc extensions to other languages sometimes
|
||||
requires processing comments anyway.
|
||||
|
||||
> xexpr-drop-empty-attributes : Bool
|
||||
|
@ -165,8 +165,8 @@ What this Library Doesn't Provide
|
|||
|
||||
Document Type Declaration (DTD) processing
|
||||
Validation
|
||||
Expanding user-defined entites
|
||||
Reading user-defined entites in attributes
|
||||
Expanding user-defined entities
|
||||
Reading user-defined entities in attributes
|
||||
Unicode support
|
||||
|
||||
XML Datatype Details
|
||||
|
|
|
@ -145,7 +145,7 @@ SRP_NAMED_CONSTANT alterDomainBits[] = {
|
|||
{ "sql-ad-drop-domain-default", SQL_AD_DROP_DOMAIN_DEFAULT },
|
||||
{ "sql-ad-add-constraint-deferrable", SQL_AD_ADD_CONSTRAINT_DEFERRABLE },
|
||||
{ "sql-ad-add-constraint-non-deferrable", SQL_AD_ADD_CONSTRAINT_NON_DEFERRABLE },
|
||||
{ "sql-ad-add-constraint-inititally-deferred", SQL_AD_ADD_CONSTRAINT_INITIALLY_DEFERRED },
|
||||
{ "sql-ad-add-constraint-initially-deferred", SQL_AD_ADD_CONSTRAINT_INITIALLY_DEFERRED },
|
||||
{ "sql-ad-add-constraint-initially-immediate", SQL_AD_ADD_CONSTRAINT_INITIALLY_IMMEDIATE },
|
||||
};
|
||||
#endif
|
||||
|
|
Loading…
Reference in New Issue
Block a user