[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
7.1 Data Structures | Various data structures. | |
7.2 Sorting and Searching | ||
7.3 Procedures | Miscellaneous utility procedures. | |
7.4 Standards Support | Support for Scheme Standards. | |
7.5 Session Support | REPL and Debugging. | |
7.6 System Interface | 'system, 'getenv, and other programs. | |
7.7 Extra-SLIB Packages | Outside the envelope. |
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
7.1.1 Arrays | 'array | |
7.1.2 Subarrays | 'subarray | |
7.1.3 Array Mapping | 'array-for-each | |
7.1.4 Association Lists | 'alist | |
7.1.5 Byte | 'byte | |
7.1.6 Byte/Number Conversions | 'byte-number | |
7.1.7 MAT-File Format | 'matfile | |
7.1.8 Portable Image Files | 'pnm | |
7.1.9 Collections | 'collect | |
7.1.10 Dynamic Data Type | 'dynamic | |
7.1.11 Hash Tables | 'hash-table | |
7.1.12 Macroless Object System | 'object | |
7.1.16 Priority Queues | 'priority-queue | |
7.1.17 Queues | 'queue | |
7.1.18 Records | 'record |
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Returns #t
if the obj is an array, and #f
if not.
array?
. A disjoint array predicate can
be written:
(define (strict-array? obj) (and (array? obj) (not (string? obj)) (not (vector? obj)))) |
Returns #t
if array1 and array2 have the same rank and shape and the
corresponding elements of array1 and array2 are equal?
.
(array=? (create-array '#(foo) 3 3) (create-array '#(foo) '(0 2) '(0 2))) => #t |
Creates and returns an array of type prototype with dimensions bound1, bound2, ... and filled with elements from prototype. prototype must be an array, vector, or string. The implementation-dependent type of the returned array will be the same as the type of prototype; except if that would be a vector or string with non-zero origin, in which case some variety of array will be returned.
If the prototype has no elements, then the initial contents of the returned array are unspecified. Otherwise, the returned array will be filled with the element at the origin of prototype.
(create-array '#(foo) 3 3) == (create-array '#(foo) '(0 2) '(0 2)) |
make-shared-array
can be used to create shared subarrays of other
arrays. The mapper is a function that translates coordinates in
the new array into coordinates in the old array. A mapper must be
linear, and its range must stay within the bounds of the old array, but
it can be otherwise arbitrary. A simple example:
(define fred (create-array '#(#f) 8 8)) (define freds-diagonal (make-shared-array fred (lambda (i) (list i i)) 8)) (array-set! freds-diagonal 'foo 3) (array-ref fred 3 3) => FOO (define freds-center (make-shared-array fred (lambda (i j) (list (+ 3 i) (+ 3 j))) 2 2)) (array-ref freds-center 0 0) => FOO |
Returns the number of dimensions of obj. If obj is not an array, 0 is returned.
Returns a list of inclusive bounds.
(array-shape (create-array '#() 3 5)) => ((0 2) (0 4)) |
array-dimensions
is similar to array-shape
but replaces
elements with a 0 minimum with one greater than the maximum.
(array-dimensions (create-array '#() 3 5)) => (3 5) |
Returns #t
if its arguments would be acceptable to
array-ref
.
Returns the (index1, index2, ...) element of array.
Stores obj in the (index1, index2, ...) element of array. The value returned
by array-set!
is unspecified.
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
selects a subset of an array. For array of rank n, there must be at least n selects arguments. For 0 <= j < n, selectsj is either an integer, a list of two integers within the range for the jth index, or #f.
When selectsj is a list of two integers, then the jth index is restricted to that subrange in the returned array.
When selectsj is #f, then the full range of the jth index is accessible in the returned array. An elided argument is equivalent to #f.
When selectsj is an integer, then the rank of the returned array is less than array, and only elements whose jth index equals selectsj are shared.
> (define ra '#2A((a b c) (d e f))) #<unspecified> > (subarray ra 0 #f) #1A(a b c) > (subarray ra 1 #f) #1A(d e f) > (subarray ra #f 1) #1A(b e) > (subarray ra '(0 1) #f) #2A((a b c) (d e f)) > (subarray ra #f '(0 1)) #2A((a b) (d e)) > (subarray ra #f '(1 2)) #2A((b c) (e f)) |
Behaves like subarray, but aligns the returned array origin to 0 ....
Returns an array shared with array but with a different origin. The coords are the exact integer coordinates of the new origin. Indexes corresponding to missing or #f coordinates are not realigned.
For example:
(define ra2 (create-array '#(5) '(5 9) '(-4 0))) (array-shape ra2) => ((5 9) (-4 0)) (array-shape (array-align ra2 0 0)) => ((0 4) (0 4)) (array-shape (array-align ra2 0)) => ((0 4) (-4 0)) (array-shape (array-align ra2)) => ((5 9) (-4 0)) (array-shape (array-align ra2 0 #f)) => ((0 4) (-4 0)) (array-shape (array-align ra2 #f 0)) => ((5 9) (0 4)) |
Returns a subarray sharing contents with array except for slices removed from either side of each dimension. Each of the trims is an exact integer indicating how much to trim. A positive s trims the data from the lower end and reduces the upper bound of the result; a negative s trims from the upper end and increases the lower bound.
For example:
(array-trim '#(0 1 2 3 4) 1) => #1A(1 2 3 4) ;; shape is ((0 3)) (array-trim '#(0 1 2 3 4) -1) => #1A(0 1 2 3) ;; shape is ((1 4)) (require 'array-for-each) (define (centered-difference ra) (array-map - (array-trim ra 1) (array-trim ra -1))) (define (forward-difference ra) (array-map - (array-trim ra 1) ra)) (define (backward-difference ra) (array-map - ra (array-trim ra -1))) (centered-difference '#(0 1 3 5 9 22)) => #1A(3 4 6 17) ;;shape is ((1 4)) (backward-difference '#(0 1 3 5 9 22)) => #1A(1 2 2 4 13) ;; shape is ((1 5)) (forward-difference '#(0 1 3 5 9 22)) => #(1 2 2 4 13) ;; shape is ((0 4)) |
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
array1, ... must have the same number of dimensions as array0 and have a range for each index which includes the range for the corresponding index in array0. proc is applied to each tuple of elements of array1 ... and the result is stored as the corresponding element in array0. The value returned is unspecified. The order of application is unspecified.
array2, ... must have the same number of dimensions as array1 and have a range for each index which includes the range for the corresponding index in array1. proc is applied to each tuple of elements of array1, array2, ... and the result is stored as the corresponding element in a new array of type prototype. The new array is returned. The order of application is unspecified.
proc is applied to each tuple of elements of array0 ... in row-major order. The value returned is unspecified.
Returns an array of lists of indexes for array such that, if li is a list of indexes for which array is defined, (equal? li (apply array-ref (array-indexes array) li)).
applies proc to the indices of each element of array in turn, storing the result in the corresponding element. The value returned and the order of application are unspecified.
One can implement array-indexes as
(define (array-indexes array) (let ((ra (apply create-array '#() (array-shape array)))) (array-index-map! ra (lambda x x)) ra)) |
(define (apl:index-generator n) (let ((v (make-vector n 1))) (array-index-map! v (lambda (i) i)) v)) |
Copies every element from vector or array source to the corresponding element of destination. destination must have the same rank as source, and be at least as large in each dimension. The order of copying is unspecified.
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Alist functions provide utilities for treating a list of key-value pairs as an associative database. These functions take an equality predicate, pred, as an argument. This predicate should be repeatable, symmetric, and transitive.
Alist functions can be used with a secondary index method such as hash tables for improved performance.
Returns an association function (like assq
, assv
, or
assoc
) corresponding to pred. The returned function
returns a key-value pair whose key is pred
-equal to its first
argument or #f
if no key in the alist is pred-equal to the
first argument.
Returns a procedure of 2 arguments, alist and key, which
returns the value associated with key in alist or #f
if
key does not appear in alist.
Returns a procedure of 3 arguments, alist, key, and value, which returns an alist with key and value associated. Any previous value associated with key will be lost. This returned procedure may or may not have side effects on its alist argument. An example of correct usage is:
(define put (alist-associator string-ci=?)) (define alist '()) (set! alist (put alist "Foo" 9)) |
Returns a procedure of 2 arguments, alist and key, which returns an alist with an association whose key is key removed. This returned procedure may or may not have side effects on its alist argument. An example of correct usage is:
(define rem (alist-remover string-ci=?)) (set! alist (rem alist "foo")) |
Returns a new association list formed by mapping proc over the keys and values of alist. proc must be a function of 2 arguments which returns the new value part.
Applies proc to each pair of keys and values of alist. proc must be a function of 2 arguments. The returned value is unspecified.
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Some algorithms are expressed in terms of arrays of small integers. Using Scheme strings to implement these arrays is not portable vis-a-vis the correspondence between integers and characters and non-ascii character sets. These functions abstract the notion of a byte.
k must be a valid index of bytes. byte-ref
returns byte k of bytes using
zero-origin indexing.
k must be a valid index of bytes, and byte must be a small
nonnegative integer. byte-set!
stores byte in element k of bytes and
returns an unspecified value.
make-bytes
returns a newly allocated byte-array of length k. If byte is
given, then all elements of the byte-array are initialized to byte,
otherwise the contents of the byte-array are unspecified.
bytes-length
returns length of byte-array bytes.
Returns a newly allocated byte-array composed of the small nonnegative arguments.
bytes->list
returns a newly allocated list of the bytes that make up the
given byte-array.
list->bytes
returns a newly allocated byte-array formed from the small
nonnegative integers in the list bytes.
Bytes->list
and list->bytes
are inverses so far as
equal?
is concerned.
Returns a newly allocated copy of the given bytes.
Reverses the order of byte-array bytes.
Returns a newly allocated bytes-array consisting of the elements of bytes in reverse order.
open-file
with 'rb or
'wb modes argument will return a binary port if the Scheme
implementation supports it.
current-output-port
.
current-input-port
.
read-bytes
and
write-bytes
, the sign of the length argument determines the
endianness (order) of bytes. Positive treats them as big-endian,
the first byte input or output is highest order. Negative treats
them as little-endian, the first byte input or output is the lowest
order.
Once read in, SLIB treats byte sequences as big-endian. The multi-byte sequences produced and used by number conversion routines see section 7.1.6 Byte/Number Conversions are always big-endian.
read-bytes
returns a newly allocated bytes-array filled with
(abs n)
bytes read from port. If n is positive, then
the first byte read is stored at index 0; otherwise the last byte
read is stored at index 0. Note that the length of the returned
string will be less than (abs n)
if port reaches
end-of-file.
port may be omitted, in which case it defaults to the value returned
by current-input-port
.
write-bytes
writes (abs n)
bytes to output-port port. If n is
positive, then the first byte written is index 0 of bytes; otherwise
the last byte written is index 0 of bytes. write-bytes
returns an unspecified
value.
port may be omitted, in which case it defaults to the value returned
by current-output-port
.
substring-read!
and substring-write
provide
lower-level procedures for reading and writing blocks of bytes. The
relative size of start and end determines the order of
writing.
(abs (- start end))
bytes
read from port. The first byte read is stored at index string.
substring-read!
returns the number of bytes read.
port may be omitted, in which case it defaults to the value returned
by current-input-port
.
substring-write
writes (abs (- start end))
bytes to
output-port port. The first byte written is index start of string. substring-write
returns the number of bytes written.
port may be omitted, in which case it defaults to the value returned
by current-output-port
.
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
The multi-byte sequences produced and used by numeric conversion
routines are always big-endian. Endianness can be changed during
reading and writing bytes using read-bytes
and
write-bytes
See section read-bytes.
The sign of the length argument to bytes/integer conversion procedures determines the signedness of the number.
Converts the first (abs n)
bytes of big-endian bytes array
to an integer. If n is negative then the integer coded by the
bytes are treated as two's-complement (can be negative).
(bytes->integer (bytes 0 0 0 15) -4) => 15 (bytes->integer (bytes 0 0 0 15) 4) => 15 (bytes->integer (bytes 255 255 255 255) -4) => -1 (bytes->integer (bytes 255 255 255 255) 4) => 4294967295 (bytes->integer (bytes 128 0 0 0) -4) => -2147483648 (bytes->integer (bytes 128 0 0 0) 4) => 2147483648 |
Converts the integer n to a byte-array of (abs n)
bytes. If n and len are both negative, then the bytes in the
returned array are coded two's-complement.
(bytes->list (integer->bytes 15 -4)) => (0 0 0 15) (bytes->list (integer->bytes 15 4)) => (0 0 0 15) (bytes->list (integer->bytes -1 -4)) => (255 255 255 255) (bytes->list (integer->bytes 4294967295 4)) => (255 255 255 255) (bytes->list (integer->bytes -2147483648 -4)) => (128 0 0 0) (bytes->list (integer->bytes 2147483648 4)) => (128 0 0 0) |
bytes must be a 4-element byte-array. bytes->ieee-float
calculates and returns the
value of bytes interpreted as a big-endian IEEE 4-byte (32-bit) number.
(bytes->ieee-float (bytes #x40 0 0 0)) => 2.0 (bytes->ieee-float (bytes #x40 #xd0 0 0)) => 6.5 (bytes->ieee-float (bytes #xc0 #xd0 0 0)) => -6.5 (bytes->ieee-float (bytes 0 #x80 0 0)) => 11.754943508222875e-39 (bytes->ieee-float (bytes 0 #x40 0 0)) => 5.877471754111437e-39 (bytes->ieee-float (bytes 0 0 0 1)) => 1.401298464324817e-45 (bytes->ieee-float (bytes #xff #x80 0 0)) => -1/0 (bytes->ieee-float (bytes #x7f #x80 0 0)) => 1/0 (bytes->ieee-float (bytes #x7f #x80 0 1)) => 0/0 |
bytes must be a 8-element byte-array. bytes->ieee-double
calculates and returns the
value of bytes interpreted as a big-endian IEEE 8-byte (64-bit) number.
(bytes->ieee-double (bytes 0 0 0 0 0 0 0 0)) => 0.0 (bytes->ieee-double (bytes #x40 0 0 0 0 0 0 0)) => 2 (bytes->ieee-double (bytes #x40 #x1A 0 0 0 0 0 0)) => 6.5 (bytes->ieee-double (bytes #xC0 #x1A 0 0 0 0 0 0)) => -6.5 (bytes->ieee-double (bytes 0 8 0 0 0 0 0 0)) => 11.125369292536006e-309 (bytes->ieee-double (bytes 0 4 0 0 0 0 0 0)) => 5.562684646268003e-309 (bytes->ieee-double (bytes 0 0 0 0 0 0 0 1)) => 4.0e-324 (bytes->ieee-double (bytes #xFF #xF0 0 0 0 0 0 0)) => -1/0 (bytes->ieee-double (bytes #x7F #xF0 0 0 0 0 0 0)) => 1/0 (bytes->ieee-double (bytes #x7F #xF8 0 0 0 0 0 0)) => 0/0 |
Returns a 4-element byte-array encoding the IEEE single-precision floating-point of x.
(bytes->list (ieee-float->bytes 2.0)) => (64 0 0 0) (bytes->list (ieee-float->bytes 6.5)) => (64 208 0 0) (bytes->list (ieee-float->bytes -6.5)) => (192 208 0 0) (bytes->list (ieee-float->bytes 11.754943508222875e-39)) => ( 0 128 0 0) (bytes->list (ieee-float->bytes 5.877471754111438e-39)) => ( 0 64 0 0) (bytes->list (ieee-float->bytes 1.401298464324817e-45)) => ( 0 0 0 1) (bytes->list (ieee-float->bytes -1/0)) => (255 128 0 0) (bytes->list (ieee-float->bytes 1/0)) => (127 128 0 0) (bytes->list (ieee-float->bytes 0/0)) => (127 128 0 1) |
Returns a 8-element byte-array encoding the IEEE double-precision floating-point of x.
(bytes->list (ieee-double->bytes 2.0)) => (64 0 0 0 0 0 0 0) (bytes->list (ieee-double->bytes 6.5)) => (64 26 0 0 0 0 0 0) (bytes->list (ieee-double->bytes -6.5)) => (192 26 0 0 0 0 0 0) (bytes->list (ieee-double->bytes 11.125369292536006e-309)) => ( 0 8 0 0 0 0 0 0) (bytes->list (ieee-double->bytes 5.562684646268003e-309)) => ( 0 4 0 0 0 0 0 0) (bytes->list (ieee-double->bytes 4.0e-324)) => ( 0 0 0 0 0 0 0 1) (bytes->list (ieee-double->bytes -1/0)) => (255 240 0 0 0 0 0 0) (bytes->list (ieee-double->bytes 1/0)) => (127 240 0 0 0 0 0 0) (bytes->list (ieee-double->bytes 0/0)) => (127 248 0 0 0 0 0 0) |
The string<?
ordering of big-endian byte-array
representations of fixed and IEEE floating-point numbers agrees with
the numerical ordering only when those numbers are non-negative.
Straighforward modification of these formats can extend the byte-collating order to work for their entire ranges. This agreement enables the full range of numbers as keys in indexed-sequential-access-method databases.
Modifies sign bit of byte-vector so that string<?
ordering of
two's-complement byte-vectors matches numerical order. integer-byte-collate!
returns
byte-vector and is its own functional inverse.
Returns copy of byte-vector with sign bit modified so that string<?
ordering of two's-complement byte-vectors matches numerical order.
integer-byte-collate
is its own functional inverse.
Modifies byte-vector so that string<?
ordering of IEEE floating-point
byte-vectors matches numerical order. ieee-byte-collate!
returns byte-vector.
Given byte-vector modified by IEEE-byte-collate!
, reverses the byte-vector
modifications.
Returns copy of byte-vector encoded so that string<?
ordering of IEEE
floating-point byte-vectors matches numerical order.
Given byte-vector returned by IEEE-byte-collate
, reverses the byte-vector
modifications.
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
http://www.mathworks.com/access/helpdesk/help/pdf_doc/matlab/matfile_format.pdf
This package reads MAT-File Format version 4 (MATLAB) binary data files. MAT-files written from big-endian or little-endian computers having IEEE format numbers are currently supported. Support for files written from VAX or Cray machines could also be added.
The numeric and text matrix types handled; support for sparse matrices awaits a sample file.
matfile:read
procedure reads matrices from the
file and returns a list of the results; a list of the name string and
array for each matrix.
matfile:load
procedure reads matrices from the
file and defines the string-ci->symbol
for each matrix to its
corresponding array. matfile:load
returns a list of the symbols defined.
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
The string path must name a portable bitmap graphics file.
pnm:type-dimensions
returns a list of 4 items:
The current set of file-type symbols is:
Reads the portable bitmap graphics file named by path into array. array must be the correct size and type for path. array is returned.
pnm:image-file->array
creates and returns an array with the
portable bitmap graphics file named by path read into it.
Writes the contents of array to a type image file named path. The file will have pixel values between 0 and maxval, which must be compatible with type. For `pbm' files, maxval must be `1'. comments are included in the file header.
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Routines for managing collections. Collections are aggregate data structures supporting iteration over their elements, similar to the Dylan(TM) language, but with a different interface. They have elements indexed by corresponding keys, although the keys may be implicit (as with lists).
New types of collections may be defined as YASOS objects (see section 3.8 Yasos). They must support the following operations:
(collection? self)
(always returns #t
);
(size self)
returns the number of elements in the collection;
(print self port)
is a specialized print operation
for the collection which prints a suitable representation on the given
port or returns it as a string if port is #t
;
(gen-elts self)
returns a thunk which on successive
invocations yields elements of self in order or gives an error if
it is invoked more than (size self)
times;
(gen-keys self)
is like gen-elts
, but yields the
collection's keys in order.
They might support specialized for-each-key
and
for-each-elt
operations.
#t
to collection?
.
do-elts
is used when only side-effects of proc are of
interest and its return value is unspecified. map-elts
returns a
collection (actually a vector) of the results of the applications of
proc.
Example:
(map-elts + (list 1 2 3) (vector 1 2 3)) => #(2 4 6) |
map-elts
and do-elts
, but each
iteration is over the collections' keys rather than their
elements.
Example:
(map-keys + (list 1 2 3) (vector 1 2 3)) => #(0 2 4) |
do-keys
and do-elts
but only for a single
collection; they are potentially more efficient.
reduce-init
(see section 7.2.1.3 Lists as sequences) to collections which will shadow the
list-based version if (require 'collect)
follows
(require 'common-list-functions)
(see section 7.2.1 Common List Functions).
Examples:
(reduce + 0 (vector 1 2 3)) => 6 (reduce union '() '((a b c) (b c d) (d a))) => (c b d a). |
some
(see section 7.2.1.3 Lists as sequences) to collections.
Example:
(any? odd? (list 2 3 4 5)) => #t |
every
(see section 7.2.1.3 Lists as sequences) to collections.
Example:
(every? collection? '((1 2) #(1 2))) => #t |
#t
iff there are no elements in collection.
(empty? collection) == (zero? (size collection))
(setter list-ref)
doesn't work properly for element 0 of a
list.
Here is a sample collection: simple-table
which is also a
table
.
(define-predicate TABLE?) (define-operation (LOOKUP table key failure-object)) (define-operation (ASSOCIATE! table key value)) ;; returns key (define-operation (REMOVE! table key)) ;; returns value (define (MAKE-SIMPLE-TABLE) (let ( (table (list)) ) (object ;; table behaviors ((TABLE? self) #t) ((SIZE self) (size table)) ((PRINT self port) (format port "#<SIMPLE-TABLE>")) ((LOOKUP self key failure-object) (cond ((assq key table) => cdr) (else failure-object) )) ((ASSOCIATE! self key value) (cond ((assq key table) => (lambda (bucket) (set-cdr! bucket value) key)) (else (set! table (cons (cons key value) table)) key) )) ((REMOVE! self key);; returns old value (cond ((null? table) (slib:error "TABLE:REMOVE! Key not found: " key)) ((eq? key (caar table)) (let ( (value (cdar table)) ) (set! table (cdr table)) value) ) (else (let loop ( (last table) (this (cdr table)) ) (cond ((null? this) (slib:error "TABLE:REMOVE! Key not found: " key)) ((eq? key (caar this)) (let ( (value (cdar this)) ) (set-cdr! last (cdr this)) value) ) (else (loop (cdr last) (cdr this))) ) ) ) )) ;; collection behaviors ((COLLECTION? self) #t) ((GEN-KEYS self) (collect:list-gen-elts (map car table))) ((GEN-ELTS self) (collect:list-gen-elts (map cdr table))) ((FOR-EACH-KEY self proc) (for-each (lambda (bucket) (proc (car bucket))) table) ) ((FOR-EACH-ELT self proc) (for-each (lambda (bucket) (proc (cdr bucket))) table) ) ) ) ) |
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
dynamic?
satisfies any of the other standard type
predicates.
The dynamic-bind
macro is not implemented.
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Returns a hash function (like hashq
, hashv
, or
hash
) corresponding to the equality predicate pred.
pred should be eq?
, eqv?
, equal?
, =
,
char=?
, char-ci=?
, string=?
, or
string-ci=?
.
Returns a vector of k empty (association) lists.
eq?
, eqv?
, equal?
, =
,
char=?
, char-ci=?
, string=?
, or
string-ci=?
.
Returns a hash association function of 2 arguments, key and
hashtab, corresponding to pred. The returned function
returns a key-value pair whose key is pred-equal to its first
argument or #f
if no key in hashtab is pred-equal to
the first argument.
Returns a procedure of 2 arguments, hashtab and key, which
returns the value associated with key in hashtab or
#f
if key does not appear in hashtab.
Returns a procedure of 3 arguments, hashtab, key, and value, which modifies hashtab so that key and value associated. Any previous value associated with key will be lost.
Returns a procedure of 2 arguments, hashtab and key, which modifies hashtab so that the association whose key is key is removed.
Returns a new hash table formed by mapping proc over the keys and values of hash-table. proc must be a function of 2 arguments which returns the new value part.
Applies proc to each pair of keys and values of hash-table. proc must be a function of 2 arguments. The returned value is unspecified.
hash-rehasher
accepts a hash table predicate and returns a function of two
arguments hashtab and new-k which is specialized for
that predicate.
This function is used for nondestrutively resizing a hash table. hashtab should be an existing hash-table using pred, new-k is the size of a new hash table to be returned. The new hash table will have all of the associations of the old hash table.
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
This is the Macroless Object System written by Wade Humeniuk (whumeniu@datap.ca). Conceptual Tributes: 3.8 Yasos, MacScheme's %object, CLOS, Lack of R4RS macros.
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
eq?
) of methods
(procedures). Methods can be added (make-method!
), deleted
(unmake-method!
) and retrieved (get-method
). Objects may
inherit methods from other objects. The object binds to the environment
it was created in, allowing closures to be used to hide private
procedures and data.
eq?
) object's method.
This allows scheme function style to be used for objects. The calling
scheme for using a generic method is (generic-method object param1
param2 ...)
.
#t
.
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
get-method
.
unmake-method!
will restore the object's previous association with the
generic-method. method must be a procedure.
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
<inverter>::(<number> <description>) |
<inverter>::value => <number>::value <inverter>::set-value! => <number>::set-value! <inverter>::describe => <description>::describe <inverter>::help <inverter>::invert <inverter>::inverter? |
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
<number>::() |
<number>::<x> |
<number>::value <number>::set-value! |
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
This algorithm for priority queues is due to Introduction to Algorithms by T. Cormen, C. Leiserson, R. Rivest. 1989 MIT Press.
Returns a binary heap suitable which can be used for priority queue operations.
Returns the number of elements in heap.
Inserts item into heap. item can be inserted multiple times. The value returned is unspecified.
Returns the item which is larger than all others according to the
pred<? argument to make-heap
. If there are no items in
heap, an error is signaled.
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
A queue is a list where elements can be added to both the front and rear, and removed from the front (i.e., they are what are often called dequeues). A queue may also be used like a stack.
Returns a new, empty queue.
Returns #t
if obj is a queue.
Returns #t
if the queue q is empty.
Adds datum to the front of queue q.
Adds datum to the rear of queue q.
queue-pop!
is used to suggest that the queue is
being used like a stack.
Removes and returns (the list) of all contents of queue q.
Returns the datum at the front of the queue q.
Returns the datum at the rear of the queue q.
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
The Record package provides a facility for user to define their own record data types.
make-record-type
that created the type represented by rtd;
if the field-names argument is provided, it is an error if it
contains any duplicates or any symbols not in the default list.
make-record-type
that created the type represented by rtd.
make-record-type
that created the type represented by
rtd.
In May of 1996, as a product of discussion on the rrrs-authors
mailing list, I rewrote `record.scm' to portably implement type
disjointness for record data types.
As long as an implementation's procedures are opaque and the
record
code is loaded before other programs, this will give
disjoint record types which are unforgeable and incorruptible by R4RS
procedures.
As a consequence, the procedures record?
,
record-type-descriptor
, record-type-name
.and
record-type-field-names
are no longer supported.
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
7.2.1 Common List Functions | 'common-list-functions | |
7.2.2 Tree operations | 'tree | |
7.2.3 Chapter Ordering | 'chapter-order | |
7.2.4 Sorting | 'sort | |
7.2.5 Topological Sort | Keep your socks on. | |
7.2.6 Hashing | 'hash | |
7.2.7 Space-Filling Curves | 'hilbert and 'sierpinski | |
7.2.8 Soundex | Dimension Reduction of Last Names | |
7.2.9 String Search | Also Search from a Port. | |
7.2.10 Sequence Comparison | 'diff and longest-common-subsequence |
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
(require 'common-list-functions)
The procedures below follow the Common LISP equivalents apart from optional arguments in some cases.
7.2.1.1 List construction | ||
7.2.1.2 Lists as sets | ||
7.2.1.3 Lists as sequences | ||
7.2.1.4 Destructive list operations | ||
7.2.1.5 Non-List functions |
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
make-list
creates and returns a list of k elements. If
init is included, all elements in the list are initialized to
init.
Example:
(make-list 3) => (#<unspecified> #<unspecified> #<unspecified>) (make-list 5 'foo) => (foo foo foo foo foo) |
list
except that the cdr of the last pair is the last
argument unless there is only one argument, when the result is just that
argument. Sometimes called cons*
. E.g.:
(list* 1) => 1 (list* 1 2 3) => (1 2 . 3) (list* 1 2 '(3 4)) => (1 2 3 4) (list* args '()) == (list args) |
copy-list
makes a copy of lst using new pairs and returns
it. Only the top level of the list is copied, i.e., pairs forming
elements of the copied list remain eq?
to the corresponding
elements of the original; the copy is, however, not eq?
to the
original, but is equal?
to it.
Example:
(copy-list '(foo foo foo)) => (foo foo foo) (define q '(foo bar baz bang)) (define p q) (eq? p q) => #t (define r (copy-list q)) (eq? q r) => #f (equal? q r) => #t (define bar '(bar)) (eq? bar (car (copy-list (list bar 'foo)))) => #t |
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
eqv?
is used to test for membership by procedures which treat
lists as sets.
adjoin
returns the adjoint of the element e and the list
l. That is, if e is in l, adjoin
returns
l, otherwise, it returns (cons e l)
.
Example:
(adjoin 'baz '(bar baz bang)) => (bar baz bang) (adjoin 'foo '(bar baz bang)) => (foo bar baz bang) |
union
returns a list of all elements that are in l1 or
l2. Duplicates between l1 and l2 are culled.
Duplicates within l1 or within l2 may or may not be
removed.
Example:
(union '(1 2 3 4) '(5 6 7 8)) => (1 2 3 4 5 6 7 8) (union '(0 1 2 3 4) '(3 4 5 6)) => (5 6 0 1 2 3 4) |
intersection
returns a list of all elements that are in both
l1 and l2.
Example:
(intersection '(1 2 3 4) '(3 4 5 6)) => (3 4) (intersection '(1 2 3 4) '(5 6 7 8)) => () |
set-difference
returns a list of all elements that are in
l1 but not in l2.
Example:
(set-difference '(1 2 3 4) '(3 4 5 6)) => (1 2) (set-difference '(1 2 3 4) '(1 2 3 4 5 6)) => () |
#t
if every element of list1 is eqv?
an
element of list2; otherwise returns #f
.
Example:
(subset? '(1 2 3 4) '(3 4 5 6)) => #f (subset? '(1 2 3 4) '(6 5 4 3 2 1 0)) => #t |
member-if
returns the list headed by the first element of
lst to satisfy (pred element)
.
Member-if
returns #f
if pred returns #f
for
every element in lst.
Example:
(member-if vector? '(a 2 b 4)) => #f (member-if number? '(a 2 b 4)) => (2 b 4) |
some
i.e., lst plus any optional arguments.
pred is applied to successive elements of the list arguments in
order. some
returns #t
as soon as one of these
applications returns #t
, and is #f
if none returns
#t
. All the lists should have the same length.
Example:
(some odd? '(1 2 3 4)) => #t (some odd? '(2 4 6 8)) => #f (some > '(1 3) '(2 4)) => #f |
every
is analogous to some
except it returns #t
if
every application of pred is #t
and #f
otherwise.
Example:
(every even? '(1 2 3 4)) => #f (every even? '(2 4 6 8)) => #t (every > '(2 3) '(1 4)) => #f |
notany
is analogous to some
but returns #t
if no
application of pred returns #t
or #f
as soon as any
one does.
notevery
is analogous to some
but returns #t
as soon
as an application of pred returns #f
, and #f
otherwise.
Example:
(notevery even? '(1 2 3 4)) => #t (notevery even? '(2 4 6 8)) => #f |
list-of??
returns a predicate which returns true if its argument
is a list of length between low-bound and high-bound
(inclusive); every element of which satisfies predicate.
list-of??
returns a predicate which returns true if its argument is a list of
length greater than (- bound)
; every element of which
satisfies predicate. Otherwise, list-of??
returns a
predicate which returns true if its argument is a list of length less
than or equal to bound; every element of which satisfies
predicate.
find-if
searches for the first element in lst such
that (pred element)
returns #t
. If it finds
any such element in lst, element is returned.
Otherwise, #f
is returned.
Example:
(find-if number? '(foo 1 bar 2)) => 1 (find-if number? '(foo bar baz bang)) => #f (find-if symbol? '(1 2 foo bar)) => foo |
remove
removes all occurrences of elt from lst using
eqv?
to test for equality and returns everything that's left.
N.B.: other implementations (Chez, Scheme->C and T, at least) use
equal?
as the equality test.
Example:
(remove 1 '(1 2 1 3 1 4 1 5)) => (2 3 4 5) (remove 'foo '(bar baz bang)) => (bar baz bang) |
remove-if
removes all elements from lst where
(pred element)
is #t
and returns everything
that's left.
Example:
(remove-if number? '(1 2 3 4)) => () (remove-if even? '(1 2 3 4 5 6 7 8)) => (1 3 5 7) |
remove-if-not
removes all elements from lst for which
(pred element)
is #f
and returns everything that's
left.
Example:
(remove-if-not number? '(foo bar baz)) => () (remove-if-not odd? '(1 2 3 4 5 6 7 8)) => (1 3 5 7) |
#t
if 2 members of lst are equal?
, #f
otherwise.
Example:
(has-duplicates? '(1 2 3 4)) => #f (has-duplicates? '(2 4 3 4)) => #t |
The procedure remove-duplicates
uses member
(rather than
memv
).
equal?
.
Example:
(remove-duplicates '(1 2 3 4)) => (1 2 3 4) (remove-duplicates '(2 4 3 4)) => (2 4 3) |
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
position
returns the 0-based position of obj in lst,
or #f
if obj does not occur in lst.
Example:
(position 'foo '(foo bar baz bang)) => 0 (position 'baz '(foo bar baz bang)) => 2 (position 'oops '(foo bar baz bang)) => #f |
reduce
combines all the elements of a sequence using a binary
operation (the combination is left-associative). For example, using
+
, one can add up all the elements. reduce
allows you to
apply a function which accepts only two arguments to more than 2
objects. Functional programmers usually refer to this as foldl.
collect:reduce
(see section 7.1.9 Collections) provides a version of
collect
generalized to collections.
Example:
(reduce + '(1 2 3 4)) => 10 (define (bad-sum . l) (reduce + l)) (bad-sum 1 2 3 4) == (reduce + (1 2 3 4)) == (+ (+ (+ 1 2) 3) 4) => 10 (bad-sum) == (reduce + ()) => () (reduce string-append '("hello" "cruel" "world")) == (string-append (string-append "hello" "cruel") "world") => "hellocruelworld" (reduce anything '()) => () (reduce anything '(x)) => x |
What follows is a rather non-standard implementation of reverse
in terms of reduce
and a combinator elsewhere called
C.
;;; Contributed by Jussi Piitulainen (jpiitula @ ling.helsinki.fi) (define commute (lambda (f) (lambda (x y) (f y x)))) (define reverse (lambda (args) (reduce-init (commute cons) '() args))) |
reduce-init
is the same as reduce, except that it implicitly
inserts init at the start of the list. reduce-init
is
preferred if you want to handle the null list, the one-element, and
lists with two or more elements consistently. It is common to use the
operator's idempotent as the initializer. Functional programmers
usually call this foldl.
Example:
(define (sum . l) (reduce-init + 0 l)) (sum 1 2 3 4) == (reduce-init + 0 (1 2 3 4)) == (+ (+ (+ (+ 0 1) 2) 3) 4) => 10 (sum) == (reduce-init + 0 '()) => 0 (reduce-init string-append "@" '("hello" "cruel" "world")) == (string-append (string-append (string-append "@" "hello") "cruel") "world") => "@hellocruelworld" |
Given a differentiation of 2 arguments, diff
, the following will
differentiate by any number of variables.
(define (diff* exp . vars) (reduce-init diff exp vars)) |
Example:
;;; Real-world example: Insertion sort using reduce-init. (define (insert l item) (if (null? l) (list item) (if (< (car l) item) (cons (car l) (insert (cdr l) item)) (cons item l)))) (define (insertion-sort l) (reduce-init insert '() l)) (insertion-sort '(3 1 4 1 5) == (reduce-init insert () (3 1 4 1 5)) == (insert (insert (insert (insert (insert () 3) 1) 4) 1) 5) == (insert (insert (insert (insert (3)) 1) 4) 1) 5) == (insert (insert (insert (1 3) 4) 1) 5) == (insert (insert (1 3 4) 1) 5) == (insert (1 1 3 4) 5) => (1 1 3 4 5) |
last
returns the last n elements of lst. n
must be a non-negative integer.
Example:
(last '(foo bar baz bang) 2) => (baz bang) (last '(1 2 3) 0) => 0 |
butlast
returns all but the last n elements of
lst.
Example:
(butlast '(a b c d) 3) => (a) (butlast '(a b c d) 4) => () |
last
and butlast
split a list into two parts when given
identical arugments.
(last '(a b c d e) 2) => (d e) (butlast '(a b c d e) 2) => (a b c) |
nthcdr
takes n cdr
s of lst and returns the
result. Thus (nthcdr 3 lst)
== (cdddr
lst)
Example:
(nthcdr 2 '(a b c d)) => (c d) (nthcdr 0 '(a b c d)) => (a b c d) |
butnthcdr
returns all but the nthcdr n elements of
lst.
Example:
(butnthcdr 3 '(a b c d)) => (a b c) (butnthcdr 4 '(a b c d)) => (a b c d) |
nthcdr
and butnthcdr
split a list into two parts when
given identical arugments.
(nthcdr 2 '(a b c d e)) => (c d e) (butnthcdr 2 '(a b c d e)) => (a b) |
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
These procedures may mutate the list they operate on, but any such mutation is undefined.
nconc
destructively concatenates its arguments. (Compare this
with append
, which copies arguments rather than destroying them.)
Sometimes called append!
(see section 7.4.4 Rev2 Procedures).
Example: You want to find the subsets of a set. Here's the obvious way:
(define (subsets set) (if (null? set) '(()) (append (map (lambda (sub) (cons (car set) sub)) (subsets (cdr set))) (subsets (cdr set))))) |
append
with nconc
, since you don't have any
need for all the intermediate results.
Example:
(define x '(a b c)) (define y '(d e f)) (nconc x y) => (a b c d e f) x => (a b c d e f) |
nconc
is the same as append!
in `sc2.scm'.
nreverse
reverses the order of elements in lst by mutating
cdr
s of the list. Sometimes called reverse!
.
Example:
(define foo '(a b c)) (nreverse foo) => (c b a) foo => (a) |
Some people have been confused about how to use nreverse
,
thinking that it doesn't return a value. It needs to be pointed out
that
(set! lst (nreverse lst)) |
(nreverse lst) |
remove
remove-if
, and
remove-if-not
.
Example:
(define lst (list 'foo 'bar 'baz 'bang)) (delete 'foo lst) => (bar baz bang) lst => (foo bar baz bang) (define lst (list 1 2 3 4 5 6 7 8 9)) (delete-if odd? lst) => (2 4 6 8) lst => (1 2 4 6 8) |
Some people have been confused about how to use delete
,
delete-if
, and delete-if
, thinking that they don't return
a value. It needs to be pointed out that
(set! lst (delete el lst)) |
(delete el lst) |
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
and?
checks to see if all its arguments are true. If they are,
and?
returns #t
, otherwise, #f
. (In contrast to
and
, this is a function, so all arguments are always evaluated
and in an unspecified order.)
Example:
(and? 1 2 3) => #t (and #f 1 2) => #f |
or?
checks to see if any of its arguments are true. If any is
true, or?
returns #t
, and #f
otherwise. (To
or
as and?
is to and
.)
Example:
(or? 1 2 #f) => #t (or? #f #f #f) => #f |
#t
if object is not a pair and #f
if it is
pair. (Called atom
in Common LISP.)
(atom? 1) => #t (atom? '(1 2)) => #f (atom? #(1 2)) ; dubious! => #t |
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
These are operations that treat lists a representations of trees.
subst
makes a copy of tree, substituting new for
every subtree or leaf of tree which is equal?
to old
and returns a modified tree. The original tree is unchanged, but
may share parts with the result.
substq
and substv
are similar, but test against old
using eq?
and eqv?
respectively. If subst
is
called with a fourth argument, equ? is the equality predicate.
Examples:
(substq 'tempest 'hurricane '(shakespeare wrote (the hurricane))) => (shakespeare wrote (the tempest)) (substq 'foo '() '(shakespeare wrote (twelfth night))) => (shakespeare wrote (twelfth night . foo) . foo) (subst '(a . cons) '(old . pair) '((old . spice) ((old . shoes) old . pair) (old . pair))) => ((old . spice) ((old . shoes) a . cons) (a . cons)) |
Makes a copy of the nested list structure tree using new pairs and
returns it. All levels are copied, so that none of the pairs in the
tree are eq?
to the original ones -- only the leaves are.
Example:
(define bar '(bar)) (copy-tree (list bar 'foo)) => ((bar) foo) (eq? bar (car (copy-tree (list bar 'foo)))) => #f |
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
The `chap:' functions deal with strings which are ordered like chapter numbers (or letters) in a book. Each section of the string consists of consecutive numeric or consecutive aphabetic characters of like case.
Returns #t if the first non-matching run of alphabetic upper-case or
the first non-matching run of alphabetic lower-case or the first
non-matching run of numeric characters of string1 is
string<?
than the corresponding non-matching run of
characters of string2.
(chap:string<? "a.9" "a.10") => #t (chap:string<? "4c" "4aa") => #t (chap:string<? "Revised^{3.99}" "Revised^{4}") => #t |
Implement the corresponding chapter-order predicates.
Returns the next string in the chapter order. If string
has no alphabetic or numeric characters,
(string-append string "0")
is returnd. The argument to
chap:next-string will always be chap:string<?
than the result.
(chap:next-string "a.9") => "a.10" (chap:next-string "4c") => "4d" (chap:next-string "4z") => "4aa" (chap:next-string "Revised^{4}") => "Revised^{5}" |
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Many Scheme systems provide some kind of sorting functions. They do not, however, always provide the same sorting functions, and those that I have had the opportunity to test provided inefficient ones (a common blunder is to use quicksort which does not perform well).
Because sort
and sort!
are not in the standard, there is
very little agreement about what these functions look like. For
example, Dybvig says that Chez Scheme provides
(merge predicate list1 list2) (merge! predicate list1 list2) (sort predicate list) (sort! predicate list) |
(sort list predicate) |
(sort! list/vector predicate?) |
(sort list/vector predicate?) (sort! list/vector predicate?) |
Here is a comprehensive catalogue of the variations I have found.
sort
and sort!
may be provided.
sort
may be provided without sort!
.
sort!
may be provided without sort
.
<
.
<=
.
(sort predicate? sequence)
.
(sort sequence predicate?)
.
(sort sequence &optional (predicate? <))
.
All of this variation really does not help anybody. A nice simple merge sort is both stable and fast (quite a lot faster than quick sort).
I am providing this source code with no restrictions at all on its use (but please retain D.H.D.Warren's credit for the original idea). You may have to rename some of these functions in order to use them in a system which already provides incompatible or inferior sorts. For each of the functions, only the top-level define needs to be edited to do that.
I could have given these functions names which would not clash with any Scheme that I know of, but I would like to encourage implementors to converge on a single interface, and this may serve as a hint. The argument order for all functions has been chosen to be as close to Common LISP as made sense, in order to avoid NIH-itis.
Each of the five functions has a required last parameter which is
a comparison function. A comparison function f
is a function of
2 arguments which acts like <
. For example,
(not (f x x)) (and (f x y) (f y z)) == (f x z) |
The standard functions <
, >
, char<?
, char>?
,
char-ci<?
, char-ci>?
, string<?
, string>?
,
string-ci<?
, and string-ci>?
are suitable for use as
comparison functions. Think of (less? x y)
as saying when
x
must not precede y
.
#t
when the sequence argument is in non-decreasing order
according to less? (that is, there is no adjacent pair ... x
y ...
for which (less? y x)
).
Returns #f
when the sequence contains at least one out-of-order
pair. It is an error if the sequence is not a list, vector, or
string.
sort
is our sort!
(well,
in fact Common LISP's stable-sort
is our sort!
, merge sort
is fast as well as stable!) so adapting CL code to Scheme takes a
bit of work anyway. I did, however, appeal to CL to determine the
order of the arguments.
The code of merge
and merge!
could have been quite a bit
simpler, but they have been coded to reduce the amount of work done per
iteration. (For example, we only have one null?
test per
iteration.)
(sorted? (sort sequence less?) less?)
. The original
sequence is not altered in any way. The new sequence shares its
elements with the old one; no elements are copied.
Some people have been confused about how to use sort!
, thinking
that it doesn't return a value. It needs to be pointed out that
(set! slist (sort! slist <)) |
(sort! slist <) |
Note that these functions do not accept a CL-style `:key' argument. A simple device for obtaining the same expressiveness is to define
(define (keyed less? key) (lambda (x y) (less? (key x) (key y)))) |
(sort a-sequence #'my-less :key #'my-key) |
(sort! a-sequence (keyed my-less? my-key)) |
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
(require 'topological-sort)
or (require 'tsort)
The algorithm is inspired by Cormen, Leiserson and Rivest (1990) Introduction to Algorithms, chapter 23.
eq?
, eqv?
, equal?
, =
,
char=?
, char-ci=?
, string=?
, or string-ci=?
.
Sort the directed acyclic graph dag so that for every edge from vertex u to v, u will come before v in the resulting list of vertices.
Time complexity: O (|V| + |E|)
Example (from Cormen):
Prof. Bumstead topologically sorts his clothing when getting dressed. The first argument totsort
describes which garments he needs to put on before others. (For example, Prof Bumstead needs to put on his shirt before he puts on his tie or his belt.)tsort
gives the correct order of dressing:
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
These hashing functions are for use in quickly classifying objects. Hash tables use these functions.
For hashq
, (eq? obj1 obj2)
implies (= (hashq obj1 k)
(hashq obj2))
.
For hashv
, (eqv? obj1 obj2)
implies (= (hashv obj1 k)
(hashv obj2))
.
For hash
, (equal? obj1 obj2)
implies (= (hash obj1 k)
(hash obj2))
.
hash
, hashv
, and hashq
return in time bounded by a
constant. Notice that items having the same hash
implies the
items have the same hashv
implies the items have the same
hashq
.
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
7.2.7.1 Peano-Hilbert Space-Filling Curve | ||
7.2.7.2 Sierpinski Curve |
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
The Peano-Hilbert Space-Filling Curve is a one-to-one mapping between a unit line segment and an n-dimensional unit cube.
The integer procedures map the non-negative integers to an arbitrarily large n-dimensional cube with its corner at the origin and all coordinates are non-negative.
For any exact nonnegative integers scalar and rank,
(= scalar (hilbert-coordinates->integer (integer->hilbert-coordinates scalar rank))) => #t |
Returns a list of rank integer coordinates corresponding to exact
non-negative integer scalar. The lists returned by integer->hilbert-coordinates
for scalar arguments
0 and 1 will differ in the first element.
Returns an exact non-negative integer corresponding to coords, a list of non-negative integer coordinates.
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
max-coordinate is the maximum coordinate (a positive integer) of a population of points. The returned procedures is a function that takes the x and y coordinates of a point, (non-negative integers) and returns an integer corresponding to the relative position of that point along a Sierpinski curve. (You can think of this as computing a (pseudo-) inverse of the Sierpinski spacefilling curve.)
Example use: Make an indexer (hash-function) for integer points lying in square of integer grid points [0,99]x[0,99]:
(define space-key (make-sierpinski-indexer 100)) |
(space-key 24 78) => 9206 (space-key 23 80) => 9172 |
Note that locations (24, 78) and (23, 80) are near in index and therefore, because the Sierpinski spacefilling curve is continuous, we know they must also be near in the plane. Nearness in the plane does not, however, necessarily correspond to nearness in index, although it tends to be so.
Example applications:
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Soundex was a classic algorithm used for manual filing of personal records before the advent of computers. It performs adequately for English names but has trouble with other languages.
See Knuth, Vol. 3 Sorting and searching, pp 391--2
To manage unusual inputs, soundex
omits all non-alphabetic
characters. Consequently, in this implementation:
(soundex <string of blanks>) => "" (soundex "") => "" |
Examples from Knuth:
(map soundex '("Euler" "Gauss" "Hilbert" "Knuth" "Lloyd" "Lukasiewicz")) => ("E460" "G200" "H416" "K530" "L300" "L222") (map soundex '("Ellery" "Ghosh" "Heilbronn" "Kant" "Ladd" "Lissajous")) => ("E460" "G200" "H416" "K530" "L300" "L222") |
Some cases in which the algorithm fails (Knuth):
(map soundex '("Rogers" "Rodgers")) => ("R262" "R326") (map soundex '("Sinclair" "St. Clair")) => ("S524" "S324") (map soundex '("Tchebysheff" "Chebyshev")) => ("T212" "C121") |
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
#f
if the string does not contain a
character char.
#f
if the string does not contain a
character char.
substring?
returns the index of the first
character of the first substring of string that is equal to
pattern; or #f
if string does not contain
pattern.
(substring? "rat" "pirate") => 2 (substring? "rat" "outrage") => #f (substring? "" any-string) => 0 |
When the str is found, find-string-from-port?
returns the
number of characters it has read from the port, and the port is set to
read the first char after that (that is, after the str) The
function returns #f
when the str isn't found.
find-string-from-port?
reads the port strictly
sequentially, and does not perform any buffering. So
find-string-from-port?
can be used even if the in-port is
open to a pipe or other communication channel.
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
diff:edit-length
implements the algorithm:
S. Wu, E. Myers, U. Manber, and W. Miller, "An O(NP) Sequence Comparison Algorithm," Information Processing Letters 35, 6 (1990), 317-323. http://www.cs.arizona.edu/people/gene/vita.html |
The values returned by diff:edit-length
can be used to gauge
the degree of match between two sequences.
Surprisingly, "An O(NP) Sequence Comparison Algorithm" does not derive the edit sequence; only the sequence length. Developing this linear-space sub-quadratic-time algorithm for computing the edit sequence required hundreds of hours of work. I have submitted a paper describing the algorithm to the Journal of Computational Biology.
If the items being sequenced are text lines, then the computed edit-list is equivalent to the output of the diff utility program. If the items being sequenced are words, then it is like the lesser known spiff program.
The non-negative integer p-lim, if provided, is maximum number of
deletions of the shorter sequence to allow. diff:longest-common-subsequence
will return #f
if more deletions would be necessary.
diff:longest-common-subsequence
returns a one-dimensional array of length (quotient (- (+
len1 len2) (diff:edit-length array1 array2)) 2)
holding the longest sequence
common to both arrays.
The non-negative integer p-lim, if provided, is maximum number of
deletions of the shorter sequence to allow. diff:edits
will return #f
if more deletions would be necessary.
diff:edits
returns a vector of length (diff:edit-length array1 array2)
composed
of a shortest sequence of edits transformaing array1 to array2.
Each edit is an integer:
(array-ref array1 (+ -1 j))
into the sequence.
(array-ref array2 (- -1 k))
from the sequence.
The non-negative integer p-lim, if provided, is maximum number of
deletions of the shorter sequence to allow. diff:edit-length
will return #f
if more deletions would be necessary.
diff:edit-length
returns the length of the shortest sequence of edits transformaing
array1 to array2.
(diff:longest-common-subsequence "fghiejcklm" "fgehijkpqrlm" eqv?) => "fghijklm" (diff:edit-length "fghiejcklm" "fgehijkpqrlm" eqv?) => 6 (diff:edits "fghiejcklm" "fgehijkpqrlm" eqv?) => #As32(3 -5 -7 8 9 10) ; e c h p q r |
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Anything that doesn't fall neatly into any of the other categories winds up here.
7.3.1 Type Coercion | 'coerce | |
7.3.2 String-Case | 'string-case | |
7.3.3 String Ports | 'string-port | |
7.3.4 Line I/O | 'line-i/o | |
7.3.5 Multi-Processing | 'process | |
7.3.6 Metric Units | Portable manifest types for numeric values. |
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
(require 'coerce)
Returns a symbol name for the type of obj.
Converts and returns obj of type char
, number
,
string
, symbol
, list
, or vector
to
result-type (which must be one of these symbols).
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
read
.
StudlyCapsExpand
returns a
copy of str where delimiter is inserted between each
lower-case character immediately followed by an upper-case character;
and between two upper-case characters immediately followed by a
lower-case character.
(StudlyCapsExpand "aX" " ") => "a X" (StudlyCapsExpand "aX" "..") => "a..X" (StudlyCapsExpand "AX") => "AX" (StudlyCapsExpand "Ax") => "Ax" (StudlyCapsExpand "AXLE") => "AXLE" (StudlyCapsExpand "aAXACz") => "a-AXA-Cz" (StudlyCapsExpand "AaXACz") => "Aa-XA-Cz" (StudlyCapsExpand "AAaXACz") => "A-Aa-XA-Cz" (StudlyCapsExpand "AAaXAC") => "A-Aa-XAC" |
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
current-input-port
.
#f
is returned. The port argument may be
omitted, in which case it defaults to the value returned by
current-input-port
.
current-input-port
.
system->line
calls system
with command as argument,
redirecting stdout to file tmp. system->line
returns a string containing the
first line of output from tmp.
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
This module implements asynchronous (non-polled) time-sliced
multi-processing in the SCM Scheme implementation using procedures
alarm
and alarm-interrupt
.
Until this is ported to another implementation, consider it an example
of writing schedulers in Scheme.
process:queue
. The
value returned is unspecified. The argument to proc should be
ignored. If proc returns, the process is killed.
process:queue
and runs the next
process from process:queue
. The value returned is
unspecified.
process:queue
. If there are no more processes on
process:queue
, (slib:exit)
is called (see section 2.4 System).
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
http://swissnet.ai.mit.edu/~jaffer/MIXF.html
Metric Interchange Format is a character string encoding for numerical values and units which:
In the expression for the value of a quantity, the unit symbol is placed after the numerical value. A dot (PERIOD, `.') is placed between the numerical value and the unit symbol.
Within a compound unit, each of the base and derived symbols can optionally have an attached SI prefix.
Unit symbols formed from other unit symbols by multiplication are indicated by means of a dot (PERIOD, `.') placed between them.
Unit symbols formed from other unit symbols by division are indicated by means of a SOLIDUS (`/') or negative exponents. The SOLIDUS must not be repeated in the same compound unit unless contained within a parenthesized subexpression.
The grouping formed by a prefix symbol attached to a unit symbol constitutes a new inseparable symbol (forming a multiple or submultiple of the unit concerned) which can be raised to a positive or negative power and which can be combined with other unit symbols to form compound unit symbols.
The grouping formed by surrounding compound unit symbols with parentheses (`(' and `)') constitutes a new inseparable symbol which can be raised to a positive or negative power and which can be combined with other unit symbols to form compound unit symbols.
Compound prefix symbols, that is, prefix symbols formed by the juxtaposition of two or more prefix symbols, are not permitted.
Prefix symbols are not used with the time-related unit symbols min (minute), h (hour), d (day). No prefix symbol may be used with dB (decibel). Only submultiple prefix symbols may be used with the unit symbols L (liter), Np (neper), o (degree), oC (degree Celsius), rad (radian), and sr (steradian). Submultiple prefix symbols may not be used with the unit symbols t (metric ton), r (revolution), or Bd (baud).
A unit exponent follows the unit, separated by a CIRCUMFLEX (`^'). Exponents may be positive or negative. Fractional exponents must be parenthesized.
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Factor Name Symbol | Factor Name Symbol ====== ==== ====== | ====== ==== ====== 1e24 yotta Y | 1e-1 deci d 1e21 zetta Z | 1e-2 centi c 1e18 exa E | 1e-3 milli m 1e15 peta P | 1e-6 micro u 1e12 tera T | 1e-9 nano n 1e9 giga G | 1e-12 pico p 1e6 mega M | 1e-15 femto f 1e3 kilo k | 1e-18 atto a 1e2 hecto h | 1e-21 zepto z 1e1 deka da | 1e-24 yocto y |
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
These binary prefixes are valid only with the units B (byte) and bit. However, decimal prefixes can also be used with bit; and decimal multiple (not submultiple) prefixes can also be used with B (byte).
Factor (power-of-2) Name Symbol ====== ============ ==== ====== 1.152921504606846976e18 (2^60) exbi Ei 1.125899906842624e15 (2^50) pebi Pi 1.099511627776e12 (2^40) tebi Ti 1.073741824e9 (2^30) gibi Gi 1.048576e6 (2^20) mebi Mi 1.024e3 (2^10) kibi Ki |
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Type of Quantity Name Symbol Equivalent ================ ==== ====== ========== time second s time minute min = 60.s time hour h = 60.min time day d = 24.h frequency hertz Hz s^-1 signaling rate baud Bd s^-1 length meter m volume liter L dm^3 plane angle radian rad solid angle steradian sr rad^2 plane angle revolution * r = 6.283185307179586.rad plane angle degree * o = 2.777777777777778e-3.r information capacity bit bit information capacity byte, octet B = 8.bit mass gram g mass ton t Mg mass unified atomic mass unit u = 1.66053873e-27.kg amount of substance mole mol catalytic activity katal kat mol/s thermodynamic temperature kelvin K centigrade temperature degree Celsius oC luminous intensity candela cd luminous flux lumen lm cd.sr illuminance lux lx lm/m^2 force newton N m.kg.s^-2 pressure, stress pascal Pa N/m^2 energy, work, heat joule J N.m energy electronvolt eV = 1.602176462e-19.J power, radiant flux watt W J/s logarithm of power ratio neper Np logarithm of power ratio decibel * dB = 0.1151293.Np electric current ampere A electric charge coulomb C s.A electric potential, EMF volt V W/A capacitance farad F C/V electric resistance ohm Ohm V/A electric conductance siemens S A/V magnetic flux weber Wb V.s magnetic flux density tesla T Wb/m^2 inductance henry H Wb/A radionuclide activity becquerel Bq s^-1 absorbed dose energy gray Gy m^2.s^-2 dose equivalent sievert Sv m^2.s^-2 |
* The formulas are:
si:conversion-factor
will be such that multiplying a
numerical value expressed in from-units by the returned conversion
factor yields the numerical value expressed in to-units.
Otherwise, si:conversion-factor
returns:
(si:conversion-factor "km/s" "m/s" ) => 0.001 (si:conversion-factor "N" "m/s" ) => 0 (si:conversion-factor "moC" "oC" ) => 1000 (si:conversion-factor "mK" "oC" ) => 0 (si:conversion-factor "rad" "o" ) => 0.0174533 (si:conversion-factor "K" "o" ) => 0 (si:conversion-factor "K" "K" ) => 1 (si:conversion-factor "oK" "oK" ) => -3 (si:conversion-factor "" "s/s" ) => 1 (si:conversion-factor "km/h" "mph" ) => -2 |
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
7.4.1 RnRS | Revised Reports on Scheme | |
7.4.2 With-File | 'with-file | |
7.4.3 Transcripts | 'transcript | |
7.4.4 Rev2 Procedures | 'rev2-procedures | |
7.4.5 Rev4 Optional Procedures | 'rev4-optional-procedures | |
7.4.6 Multi-argument / and - | 'multiarg/and- | |
7.4.7 Multi-argument Apply | 'multiarg-apply | |
7.4.8 Rationalize | 'rationalize | |
7.4.9 Promises | 'delay | |
7.4.10 Dynamic-Wind | 'dynamic-wind | |
7.4.11 Eval | 'eval | |
7.4.12 Values | 'values | |
7.4.13 SRFI | 'http://srfi.schemers.org/srfi-0/srfi-0.html |
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
The r2rs
, r3rs
, r4rs
, and r5rs
features
attempt to provide procedures and macros to bring a Scheme
implementation to the desired version of Scheme.
rev3-procedures
and rev2-procedures
.
rev3-procedures
.
Note: SLIB already mandates the r3rs
procedures which can
be portably implemented in r4rs
implementations.
rev4-optional-procedures
.
values
, macro
, and eval
.
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
read-char
, read
, write-char
,
write
, display
, and newline
.
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
The procedures below were specified in the Revised^2 Report on
Scheme. N.B.: The symbols 1+
and -1+
are not
R4RS syntax. Scheme->C, for instance, chokes on this
module.
0 <= start1 <= end1 <= (string-length string1) 0 <= start2 <= end1 - start1 + start2 <= (string-length string2) |
substring-move-left!
and substring-move-right!
store
characters of string1 beginning with index start1
(inclusive) and ending with index end1 (exclusive) into
string2 beginning with index start2 (inclusive).
substring-move-left!
stores characters in time order of
increasing indices. substring-move-right!
stores characters in
time order of increasing indeces.
(= 0 (string-length str))
nconc
.
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
(require 'rev4-optional-procedures)
For the specification of these optional procedures, See section `Standard procedures' in Revised(4) Scheme.
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
For the specification of these optional forms, See section `Numerical operations' in Revised(4) Scheme.
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
For the specification of this optional form, See section `Control features' in Revised(4) Scheme.
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Computes the correct result for exact arguments (provided the implementation supports exact rational numbers of unlimited precision); and produces a reasonable answer for inexact arguments when inexact arithmetic is implemented using floating-point.
Rationalize
has limited use in implementations lacking exact
(non-integer) rational numbers. The following procedures return a list
of the numerator and denominator.
find-ratio
returns the list of the simplest
numerator and denominator whose quotient differs from x by no more
than e.
(find-ratio 3/97 .0001) => (3 97) (find-ratio 3/97 .001) => (1 32) |
find-ratio-between
returns the list of the simplest
numerator and denominator between x and y.
(find-ratio-between 2/7 3/5) => (1 2) (find-ratio-between -3/5 -2/7) => (-1 2) |
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
(require 'delay)
provides force
and delay
:
(delay expression)
to
(make-promise (lambda () expression)) |
(see section `Control features' in Revised(4) Scheme).
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
This facility is a generalization of Common LISP unwind-protect
,
designed to take into account the fact that continuations produced by
call-with-current-continuation
may be reentered.
dynamic-wind
calls thunk1, thunk2, and then
thunk3. The value returned by thunk2 is returned as the
result of dynamic-wind
. thunk3 is also called just before
control leaves the dynamic context of thunk2 by calling a
continuation created outside that context. Furthermore, thunk1 is
called before reentering the dynamic context of thunk2 by calling
a continuation created inside that context. (Control is inside the
context of thunk2 if thunk2 is on the current return stack).
Warning: There is no provision for dealing with errors or
interrupts. If an error or interrupt occurs while using
dynamic-wind
, the dynamic environment will be that in effect at
the time of the error or interrupt.
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Evaluates expression in the specified environment and returns its
value. Expression must be a valid Scheme expression represented
as data, and environment-specifier must be a value returned by one
of the three procedures described below. Implementations may extend
eval
to allow non-expression programs (definitions) as the first
argument and to allow other values as environments, with the restriction
that eval
is not allowed to create new bindings in the
environments associated with null-environment
or
scheme-report-environment
.
(eval '(* 7 3) (scheme-report-environment 5)) => 21 (let ((f (eval '(lambda (f x) (f x x)) (null-environment)))) (f + 10)) => 20 |
Version must be an exact non-negative integer n
corresponding to a version of one of the Revised^n Reports on
Scheme. Scheme-report-environment
returns a specifier for an
environment that contains the set of bindings specified in the
corresponding report that the implementation supports.
Null-environment
returns a specifier for an environment that
contains only the (syntactic) bindings for all the syntactic keywords
defined in the given version of the report.
Not all versions may be available in all implementations at all times. However, an implementation that conforms to version n of the Revised^n Reports on Scheme must accept version n. An error is signalled if the specified version is not available.
The effect of assigning (through the use of eval
) a variable
bound in a scheme-report-environment
(for example car
) is
unspecified. Thus the environments specified by
scheme-report-environment
may be immutable.
This optional procedure returns a specifier for the environment that contains implementation-defined bindings, typically a superset of those listed in the report. The intent is that this procedure will return the environment in which the implementation would evaluate expressions dynamically typed by the user.
Here are some more eval
examples:
(require 'eval) => #<unspecified> (define car 'volvo) => #<unspecified> car => volvo (eval 'car (interaction-environment)) => volvo (eval 'car (scheme-report-environment 5)) => #<primitive-procedure car> (eval '(eval 'car (interaction-environment)) (scheme-report-environment 5)) => volvo (eval '(eval '(set! car 'buick) (interaction-environment)) (scheme-report-environment 5)) => #<unspecified> car => buick (eval 'car (scheme-report-environment 5)) => #<primitive-procedure car> (eval '(eval 'car (interaction-environment)) (scheme-report-environment 5)) => buick |
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
values
takes any number of arguments, and passes (returns) them
to its continuation.
call-with-values
calls thunk with a
continuation that, when passed some values, calls proc with those
values as arguments.
Except for continuations created by the call-with-values
procedure, all continuations take exactly one value, as now; the effect
of passing no value or more than one value to continuations that were
not created by the call-with-values
procedure is
unspecified.
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Implements Scheme Request For Implementation (SRFI) as described at http://srfi.schemers.org/
The Copyright terms of each SRFI states:
"However, this document itself may not be modified in any way, ..."
Therefore, the specification of SRFI constructs must not be quoted without including the complete SRFI document containing discussion and a sample implementation program.
Syntax: Each <clause> should be of the form
(<feature> <expression1> ...) |
where <feature> is a boolean expression composed of symbols and `and', `or', and `not' of boolean expressions. The last <clause> may be an "else clause," which has the form
(else <expression1> <expression2> ...). |
The first clause whose feature expression is satisfied is expanded. If no feature expression is satisfied and there is no else clause, an error is signaled.
SLIB cond-expand
is an extension of SRFI-0,
http://srfi.schemers.org/srfi-0/srfi-0.html.
7.4.13.1 SRFI-1 | list-processing | |
7.4.13.2 SRFI-2 | guarded LET* special form | |
7.4.13.3 SRFI-8 | Binding to multiple values | |
7.4.13.4 SRFI-9 | Defining Record Types |
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Implements the SRFI-1 list-processing library as described at http://srfi.schemers.org/srfi-1/srfi-1.html
(define (xcons d a) (cons a d))
.
(proc
i)
for 0 <= i < len.
Returns a circular list of obj1, obj2, ....
(car (last-pair lst))
member
returns the first sublist of list whose car is obj, where the sublists
of list are the non-empty lists returned by (list-tail list k)
for k less than the length of list. If obj does not occur in list,
then #f (not the empty list) is returned. The procedure pred is
used for testing equality. If pred is not provided, `equal?' is
used.
alist (for "association list") must be a list of pairs. These procedures find the first pair in alist whose car field is obj, and returns that pair. If no pair in alist has obj as its car, then #f (not the empty list) is returned. The procedure pred is used for testing equality. If pred is not provided, `equal?' is used.
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
http://srfi.schemers.org/srfi-9/srfi-9.html
Where
<field-spec> == (<field-tag> <accessor-name>) == (<field-tag> <accessor-name> <modifier-name>) |
define-record-type
is a syntax wrapper for the SLIB
record
module.
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
7.5.1 Repl | Macros at top-level | |
7.5.2 Quick Print | Loop-safe Output | |
7.5.3 Debug | To err is human ... | |
7.5.4 Breakpoints | Pause execution | |
7.5.5 Tracing | 'trace |
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Here is a read-eval-print-loop which, given an eval, evaluates forms.
read
s, repl:eval
s and write
s expressions from
(current-input-port)
to (current-output-port)
until an
end-of-file is encountered. load
, slib:eval
,
slib:error
, and repl:quit
dynamically bound during
repl:top-level
.
repl:top-level
.
The repl:
procedures establish, as much as is possible to do
portably, a top level environment supporting macros.
repl:top-level
uses dynamic-wind
to catch error conditions
and interrupts. If your implementation supports this you are all set.
Otherwise, if there is some way your implementation can catch error
conditions and interrupts, then have them call slib:error
. It
will display its arguments and reenter repl:top-level
.
slib:error
dynamically bound by repl:top-level
.
To have your top level loop always use macros, add any interrupt catching lines and the following lines to your Scheme init file:
(require 'macro) (require 'repl) (repl:top-level macro:eval) |
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
When displaying error messages and warnings, it is paramount that the output generated for circular lists and large data structures be limited. This section supplies a procedure to do this. It could be much improved.
Notice that the neccessity for truncating output eliminates Common-Lisp's 4.2 Format (version 3.0) from consideration; even when variables*print-level*
and*print-level*
are set, huge strings and bit-vectors are not limited.
qp
writes its arguments, separated by spaces, to
(current-output-port)
. qp
compresses printing by
substituting `...' for substructure it does not have sufficient
room to print. qpn
is like qp
but outputs a newline
before returning. qpr
is like qpn
except that it returns
its last argument.
qp
should use. If *qp-width* is #f, then all items will be
write
n. If *qp-width* is 0, then all items except
procedures will be write
n; procedures will be indicated by
`#[proc]'.
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Requiring debug
automatically requires trace
and
break
.
An application with its own datatypes may want to substitute its own
printer for qp
. This example shows how to do this:
(define qpn (lambda args) ...) (provide 'qp) (require 'debug) |
define
d at top-level in
`file' ....
define
d at top-level in
`file' ....
define
d at top-level in
`file' ....
define
d at
top-level in `file' ....
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
break
or
abort
, a message will appear when you (require 'break)
or
(require 'debug)
telling you to type (init-debug)
. This
is in order to establish a top-level continuation. Typing
(init-debug)
at top level sets up a continuation for
break
.
breakpoint
is called before calling proc1 ....
These are procedures for breaking. If defmacros are not natively supported by your implementation, these might be more convenient to use.
(set! symbol (breakf symbol)) |
(set! symbol (breakf symbol 'symbol)) |
(define symbol (breakf function)) |
(define symbol (breakf function 'symbol)) |
(set! symbol (unbreakf symbol)) |
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
This feature provides three ways to monitor procedure invocations:
These are procedures for tracing. If defmacros are not natively supported by your implementation, these might be more convenient to use.
(set! symbol (tracef symbol)) |
(set! symbol (tracef symbol 'symbol)) |
(define symbol (tracef function)) |
(define symbol (tracef function 'symbol)) |
(set! symbol (untracef symbol)) |
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
If (provided? 'getenv)
:
#f
is returned.
If (provided? 'system)
:
7.6.1 Directories | ||
7.6.2 Transactions | ||
7.6.3 CVS |
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
current-directory
returns a string containing the absolute file
name representing the current working directory. If this string
cannot be obtained, #f is returned.
If current-directory
cannot be supported by the platform, then #f is returned.
Creates a sub-directory name of the current-directory. If
successful, make-directory
returns #t; otherwise #f.
proc must be a procedure taking one argument. `Directory-For-Each' applies proc to the (string) name of each file in directory. The dynamic order in which proc is applied to the filenames is unspecified. The value returned by `directory-for-each' is unspecified.
(filename:match?? match)
would return a non-false value
(see section `Filenames' in SLIB).
(require 'directory) (directory-for-each print "." "[A-Z]*.scm") -| "Bev2slib.scm" "Template.scm" |
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
If system
is provided by the Scheme implementation, the
transact package provides functions for file-locking and
file-replacement transactions.
Unix file-locking is focussed on write permissions for segments of a existing file. While this might be employed for (binary) database access, it is not used for everyday contention (between users) for text files.
Microsoft has several file-locking protocols. Their model denies write access to a file if any reader has it open. This is too restrictive. Write access is denied even when the reader has reached end-of-file. And tracking read access (which is much more common than write access) causes havoc when remote hosts crash or disconnect.
It is bizarre that the concept of multi-user contention for modifying files has not been adequately addressed by either of the large operating system development efforts. There is further irony that both camps support contention detection and resolution only through weak conventions of some their document editing programs.
The file-lock procedures implement a transaction method for file replacement compatible with the methods used by the GNU emacs text editor on Unix systems and the Microsoft Word editor.
Both protocols employ what I term a certificate containing the user, hostname, time, and (on Unix) process-id. Intent to replace file is indicated by adding to file's directory a certificate object whose name is derived from file.
The Microsoft Word certificate is contained in a 162 byte file named for the visited file with a `~$' prefix. Emacs/Unix creates a symbolic link to a certificate named for the visited file prefixed with `.#'. Because Unix systems can import Microsoft file systems, these routines maintain and check both Emacs and Word certificates.
Returns the string `user@hostname' associated with the lock owner of file path if locked; and #f otherwise.
path must be a string naming the file to be locked. If supplied, email
must be a string formatted as `user@hostname'. If
absent, email defaults to the value returned by user-email-address
.
If path is already locked, then file-lock!
returns `#f'. If path is
unlocked, then file-lock!
returns the certificate string associated with the
new lock for file path.
path must be a string naming the file to be unlocked. certificate must be the
string returned by file-lock!
for path.
If path is locked with certificate, then file-unlock!
removes the locks and returns
`#t'. Otherwise, file-unlock!
leaves the file system unaltered and returns
`#f'.
path must be a string. backup-style must be a symbol. Depending on backup-style, emacs:backup-name
returns:
path must be a string naming an existing file. backup-style is one of the symbols none, simple, numbered, existing, orig, bak or #f; with meanings described above; or a string naming the location of a backup file. backup-style defaults to #f. If supplied, certificate is the certificate with which path is locked.
proc must be a procedure taking two string arguments:
If path is locked by other than certificate, or if certificate is supplied and path is not
locked, then transact-file-replacement
returns #f. If certificate is not supplied, then, transact-file-replacement
creates
temporary (Emacs and Word) locks for path during the transaction. The
lock status of path will be restored before transact-file-replacement
returns.
transact-file-replacement
calls proc with path (which should not be modified) and a temporary
file path to be written.
If proc returns any value other than #t, then the file named by path
is not altered and transact-file-replacement
returns #f.
Otherwise, emacs:backup-name
is called with path and backup-style. If it
returns a string, then path is renamed to it.
Finally, the temporary file is renamed path.
transact-file-replacement
returns #t if path was successfully replaced; and #f otherwise.
user-email-address
returns a string of the form `username@hostname'. If
this e-mail address cannot be obtained, #f is returned.
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
(getenv "CVSROOT")
if Root doesn't exist.
Writes new-root to file CVS/Root of directory/ and all its subdirectories.
Signals an error if CVS/Repository or CVS/Root files in directory/ or any subdirectory do not match.
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Several Scheme packages have been written using SLIB. There are several reasons why a package might not be included in the SLIB distribution:
Once an optional package is installed (and an entry added to
*catalog*
, the require
mechanism allows it to be called up
and used as easily as any other SLIB package. Some optional packages
(for which *catalog*
already has entries) available from SLIB
sites are:
<A HREF="http://swissnet.ai.mit.edu/ftpdir/scm/slib-psd1-3.tar.gz"> http://swissnet.ai.mit.edu/ftpdir/scm/slib-psd1-3.tar.gz </A>
swissnet.ai.mit.edu:/pub/scm/slib-psd1-3.tar.gz
ftp.maths.tcd.ie:pub/bosullvn/jacal/slib-psd1-3.tar.gz
ftp.cs.indiana.edu:/pub/scheme-repository/utl/slib-psd1-3.tar.gz
With PSD, you can run a Scheme program in an Emacs buffer, set breakpoints, single step evaluation and access and modify the program's variables. It works by instrumenting the original source code, so it should run with any R4RS compliant Scheme. It has been tested with SCM, Elk 1.5, and the sci interpreter in the Scheme->C system, but should work with other Schemes with a minimal amount of porting, if at all. Includes documentation and user's manual. Written by Pertti Kellom\"aki, pk @ cs.tut.fi. The Lisp Pointers article describing PSD (Lisp Pointers VI(1):15-23, January-March 1993) is available as <A HREF="http://www.cs.tut.fi/staff/pk/scheme/psd/article/article.html"> http://www.cs.tut.fi/staff/pk/scheme/psd/article/article.html </A>
[ << ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |