Warning: This is the manual of the legacy Guile 2.2 series. You may want to read the manual of the current stable series instead.

Next: , Previous: , Up: POSIX   [Contents][Index]


7.2.2 Ports and File Descriptors

Conventions generally follow those of scsh, The Scheme shell (scsh).

Each open file port has an associated operating system file descriptor. File descriptors are generally not useful in Scheme programs; however they may be needed when interfacing with foreign code and the Unix environment.

A file descriptor can be extracted from a port and a new port can be created from a file descriptor. However a file descriptor is just an integer and the garbage collector doesn’t recognize it as a reference to the port. If all other references to the port were dropped, then it’s likely that the garbage collector would free the port, with the side-effect of closing the file descriptor prematurely.

To assist the programmer in avoiding this problem, each port has an associated revealed count which can be used to keep track of how many times the underlying file descriptor has been stored in other places. If a port’s revealed count is greater than zero, the file descriptor will not be closed when the port is garbage collected. A programmer can therefore ensure that the revealed count will be greater than zero if the file descriptor is needed elsewhere.

For the simple case where a file descriptor is “imported” once to become a port, it does not matter if the file descriptor is closed when the port is garbage collected. There is no need to maintain a revealed count. Likewise when “exporting” a file descriptor to the external environment, setting the revealed count is not required provided the port is kept open (i.e., is pointed to by a live Scheme binding) while the file descriptor is in use.

To correspond with traditional Unix behaviour, three file descriptors (0, 1, and 2) are automatically imported when a program starts up and assigned to the initial values of the current/standard input, output, and error ports, respectively. The revealed count for each is initially set to one, so that dropping references to one of these ports will not result in its garbage collection: it could be retrieved with fdopen or fdes->ports.

Guile’s ports can be buffered. This means that writing a byte to a file port goes to the internal buffer first, and only when the buffer is full (or the user invokes force-output on the port) is the data actually written to the file descriptor. Likewise on input, bytes are read in from the file descriptor in blocks and placed in a buffer. Reading a character via read-char first goes to the buffer, filling it as needed. Usually read buffering is more or less transparent, but write buffering can sometimes cause writes to be delayed unexpectedly, if you forget to call force-output. See Buffering, for more on how to control port buffers.

Note however that some procedures (e.g., recv!) will accept ports as arguments, but will actually operate directly on the file descriptor underlying the port. Any port buffering is ignored, including the buffer which implements peek-char and unread-char.

Scheme Procedure: port-revealed port
C Function: scm_port_revealed (port)

Return the revealed count for port.

Scheme Procedure: set-port-revealed! port rcount
C Function: scm_set_port_revealed_x (port, rcount)

Sets the revealed count for a port to rcount. The return value is unspecified.

Scheme Procedure: fileno port
C Function: scm_fileno (port)

Return the integer file descriptor underlying port. Does not change its revealed count.

Scheme Procedure: port->fdes port

Returns the integer file descriptor underlying port. As a side effect the revealed count of port is incremented.

Scheme Procedure: fdopen fdes modes
C Function: scm_fdopen (fdes, modes)

Return a new port based on the file descriptor fdes. Modes are given by the string modes. The revealed count of the port is initialized to zero. The modes string is the same as that accepted by open-file (see open-file).

Scheme Procedure: fdes->ports fdes
C Function: scm_fdes_to_ports (fdes)

Return a list of existing ports which have fdes as an underlying file descriptor, without changing their revealed counts.

Scheme Procedure: fdes->inport fdes

Returns an existing input port which has fdes as its underlying file descriptor, if one exists, and increments its revealed count. Otherwise, returns a new input port with a revealed count of 1.

Scheme Procedure: fdes->outport fdes

Returns an existing output port which has fdes as its underlying file descriptor, if one exists, and increments its revealed count. Otherwise, returns a new output port with a revealed count of 1.

Scheme Procedure: primitive-move->fdes port fdes
C Function: scm_primitive_move_to_fdes (port, fdes)

Moves the underlying file descriptor for port to the integer value fdes without changing the revealed count of port. Any other ports already using this descriptor will be automatically shifted to new descriptors and their revealed counts reset to zero. The return value is #f if the file descriptor already had the required value or #t if it was moved.

Scheme Procedure: move->fdes port fdes

Moves the underlying file descriptor for port to the integer value fdes and sets its revealed count to one. Any other ports already using this descriptor will be automatically shifted to new descriptors and their revealed counts reset to zero. The return value is unspecified.

Scheme Procedure: release-port-handle port

Decrements the revealed count for a port.

Scheme Procedure: fsync port_or_fd
C Function: scm_fsync (port_or_fd)

Copies any unwritten data for the specified output file descriptor to disk. If port_or_fd is a port, its buffer is flushed before the underlying file descriptor is fsync’d. The return value is unspecified.

Scheme Procedure: open path flags [mode]
C Function: scm_open (path, flags, mode)

Open the file named by path for reading and/or writing. flags is an integer specifying how the file should be opened. mode is an integer specifying the permission bits of the file, if it needs to be created, before the umask (see Processes) is applied. The default is 666 (Unix itself has no default).

flags can be constructed by combining variables using logior. Basic flags are:

Variable: O_RDONLY

Open the file read-only.

Variable: O_WRONLY

Open the file write-only.

Variable: O_RDWR

Open the file read/write.

Variable: O_APPEND

Append to the file instead of truncating.

Variable: O_CREAT

Create the file if it does not already exist.

See File Status Flags in The GNU C Library Reference Manual, for additional flags.

Scheme Procedure: open-fdes path flags [mode]
C Function: scm_open_fdes (path, flags, mode)

Similar to open but return a file descriptor instead of a port.

Scheme Procedure: close fd_or_port
C Function: scm_close (fd_or_port)

Similar to close-port (see close-port), but also works on file descriptors. A side effect of closing a file descriptor is that any ports using that file descriptor are moved to a different file descriptor and have their revealed counts set to zero.

Scheme Procedure: close-fdes fd
C Function: scm_close_fdes (fd)

A simple wrapper for the close system call. Close file descriptor fd, which must be an integer. Unlike close, the file descriptor will be closed even if a port is using it. The return value is unspecified.

Scheme Procedure: pipe
C Function: scm_pipe ()

Return a newly created pipe: a pair of ports which are linked together on the local machine. The CAR is the input port and the CDR is the output port. Data written (and flushed) to the output port can be read from the input port. Pipes are commonly used for communication with a newly forked child process. The need to flush the output port can be avoided by making it unbuffered using setvbuf (see Buffering).

Variable: PIPE_BUF

A write of up to PIPE_BUF many bytes to a pipe is atomic, meaning when done it goes into the pipe instantaneously and as a contiguous block (see Atomicity of Pipe I/O in The GNU C Library Reference Manual).

Note that the output port is likely to block if too much data has been written but not yet read from the input port. Typically the capacity is PIPE_BUF bytes.

The next group of procedures perform a dup2 system call, if newfd (an integer) is supplied, otherwise a dup. The file descriptor to be duplicated can be supplied as an integer or contained in a port. The type of value returned varies depending on which procedure is used.

All procedures also have the side effect when performing dup2 that any ports using newfd are moved to a different file descriptor and have their revealed counts set to zero.

Scheme Procedure: dup->fdes fd_or_port [fd]
C Function: scm_dup_to_fdes (fd_or_port, fd)

Return a new integer file descriptor referring to the open file designated by fd_or_port, which must be either an open file port or a file descriptor.

Scheme Procedure: dup->inport port/fd [newfd]

Returns a new input port using the new file descriptor.

Scheme Procedure: dup->outport port/fd [newfd]

Returns a new output port using the new file descriptor.

Scheme Procedure: dup port/fd [newfd]

Returns a new port if port/fd is a port, with the same mode as the supplied port, otherwise returns an integer file descriptor.

Scheme Procedure: dup->port port/fd mode [newfd]

Returns a new port using the new file descriptor. mode supplies a mode string for the port (see open-file).

Scheme Procedure: duplicate-port port modes

Returns a new port which is opened on a duplicate of the file descriptor underlying port, with mode string modes as for open-file. The two ports will share a file position and file status flags.

Unexpected behaviour can result if both ports are subsequently used and the original and/or duplicate ports are buffered. The mode string can include 0 to obtain an unbuffered duplicate port.

This procedure is equivalent to (dup->port port modes).

Scheme Procedure: redirect-port old_port new_port
C Function: scm_redirect_port (old_port, new_port)

This procedure takes two ports and duplicates the underlying file descriptor from old_port into new_port. The current file descriptor in new_port will be closed. After the redirection the two ports will share a file position and file status flags.

The return value is unspecified.

Unexpected behaviour can result if both ports are subsequently used and the original and/or duplicate ports are buffered.

This procedure does not have any side effects on other ports or revealed counts.

Scheme Procedure: dup2 oldfd newfd
C Function: scm_dup2 (oldfd, newfd)

A simple wrapper for the dup2 system call. Copies the file descriptor oldfd to descriptor number newfd, replacing the previous meaning of newfd. Both oldfd and newfd must be integers. Unlike for dup->fdes or primitive-move->fdes, no attempt is made to move away ports which are using newfd. The return value is unspecified.

Scheme Procedure: port-for-each proc
C Function: scm_port_for_each (SCM proc)
C Function: scm_c_port_for_each (void (*proc)(void *, SCM), void *data)

Apply proc to each port in the Guile port table (FIXME: what is the Guile port table?) in turn. The return value is unspecified. More specifically, proc is applied exactly once to every port that exists in the system at the time port-for-each is invoked. Changes to the port table while port-for-each is running have no effect as far as port-for-each is concerned.

The C function scm_port_for_each takes a Scheme procedure encoded as a SCM value, while scm_c_port_for_each takes a pointer to a C function and passes along a arbitrary data cookie.

Scheme Procedure: fcntl port/fd cmd [value]
C Function: scm_fcntl (object, cmd, value)

Apply cmd on port/fd, either a port or file descriptor. The value argument is used by the SET commands described below, it’s an integer value.

Values for cmd are:

Variable: F_DUPFD

Duplicate the file descriptor, the same as dup->fdes above does.

Variable: F_GETFD
Variable: F_SETFD

Get or set flags associated with the file descriptor. The only flag is the following,

Variable: FD_CLOEXEC

“Close on exec”, meaning the file descriptor will be closed on an exec call (a successful such call). For example to set that flag,

(fcntl port F_SETFD FD_CLOEXEC)

Or better, set it but leave any other possible future flags unchanged,

(fcntl port F_SETFD (logior FD_CLOEXEC
                            (fcntl port F_GETFD)))
Variable: F_GETFL
Variable: F_SETFL

Get or set flags associated with the open file. These flags are O_RDONLY etc described under open above.

A common use is to set O_NONBLOCK on a network socket. The following sets that flag, and leaves other flags unchanged.

(fcntl sock F_SETFL (logior O_NONBLOCK
                            (fcntl sock F_GETFL)))
Variable: F_GETOWN
Variable: F_SETOWN

Get or set the process ID of a socket’s owner, for SIGIO signals.

Scheme Procedure: flock file operation
C Function: scm_flock (file, operation)

Apply or remove an advisory lock on an open file. operation specifies the action to be done:

Variable: LOCK_SH

Shared lock. More than one process may hold a shared lock for a given file at a given time.

Variable: LOCK_EX

Exclusive lock. Only one process may hold an exclusive lock for a given file at a given time.

Variable: LOCK_UN

Unlock the file.

Variable: LOCK_NB

Don’t block when locking. This is combined with one of the other operations using logior (see Bitwise Operations). If flock would block an EWOULDBLOCK error is thrown (see Conventions).

The return value is not specified. file may be an open file descriptor or an open file descriptor port.

Note that flock does not lock files across NFS.

Scheme Procedure: select reads writes excepts [secs [usecs]]
C Function: scm_select (reads, writes, excepts, secs, usecs)

This procedure has a variety of uses: waiting for the ability to provide input, accept output, or the existence of exceptional conditions on a collection of ports or file descriptors, or waiting for a timeout to occur.

When an error occurs, this procedure throws a system-error exception (see system-error). Note that select may return early for other reasons, for example due to pending interrupts. See Asyncs, for more on interrupts.

reads, writes and excepts can be lists or vectors, with each member a port or a file descriptor. The value returned is a list of three corresponding lists or vectors containing only the members which meet the specified requirement. The ability of port buffers to provide input or accept output is taken into account. Ordering of the input lists or vectors is not preserved.

The optional arguments secs and usecs specify the timeout. Either secs can be specified alone, as either an integer or a real number, or both secs and usecs can be specified as integers, in which case usecs is an additional timeout expressed in microseconds. If secs is omitted or is #f then select will wait for as long as it takes for one of the other conditions to be satisfied.

The scsh version of select differs as follows: Only vectors are accepted for the first three arguments. The usecs argument is not supported. Multiple values are returned instead of a list. Duplicates in the input vectors appear only once in output. An additional select! interface is provided.

While it is sometimes necessary to operate at the level of file descriptors, this is an operation whose correctness can only be considered as part of a whole program. So for example while the effects of (string-set! x 34 #\y) are limited to the bits of code that can access x, (close-fdes 34) mutates the state of the entire process. In particular if another thread is using file descriptor 34 then their state might be corrupted; and another thread which opens a file might cause file descriptor 34 to be re-used, so that corruption could manifest itself in a strange way.

However when working with file descriptors, it’s common to want to associate information with the file descriptor, perhaps in a side table. To support this use case and to allow user code to remove an association when a file descriptor is closed, Guile offers fdes finalizers.

As the name indicates, fdes finalizers are finalizers – they can run in response to garbage collection, and they can also run in response to explicit calls to close-port, close-fdes, or the like. As such they inherit many of the pitfalls of finalizers: they may be invoked from concurrent threads, or not at all. See Foreign Object Memory Management, for more on finalizers.

To use fdes finalizers, import their module;

(use-modules (ice-9 fdes-finalizers))
Scheme Procedure: add-fdes-finalizer! fdes finalizer
Scheme Procedure: remove-fdes-finalizer! fdes finalizer

Add or remove a finalizer for fdes. A finalizer is a procedure that is called by Guile when a file descriptor is closed. The file descriptor being closed is passed as the one argument to the finalizer. If a finalizer has been added multiple times to a file descriptor, to remove it would require that number of calls to remove-fdes-finalizer!.

The finalizers added to a file descriptor are called by Guile in an unspecified order, and their return values are ignored.


Next: , Previous: , Up: POSIX   [Contents][Index]