get-bytevector-n, read-bytevector - read data from a binary port

---

LIBRARY

(import (rnrs))                     ;R6RS
(import (rnrs io ports))            ;R6RS
(import (scheme base))              ;R7RS

SYNOPSIS

;; R6RS
(get-bytevector-n binary-input-port k)

;; R7RS
(read-bytevector k)
(read-bytevector k binary-input-port)

DESCRIPTION

R7RS

The default value for binary-input-port is the object returned by current-input-port(3scm).

Multiple end-of-file conditions

The port may return an end-of-file object and then still keep producing data if another read is attempted. Files do not normally work this way, but it is possible for other types of ports to do so, such as terminals. R6RS explicitly mentions this situation while R7RS does not.

RETURN VALUES

R6RS

There is a single, unique end-of-file object.

EXAMPLES

(call-with-port (open-file-input-port "/dev/zero")
  (lambda (p)
    (get-bytevector-n p 4)))
        => #vu8(0 0 0 0)

ERRORS

&assertion (R6RS)

The wrong number of arguments was passed or an argument was outside its domain. In particular, count must be an exact, nonnegative integer object, and binary-input-port must be an open binary input port.

&i/o-read (R6RS)

There was an I/O error during the read operation.

&i/o-port (R6RS)

This condition specifies the port object related to an &i/o-read condition.

R7RS

The assertions described above are errors. Implementations may signal an error, extend the procedure's domain of definition to include such arguments, or fail catastrophically.

SEE ALSO

STANDARDS

HISTORY

AUTHORS

BUGS