Package-level declarations

Primitive: Create a directory with the indicated name and permissions. Answer a new fiber which, if creation is successful, will be started to run the success function. If the creation fails, then the fiber will be started to apply the failure function to the error code. The fiber runs at the specified priority.

Primitive: Answer the real path of the current working directory.

Primitive: Answer the absolute path that corresponds to the specified path.

Primitive: Is the specified path executable?

Primitive: Is the specified path readable?

Primitive: Is the specified path writable?

Primitive: Close the file associated with the specified handle. Forget the association between the handle and the file.

Primitive: Recursively copy the source path to the destination path.

Primitive: Does a file exist at the specified path? If the second argument is false, then no symbolic links will be traversed.

Primitive: Determine the transfer alignment of the underlying file. This might not agree with the buffer size used in higher level abstractions, but the VM manages buffers for the file along this alignment.

Primitive: Answer the group that owns the file denoted by the specified path.

Primitive: Answer the user that owns the file denoted by the specified path.

Primitive: Answer the ordinals (into IOSystem.posixPermissions) of the POSIX file permissions that describe the access rights granted by the file named by specified path.

Primitive: Determine whether the given filename is an absolute path.

Primitive: Answer the metadata for the file indicated by the specified path.

Primitive: Move the source path to the destination path. Use the supplied boolean to decide whether to permit the destination to be overwritten.

Primitive: Open an file. Answer a handle that uniquely identifies the file.

Primitive: Concatenate the elements of the specified tuple to form a platform-specific path.

Primitive: Split the specified path into its components.

Primitive: Read the requested number of bytes from the file channel associated with the specified handle, starting at the requested one-based position. Produce them as a tuple of bytes. If fewer bytes are available, then simply produce a shorter tuple; an empty tuple unambiguously indicates that the end of the file has been reached. If the request amount is infinite or very large, fewer bytes may be returned, at the discretion of the Avail VM.

Primitive: Answer the real path that corresponds to the specified path.

Primitive: Force all system buffers associated with the readable file channel associated with the handle to be discarded from the cache.

Primitive: Rename the source path to the destination path. Try not to overwrite an existing destination. This operation is only likely to work for two paths provided by the same file store.

Primitive: Do the specified paths denote the same file?

Primitive: Set the group owner of the file denoted by the specified path to the group denoted by the specified name.

Primitive: Set the owner of the file denoted by the specified path to the user denoted by the specified name.

Primitive: Set the access rights for the file specified by the given path.

Primitive: Answer the size of the file associated with the specified handle. Supports 64-bit file sizes.

Primitive: Force all system buffers associated with the writable file channel associated with the handle to synchronize with the underlying device.

Primitive: If the specified size is less than the size of the indicated writable file channel associated with the handle, then reduce its size as indicated, discarding any data beyond the new file size.

Primitive: Unlink the specified path from the file system.

Primitive: Write the specified tuple to the file associated with the handle. Writing begins at the specified one-based position of the file.