2d4f3e2ac9
The layer is now redundant, since everything left in "pkgs" is in the "racket-pkgs" category.
30 lines
1.1 KiB
Racket
30 lines
1.1 KiB
Racket
#lang scribble/doc
|
|
@(require scribble/manual scribble/eval "guide-utils.rkt")
|
|
|
|
@title[#:tag "ports"]{Input and Output Ports}
|
|
|
|
A @deftech{port} encapsulates an I/O stream, normally for just one
|
|
direction. An @deftech{input port} reads from a stream, and an
|
|
@deftech{output port} writes to a string.
|
|
|
|
For many procedures that accept a port argument, the argument is
|
|
optional, and it defaults to either the @defterm{current input port}
|
|
or @defterm{current output port}. For @exec{mzscheme}, the current
|
|
ports are initialized to the process's stdin and stdout. The
|
|
@racket[current-input-port] and @racket[current-output-port]
|
|
procedures, when called with no arguments, return the current output
|
|
and input port, respectively.
|
|
|
|
@examples[
|
|
(display "hello world\n")
|
|
(display "hello world\n" (current-output-port))
|
|
]
|
|
|
|
Ports are created by various procedures that specific to the different
|
|
kinds of streams. For example, @racket[open-input-file] creates an
|
|
input port for reading from a file. Procedures like
|
|
@racket[with-input-from-file] both create a port and install it as the
|
|
current port while calling a given body procedure.
|
|
|
|
See @secref["io"] for information about using ports.
|