Common I/O Behaviors


The following table is an introduction to the common I/O behaviors.
 
Behavior Meaning

Auto close

Automatically closes the I/O object when it is destroyed.

Raw I/O

Reads and writes an interface using buffers of data without formatting or internal buffering. Raw I/O sends raw data buffers to and receives them from the underlying system calls.

I/O state

Each I/O object maintains a state indicating whether or not the object is ready for I/O.

Open control

An I/O object with an os_open_t parameter in its constructor is constructed either to access an existing object in the system or to create a new object.

You cannot change open control settings after an I/O object is opened. The os_open_control class encapsulates the variations in an os_open_t parameter.

I/O control

An I/O object with a constructor that takes an os_ioctl_t parameter, or has an interface containing io_control() , can be constructed with special I/O characteristics. These characteristics include the object's blocking mode.

The os_io_control class encapsulates the variations in an os_ioctl_t parameter.

Status

You can query many I/O objects for a status, which is returned in the form of an os_io_status object. This status object contains the object's size, device, inode number, user, group, and access times.

The following sections describe each I/O behavior in detail.

Open control and I/O control are flag-controlled behaviors. You can specify the value of these flags using one of the following.

Valid flags for each control are defined in the following sections.


Copyright©1994-2026 Recursion Software LLC
All Rights Reserved - For use by licensed users only.