sunterlib/scsh/bytio
Anthony Carrico 02699e0409 Add script to change install lib version from 1.2.0 to 1.3.0, and make that change. THIS IS UNTESTED. I have no idea if packages need further changes for 1.3.0. 2012-01-16 03:06:42 +00:00
..
AUTHORS improved blurb 2005-08-16 23:11:13 +00:00
BLURB improved blurb 2005-08-16 23:11:13 +00:00
NEWS improved blurb 2005-08-16 23:11:13 +00:00
README version numbers, explicit project dependencies 2004-03-14 19:39:49 +00:00
packages.scm Moved package and interface definition to packages.scm. Generate load scripts. 2004-03-14 22:59:57 +00:00
pkg-def.scm Add script to change install lib version from 1.2.0 to 1.3.0, and make that change. THIS IS UNTESTED. I have no idea if packages need further changes for 1.3.0. 2012-01-16 03:06:42 +00:00
rw-bytes.scm fixed (read-bytes/partial! _ _ n n) 2003-04-22 17:13:43 +00:00

README

sunterlib/scsh/bytio -- Byte I/O

Package-Dependencies

BYTIO's structure BYTIO depends on structures from these other sunterlib
projects:
             krims
             sequences

                                  *

Procedures exported by BYTIO

(read-byte [inport]) --> n in [0:256)
(peek-byte [inport]) --> n in [0:256)
(write-byte n [outport]) --> unspec

Synopsis:  Obvious byte analogues to Scheme's character readers and
writers.  [ Presently these are only wrappers around the char procs.
That means, the system reads octets, cooks them into characters, that
we revert to raw numeric meat, i.e. small integers in [0:256). ]

                                *

(read-bytes n [fd/port]) --> bytes or #f
(read-bytes/partial n [fd/port]) --> bytes pr #f

(read-bytes! bytes [fd/port start end]) --> nread or #f
(read-bytes!/partial bytes [fd/port start end]) --> nread or #f

(write-bytes bytes [fd/port start end]) --> unspec

Synopsis:  Obvious byte analogues of the corresponding string procs
documented in the scsh manual, with byte-vectors BYTES replacing
strings.  (String arguments BYTES work, too.)

Notes:
* Byte-vector constructors etc. are in structure BYTE-VECTORS.
* The present implementation avoids allocating temp buffers by not
  always reading very much ...
* The procedures aren't tested well, yet.

                              0Oo