info.guardianproject.libcore.io

Class IoBridge

java.lang.Object

info.guardianproject.libcore.io.IoBridge

public final class IoBridge
extends java.lang.Object

Implements java.io/java.net/java.nio semantics in terms of the underlying POSIX system calls.

Method Summary

Modifier and Type	Method and Description
static void	checkOffsetAndCount(int arrayLength, int offset, int count) Checks that the range described by offset and count doesn't exceed arrayLength.
static FileDescriptor	open(java.lang.String path, int flags) java.io only throws FileNotFoundException when opening files, regardless of what actually went wrong.
static int	read(FileDescriptor fd, byte[] bytes, int byteOffset, int byteCount) java.io thinks that a read at EOF is an error and should return -1, contrary to traditional Unix practice where you'd read until you got 0 bytes (and any future read would return -1).
static void	write(FileDescriptor fd, byte[] bytes, int byteOffset, int byteCount, int flags) java.io always writes every byte it's asked to, or fails with an error.

Methods inherited from class java.lang.Object

clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

Method Detail

checkOffsetAndCount

public static void checkOffsetAndCount(int arrayLength,
                                       int offset,
                                       int count)

Checks that the range described by offset and count doesn't exceed arrayLength. This is from Android's java.util.Arrays.

open

public static FileDescriptor open(java.lang.String path,
                                  int flags)
                           throws java.io.FileNotFoundException

java.io only throws FileNotFoundException when opening files, regardless of what actually went wrong. Additionally, java.io is more restrictive than POSIX when it comes to opening directories: POSIX says read-only is okay, but java.io doesn't even allow that. We also have an Android-specific hack to alter the default permissions.

Throws:

java.io.FileNotFoundException

read

public static int read(FileDescriptor fd,
                       byte[] bytes,
                       int byteOffset,
                       int byteCount)
                throws java.io.IOException

java.io thinks that a read at EOF is an error and should return -1, contrary to traditional Unix practice where you'd read until you got 0 bytes (and any future read would return -1).

Throws:

java.io.IOException

write

public static void write(FileDescriptor fd,
                         byte[] bytes,
                         int byteOffset,
                         int byteCount,
                         int flags)
                  throws java.io.IOException

java.io always writes every byte it's asked to, or fails with an error. (That is, unlike Unix it never just writes as many bytes as happens to be convenient.)

Throws:

java.io.IOException