.TH "physfs.h" 3 "Fri Oct 7 2022" "Version 3.2.0" "physfs" \" -*- nroff -*-
.ad l
.nh
.SH NAME
physfs.h
.SH SYNOPSIS
.br
.PP
.SS "Data Structures"

.in +1c
.ti -1c
.RI "struct \fBPHYSFS_File\fP"
.br
.RI "A PhysicsFS file handle\&. "
.ti -1c
.RI "struct \fBPHYSFS_ArchiveInfo\fP"
.br
.RI "Information on various PhysicsFS-supported archives\&. "
.ti -1c
.RI "struct \fBPHYSFS_Version\fP"
.br
.RI "Information the version of PhysicsFS in use\&. "
.ti -1c
.RI "struct \fBPHYSFS_Allocator\fP"
.br
.RI "PhysicsFS allocation function pointers\&. "
.ti -1c
.RI "struct \fBPHYSFS_Stat\fP"
.br
.RI "Meta data for a file or directory\&. "
.ti -1c
.RI "struct \fBPHYSFS_Io\fP"
.br
.RI "An abstract i/o interface\&. "
.ti -1c
.RI "struct \fBPHYSFS_Archiver\fP"
.br
.RI "Abstract interface to provide support for user-defined archives\&. "
.in -1c
.SS "Macros"

.in +1c
.ti -1c
.RI "#define \fBPHYSFS_file\fP   \fBPHYSFS_File\fP"
.br
.RI "1\&.0 API compatibility define\&. "
.ti -1c
.RI "#define \fBPHYSFS_VERSION\fP(x)"
.br
.RI "Macro to determine PhysicsFS version program was compiled against\&. "
.in -1c
.SS "Typedefs"

.in +1c
.ti -1c
.RI "typedef unsigned char \fBPHYSFS_uint8\fP"
.br
.RI "An unsigned, 8-bit integer type\&. "
.ti -1c
.RI "typedef signed char \fBPHYSFS_sint8\fP"
.br
.RI "A signed, 8-bit integer type\&. "
.ti -1c
.RI "typedef unsigned short \fBPHYSFS_uint16\fP"
.br
.RI "An unsigned, 16-bit integer type\&. "
.ti -1c
.RI "typedef signed short \fBPHYSFS_sint16\fP"
.br
.RI "A signed, 16-bit integer type\&. "
.ti -1c
.RI "typedef unsigned int \fBPHYSFS_uint32\fP"
.br
.RI "An unsigned, 32-bit integer type\&. "
.ti -1c
.RI "typedef signed int \fBPHYSFS_sint32\fP"
.br
.RI "A signed, 32-bit integer type\&. "
.ti -1c
.RI "typedef unsigned long long \fBPHYSFS_uint64\fP"
.br
.RI "An unsigned, 64-bit integer type\&. "
.ti -1c
.RI "typedef signed long long \fBPHYSFS_sint64\fP"
.br
.RI "A signed, 64-bit integer type\&. "
.ti -1c
.RI "typedef struct \fBPHYSFS_File\fP \fBPHYSFS_File\fP"
.br
.ti -1c
.RI "typedef struct \fBPHYSFS_ArchiveInfo\fP \fBPHYSFS_ArchiveInfo\fP"
.br
.ti -1c
.RI "typedef struct \fBPHYSFS_Version\fP \fBPHYSFS_Version\fP"
.br
.ti -1c
.RI "typedef struct \fBPHYSFS_Allocator\fP \fBPHYSFS_Allocator\fP"
.br
.ti -1c
.RI "typedef void(* \fBPHYSFS_StringCallback\fP) (void *data, const char *str)"
.br
.RI "Function signature for callbacks that report strings\&. "
.ti -1c
.RI "typedef void(* \fBPHYSFS_EnumFilesCallback\fP) (void *data, const char *origdir, const char *fname)"
.br
.RI "Function signature for callbacks that enumerate files\&. "
.ti -1c
.RI "typedef enum \fBPHYSFS_EnumerateCallbackResult\fP \fBPHYSFS_EnumerateCallbackResult\fP"
.br
.ti -1c
.RI "typedef \fBPHYSFS_EnumerateCallbackResult\fP(* \fBPHYSFS_EnumerateCallback\fP) (void *data, const char *origdir, const char *fname)"
.br
.RI "Possible return values from PHYSFS_EnumerateCallback\&. "
.ti -1c
.RI "typedef enum \fBPHYSFS_FileType\fP \fBPHYSFS_FileType\fP"
.br
.ti -1c
.RI "typedef struct \fBPHYSFS_Stat\fP \fBPHYSFS_Stat\fP"
.br
.ti -1c
.RI "typedef struct \fBPHYSFS_Io\fP \fBPHYSFS_Io\fP"
.br
.ti -1c
.RI "typedef enum \fBPHYSFS_ErrorCode\fP \fBPHYSFS_ErrorCode\fP"
.br
.ti -1c
.RI "typedef struct \fBPHYSFS_Archiver\fP \fBPHYSFS_Archiver\fP"
.br
.in -1c
.SS "Enumerations"

.in +1c
.ti -1c
.RI "enum \fBPHYSFS_EnumerateCallbackResult\fP { \fBPHYSFS_ENUM_ERROR\fP = -1, \fBPHYSFS_ENUM_STOP\fP = 0, \fBPHYSFS_ENUM_OK\fP = 1 }"
.br
.ti -1c
.RI "enum \fBPHYSFS_FileType\fP { \fBPHYSFS_FILETYPE_REGULAR\fP, \fBPHYSFS_FILETYPE_DIRECTORY\fP, \fBPHYSFS_FILETYPE_SYMLINK\fP, \fBPHYSFS_FILETYPE_OTHER\fP }"
.br
.RI "Type of a File\&. "
.ti -1c
.RI "enum \fBPHYSFS_ErrorCode\fP { \fBPHYSFS_ERR_OK\fP, \fBPHYSFS_ERR_OTHER_ERROR\fP, \fBPHYSFS_ERR_OUT_OF_MEMORY\fP, \fBPHYSFS_ERR_NOT_INITIALIZED\fP, \fBPHYSFS_ERR_IS_INITIALIZED\fP, \fBPHYSFS_ERR_ARGV0_IS_NULL\fP, \fBPHYSFS_ERR_UNSUPPORTED\fP, \fBPHYSFS_ERR_PAST_EOF\fP, \fBPHYSFS_ERR_FILES_STILL_OPEN\fP, \fBPHYSFS_ERR_INVALID_ARGUMENT\fP, \fBPHYSFS_ERR_NOT_MOUNTED\fP, \fBPHYSFS_ERR_NOT_FOUND\fP, \fBPHYSFS_ERR_SYMLINK_FORBIDDEN\fP, \fBPHYSFS_ERR_NO_WRITE_DIR\fP, \fBPHYSFS_ERR_OPEN_FOR_READING\fP, \fBPHYSFS_ERR_OPEN_FOR_WRITING\fP, \fBPHYSFS_ERR_NOT_A_FILE\fP, \fBPHYSFS_ERR_READ_ONLY\fP, \fBPHYSFS_ERR_CORRUPT\fP, \fBPHYSFS_ERR_SYMLINK_LOOP\fP, \fBPHYSFS_ERR_IO\fP, \fBPHYSFS_ERR_PERMISSION\fP, \fBPHYSFS_ERR_NO_SPACE\fP, \fBPHYSFS_ERR_BAD_FILENAME\fP, \fBPHYSFS_ERR_BUSY\fP, \fBPHYSFS_ERR_DIR_NOT_EMPTY\fP, \fBPHYSFS_ERR_OS_ERROR\fP, \fBPHYSFS_ERR_DUPLICATE\fP, \fBPHYSFS_ERR_BAD_PASSWORD\fP, \fBPHYSFS_ERR_APP_CALLBACK\fP }"
.br
.RI "Values that represent specific causes of failure\&. "
.in -1c
.SS "Functions"

.in +1c
.ti -1c
.RI "void \fBPHYSFS_getLinkedVersion\fP (\fBPHYSFS_Version\fP *ver)"
.br
.RI "Get the version of PhysicsFS that is linked against your program\&. "
.ti -1c
.RI "int \fBPHYSFS_init\fP (const char *argv0)"
.br
.RI "Initialize the PhysicsFS library\&. "
.ti -1c
.RI "int \fBPHYSFS_deinit\fP (void)"
.br
.RI "Deinitialize the PhysicsFS library\&. "
.ti -1c
.RI "const \fBPHYSFS_ArchiveInfo\fP ** \fBPHYSFS_supportedArchiveTypes\fP (void)"
.br
.RI "Get a list of supported archive types\&. "
.ti -1c
.RI "void \fBPHYSFS_freeList\fP (void *listVar)"
.br
.RI "Deallocate resources of lists returned by PhysicsFS\&. "
.ti -1c
.RI "const char * \fBPHYSFS_getLastError\fP (void)"
.br
.RI "Get human-readable error information\&. "
.ti -1c
.RI "const char * \fBPHYSFS_getDirSeparator\fP (void)"
.br
.RI "Get platform-dependent dir separator string\&. "
.ti -1c
.RI "void \fBPHYSFS_permitSymbolicLinks\fP (int allow)"
.br
.RI "Enable or disable following of symbolic links\&. "
.ti -1c
.RI "char ** \fBPHYSFS_getCdRomDirs\fP (void)"
.br
.RI "Get an array of paths to available CD-ROM drives\&. "
.ti -1c
.RI "const char * \fBPHYSFS_getBaseDir\fP (void)"
.br
.RI "Get the path where the application resides\&. "
.ti -1c
.RI "const char * \fBPHYSFS_getUserDir\fP (void)"
.br
.RI "Get the path where user's home directory resides\&. "
.ti -1c
.RI "const char * \fBPHYSFS_getWriteDir\fP (void)"
.br
.RI "Get path where PhysicsFS will allow file writing\&. "
.ti -1c
.RI "int \fBPHYSFS_setWriteDir\fP (const char *newDir)"
.br
.RI "Tell PhysicsFS where it may write files\&. "
.ti -1c
.RI "int \fBPHYSFS_addToSearchPath\fP (const char *newDir, int appendToPath)"
.br
.RI "Add an archive or directory to the search path\&. "
.ti -1c
.RI "int \fBPHYSFS_removeFromSearchPath\fP (const char *oldDir)"
.br
.RI "Remove a directory or archive from the search path\&. "
.ti -1c
.RI "char ** \fBPHYSFS_getSearchPath\fP (void)"
.br
.RI "Get the current search path\&. "
.ti -1c
.RI "int \fBPHYSFS_setSaneConfig\fP (const char *organization, const char *appName, const char *archiveExt, int includeCdRoms, int archivesFirst)"
.br
.RI "Set up sane, default paths\&. "
.ti -1c
.RI "int \fBPHYSFS_mkdir\fP (const char *dirName)"
.br
.RI "Create a directory\&. "
.ti -1c
.RI "int \fBPHYSFS_delete\fP (const char *filename)"
.br
.RI "Delete a file or directory\&. "
.ti -1c
.RI "const char * \fBPHYSFS_getRealDir\fP (const char *filename)"
.br
.RI "Figure out where in the search path a file resides\&. "
.ti -1c
.RI "char ** \fBPHYSFS_enumerateFiles\fP (const char *dir)"
.br
.RI "Get a file listing of a search path's directory\&. "
.ti -1c
.RI "int \fBPHYSFS_exists\fP (const char *fname)"
.br
.RI "Determine if a file exists in the search path\&. "
.ti -1c
.RI "int \fBPHYSFS_isDirectory\fP (const char *fname)"
.br
.RI "Determine if a file in the search path is really a directory\&. "
.ti -1c
.RI "int \fBPHYSFS_isSymbolicLink\fP (const char *fname)"
.br
.RI "Determine if a file in the search path is really a symbolic link\&. "
.ti -1c
.RI "\fBPHYSFS_sint64\fP \fBPHYSFS_getLastModTime\fP (const char *filename)"
.br
.RI "Get the last modification time of a file\&. "
.ti -1c
.RI "\fBPHYSFS_File\fP * \fBPHYSFS_openWrite\fP (const char *filename)"
.br
.RI "Open a file for writing\&. "
.ti -1c
.RI "\fBPHYSFS_File\fP * \fBPHYSFS_openAppend\fP (const char *filename)"
.br
.RI "Open a file for appending\&. "
.ti -1c
.RI "\fBPHYSFS_File\fP * \fBPHYSFS_openRead\fP (const char *filename)"
.br
.RI "Open a file for reading\&. "
.ti -1c
.RI "int \fBPHYSFS_close\fP (\fBPHYSFS_File\fP *handle)"
.br
.RI "Close a PhysicsFS filehandle\&. "
.ti -1c
.RI "\fBPHYSFS_sint64\fP \fBPHYSFS_read\fP (\fBPHYSFS_File\fP *handle, void *buffer, \fBPHYSFS_uint32\fP objSize, \fBPHYSFS_uint32\fP objCount)"
.br
.RI "Read data from a PhysicsFS filehandle\&. "
.ti -1c
.RI "\fBPHYSFS_sint64\fP \fBPHYSFS_write\fP (\fBPHYSFS_File\fP *handle, const void *buffer, \fBPHYSFS_uint32\fP objSize, \fBPHYSFS_uint32\fP objCount)"
.br
.RI "Write data to a PhysicsFS filehandle\&. "
.ti -1c
.RI "int \fBPHYSFS_eof\fP (\fBPHYSFS_File\fP *handle)"
.br
.RI "Check for end-of-file state on a PhysicsFS filehandle\&. "
.ti -1c
.RI "\fBPHYSFS_sint64\fP \fBPHYSFS_tell\fP (\fBPHYSFS_File\fP *handle)"
.br
.RI "Determine current position within a PhysicsFS filehandle\&. "
.ti -1c
.RI "int \fBPHYSFS_seek\fP (\fBPHYSFS_File\fP *handle, \fBPHYSFS_uint64\fP pos)"
.br
.RI "Seek to a new position within a PhysicsFS filehandle\&. "
.ti -1c
.RI "\fBPHYSFS_sint64\fP \fBPHYSFS_fileLength\fP (\fBPHYSFS_File\fP *handle)"
.br
.RI "Get total length of a file in bytes\&. "
.ti -1c
.RI "int \fBPHYSFS_setBuffer\fP (\fBPHYSFS_File\fP *handle, \fBPHYSFS_uint64\fP bufsize)"
.br
.RI "Set up buffering for a PhysicsFS file handle\&. "
.ti -1c
.RI "int \fBPHYSFS_flush\fP (\fBPHYSFS_File\fP *handle)"
.br
.RI "Flush a buffered PhysicsFS file handle\&. "
.ti -1c
.RI "\fBPHYSFS_sint16\fP \fBPHYSFS_swapSLE16\fP (\fBPHYSFS_sint16\fP val)"
.br
.RI "Swap littleendian signed 16 to platform's native byte order\&. "
.ti -1c
.RI "\fBPHYSFS_uint16\fP \fBPHYSFS_swapULE16\fP (\fBPHYSFS_uint16\fP val)"
.br
.RI "Swap littleendian unsigned 16 to platform's native byte order\&. "
.ti -1c
.RI "\fBPHYSFS_sint32\fP \fBPHYSFS_swapSLE32\fP (\fBPHYSFS_sint32\fP val)"
.br
.RI "Swap littleendian signed 32 to platform's native byte order\&. "
.ti -1c
.RI "\fBPHYSFS_uint32\fP \fBPHYSFS_swapULE32\fP (\fBPHYSFS_uint32\fP val)"
.br
.RI "Swap littleendian unsigned 32 to platform's native byte order\&. "
.ti -1c
.RI "\fBPHYSFS_sint64\fP \fBPHYSFS_swapSLE64\fP (\fBPHYSFS_sint64\fP val)"
.br
.RI "Swap littleendian signed 64 to platform's native byte order\&. "
.ti -1c
.RI "\fBPHYSFS_uint64\fP \fBPHYSFS_swapULE64\fP (\fBPHYSFS_uint64\fP val)"
.br
.RI "Swap littleendian unsigned 64 to platform's native byte order\&. "
.ti -1c
.RI "\fBPHYSFS_sint16\fP \fBPHYSFS_swapSBE16\fP (\fBPHYSFS_sint16\fP val)"
.br
.RI "Swap bigendian signed 16 to platform's native byte order\&. "
.ti -1c
.RI "\fBPHYSFS_uint16\fP \fBPHYSFS_swapUBE16\fP (\fBPHYSFS_uint16\fP val)"
.br
.RI "Swap bigendian unsigned 16 to platform's native byte order\&. "
.ti -1c
.RI "\fBPHYSFS_sint32\fP \fBPHYSFS_swapSBE32\fP (\fBPHYSFS_sint32\fP val)"
.br
.RI "Swap bigendian signed 32 to platform's native byte order\&. "
.ti -1c
.RI "\fBPHYSFS_uint32\fP \fBPHYSFS_swapUBE32\fP (\fBPHYSFS_uint32\fP val)"
.br
.RI "Swap bigendian unsigned 32 to platform's native byte order\&. "
.ti -1c
.RI "\fBPHYSFS_sint64\fP \fBPHYSFS_swapSBE64\fP (\fBPHYSFS_sint64\fP val)"
.br
.RI "Swap bigendian signed 64 to platform's native byte order\&. "
.ti -1c
.RI "\fBPHYSFS_uint64\fP \fBPHYSFS_swapUBE64\fP (\fBPHYSFS_uint64\fP val)"
.br
.RI "Swap bigendian unsigned 64 to platform's native byte order\&. "
.ti -1c
.RI "int \fBPHYSFS_readSLE16\fP (\fBPHYSFS_File\fP *file, \fBPHYSFS_sint16\fP *val)"
.br
.RI "Read and convert a signed 16-bit littleendian value\&. "
.ti -1c
.RI "int \fBPHYSFS_readULE16\fP (\fBPHYSFS_File\fP *file, \fBPHYSFS_uint16\fP *val)"
.br
.RI "Read and convert an unsigned 16-bit littleendian value\&. "
.ti -1c
.RI "int \fBPHYSFS_readSBE16\fP (\fBPHYSFS_File\fP *file, \fBPHYSFS_sint16\fP *val)"
.br
.RI "Read and convert a signed 16-bit bigendian value\&. "
.ti -1c
.RI "int \fBPHYSFS_readUBE16\fP (\fBPHYSFS_File\fP *file, \fBPHYSFS_uint16\fP *val)"
.br
.RI "Read and convert an unsigned 16-bit bigendian value\&. "
.ti -1c
.RI "int \fBPHYSFS_readSLE32\fP (\fBPHYSFS_File\fP *file, \fBPHYSFS_sint32\fP *val)"
.br
.RI "Read and convert a signed 32-bit littleendian value\&. "
.ti -1c
.RI "int \fBPHYSFS_readULE32\fP (\fBPHYSFS_File\fP *file, \fBPHYSFS_uint32\fP *val)"
.br
.RI "Read and convert an unsigned 32-bit littleendian value\&. "
.ti -1c
.RI "int \fBPHYSFS_readSBE32\fP (\fBPHYSFS_File\fP *file, \fBPHYSFS_sint32\fP *val)"
.br
.RI "Read and convert a signed 32-bit bigendian value\&. "
.ti -1c
.RI "int \fBPHYSFS_readUBE32\fP (\fBPHYSFS_File\fP *file, \fBPHYSFS_uint32\fP *val)"
.br
.RI "Read and convert an unsigned 32-bit bigendian value\&. "
.ti -1c
.RI "int \fBPHYSFS_readSLE64\fP (\fBPHYSFS_File\fP *file, \fBPHYSFS_sint64\fP *val)"
.br
.RI "Read and convert a signed 64-bit littleendian value\&. "
.ti -1c
.RI "int \fBPHYSFS_readULE64\fP (\fBPHYSFS_File\fP *file, \fBPHYSFS_uint64\fP *val)"
.br
.RI "Read and convert an unsigned 64-bit littleendian value\&. "
.ti -1c
.RI "int \fBPHYSFS_readSBE64\fP (\fBPHYSFS_File\fP *file, \fBPHYSFS_sint64\fP *val)"
.br
.RI "Read and convert a signed 64-bit bigendian value\&. "
.ti -1c
.RI "int \fBPHYSFS_readUBE64\fP (\fBPHYSFS_File\fP *file, \fBPHYSFS_uint64\fP *val)"
.br
.RI "Read and convert an unsigned 64-bit bigendian value\&. "
.ti -1c
.RI "int \fBPHYSFS_writeSLE16\fP (\fBPHYSFS_File\fP *file, \fBPHYSFS_sint16\fP val)"
.br
.RI "Convert and write a signed 16-bit littleendian value\&. "
.ti -1c
.RI "int \fBPHYSFS_writeULE16\fP (\fBPHYSFS_File\fP *file, \fBPHYSFS_uint16\fP val)"
.br
.RI "Convert and write an unsigned 16-bit littleendian value\&. "
.ti -1c
.RI "int \fBPHYSFS_writeSBE16\fP (\fBPHYSFS_File\fP *file, \fBPHYSFS_sint16\fP val)"
.br
.RI "Convert and write a signed 16-bit bigendian value\&. "
.ti -1c
.RI "int \fBPHYSFS_writeUBE16\fP (\fBPHYSFS_File\fP *file, \fBPHYSFS_uint16\fP val)"
.br
.RI "Convert and write an unsigned 16-bit bigendian value\&. "
.ti -1c
.RI "int \fBPHYSFS_writeSLE32\fP (\fBPHYSFS_File\fP *file, \fBPHYSFS_sint32\fP val)"
.br
.RI "Convert and write a signed 32-bit littleendian value\&. "
.ti -1c
.RI "int \fBPHYSFS_writeULE32\fP (\fBPHYSFS_File\fP *file, \fBPHYSFS_uint32\fP val)"
.br
.RI "Convert and write an unsigned 32-bit littleendian value\&. "
.ti -1c
.RI "int \fBPHYSFS_writeSBE32\fP (\fBPHYSFS_File\fP *file, \fBPHYSFS_sint32\fP val)"
.br
.RI "Convert and write a signed 32-bit bigendian value\&. "
.ti -1c
.RI "int \fBPHYSFS_writeUBE32\fP (\fBPHYSFS_File\fP *file, \fBPHYSFS_uint32\fP val)"
.br
.RI "Convert and write an unsigned 32-bit bigendian value\&. "
.ti -1c
.RI "int \fBPHYSFS_writeSLE64\fP (\fBPHYSFS_File\fP *file, \fBPHYSFS_sint64\fP val)"
.br
.RI "Convert and write a signed 64-bit littleendian value\&. "
.ti -1c
.RI "int \fBPHYSFS_writeULE64\fP (\fBPHYSFS_File\fP *file, \fBPHYSFS_uint64\fP val)"
.br
.RI "Convert and write an unsigned 64-bit littleendian value\&. "
.ti -1c
.RI "int \fBPHYSFS_writeSBE64\fP (\fBPHYSFS_File\fP *file, \fBPHYSFS_sint64\fP val)"
.br
.RI "Convert and write a signed 64-bit bigending value\&. "
.ti -1c
.RI "int \fBPHYSFS_writeUBE64\fP (\fBPHYSFS_File\fP *file, \fBPHYSFS_uint64\fP val)"
.br
.RI "Convert and write an unsigned 64-bit bigendian value\&. "
.ti -1c
.RI "int \fBPHYSFS_isInit\fP (void)"
.br
.RI "Determine if the PhysicsFS library is initialized\&. "
.ti -1c
.RI "int \fBPHYSFS_symbolicLinksPermitted\fP (void)"
.br
.RI "Determine if the symbolic links are permitted\&. "
.ti -1c
.RI "int \fBPHYSFS_setAllocator\fP (const \fBPHYSFS_Allocator\fP *allocator)"
.br
.RI "Hook your own allocation routines into PhysicsFS\&. "
.ti -1c
.RI "int \fBPHYSFS_mount\fP (const char *newDir, const char *mountPoint, int appendToPath)"
.br
.RI "Add an archive or directory to the search path\&. "
.ti -1c
.RI "const char * \fBPHYSFS_getMountPoint\fP (const char *dir)"
.br
.RI "Determine a mounted archive's mountpoint\&. "
.ti -1c
.RI "void \fBPHYSFS_getCdRomDirsCallback\fP (\fBPHYSFS_StringCallback\fP c, void *d)"
.br
.RI "Enumerate CD-ROM directories, using an application-defined callback\&. "
.ti -1c
.RI "void \fBPHYSFS_getSearchPathCallback\fP (\fBPHYSFS_StringCallback\fP c, void *d)"
.br
.RI "Enumerate the search path, using an application-defined callback\&. "
.ti -1c
.RI "void \fBPHYSFS_enumerateFilesCallback\fP (const char *dir, \fBPHYSFS_EnumFilesCallback\fP c, void *d)"
.br
.RI "Get a file listing of a search path's directory, using an application-defined callback\&. "
.ti -1c
.RI "void \fBPHYSFS_utf8FromUcs4\fP (const \fBPHYSFS_uint32\fP *src, char *dst, \fBPHYSFS_uint64\fP len)"
.br
.RI "Convert a UCS-4 string to a UTF-8 string\&. "
.ti -1c
.RI "void \fBPHYSFS_utf8ToUcs4\fP (const char *src, \fBPHYSFS_uint32\fP *dst, \fBPHYSFS_uint64\fP len)"
.br
.RI "Convert a UTF-8 string to a UCS-4 string\&. "
.ti -1c
.RI "void \fBPHYSFS_utf8FromUcs2\fP (const \fBPHYSFS_uint16\fP *src, char *dst, \fBPHYSFS_uint64\fP len)"
.br
.RI "Convert a UCS-2 string to a UTF-8 string\&. "
.ti -1c
.RI "void \fBPHYSFS_utf8ToUcs2\fP (const char *src, \fBPHYSFS_uint16\fP *dst, \fBPHYSFS_uint64\fP len)"
.br
.RI "Convert a UTF-8 string to a UCS-2 string\&. "
.ti -1c
.RI "void \fBPHYSFS_utf8FromLatin1\fP (const char *src, char *dst, \fBPHYSFS_uint64\fP len)"
.br
.RI "Convert a UTF-8 string to a Latin1 string\&. "
.ti -1c
.RI "int \fBPHYSFS_caseFold\fP (const \fBPHYSFS_uint32\fP from, \fBPHYSFS_uint32\fP *to)"
.br
.RI "'Fold' a Unicode codepoint to a lowercase equivalent\&. "
.ti -1c
.RI "int \fBPHYSFS_utf8stricmp\fP (const char *str1, const char *str2)"
.br
.RI "Case-insensitive compare of two UTF-8 strings\&. "
.ti -1c
.RI "int \fBPHYSFS_utf16stricmp\fP (const \fBPHYSFS_uint16\fP *str1, const \fBPHYSFS_uint16\fP *str2)"
.br
.RI "Case-insensitive compare of two UTF-16 strings\&. "
.ti -1c
.RI "int \fBPHYSFS_ucs4stricmp\fP (const \fBPHYSFS_uint32\fP *str1, const \fBPHYSFS_uint32\fP *str2)"
.br
.RI "Case-insensitive compare of two UCS-4 strings\&. "
.ti -1c
.RI "int \fBPHYSFS_enumerate\fP (const char *dir, \fBPHYSFS_EnumerateCallback\fP c, void *d)"
.br
.RI "Get a file listing of a search path's directory, using an application-defined callback, with errors reported\&. "
.ti -1c
.RI "int \fBPHYSFS_unmount\fP (const char *oldDir)"
.br
.RI "Remove a directory or archive from the search path\&. "
.ti -1c
.RI "const \fBPHYSFS_Allocator\fP * \fBPHYSFS_getAllocator\fP (void)"
.br
.RI "Discover the current allocator\&. "
.ti -1c
.RI "int \fBPHYSFS_stat\fP (const char *fname, \fBPHYSFS_Stat\fP *stat)"
.br
.RI "Get various information about a directory or a file\&. "
.ti -1c
.RI "void \fBPHYSFS_utf8FromUtf16\fP (const \fBPHYSFS_uint16\fP *src, char *dst, \fBPHYSFS_uint64\fP len)"
.br
.RI "Convert a UTF-16 string to a UTF-8 string\&. "
.ti -1c
.RI "void \fBPHYSFS_utf8ToUtf16\fP (const char *src, \fBPHYSFS_uint16\fP *dst, \fBPHYSFS_uint64\fP len)"
.br
.RI "Convert a UTF-8 string to a UTF-16 string\&. "
.ti -1c
.RI "\fBPHYSFS_sint64\fP \fBPHYSFS_readBytes\fP (\fBPHYSFS_File\fP *handle, void *buffer, \fBPHYSFS_uint64\fP len)"
.br
.RI "Read bytes from a PhysicsFS filehandle\&. "
.ti -1c
.RI "\fBPHYSFS_sint64\fP \fBPHYSFS_writeBytes\fP (\fBPHYSFS_File\fP *handle, const void *buffer, \fBPHYSFS_uint64\fP len)"
.br
.RI "Write data to a PhysicsFS filehandle\&. "
.ti -1c
.RI "int \fBPHYSFS_mountIo\fP (\fBPHYSFS_Io\fP *io, const char *newDir, const char *mountPoint, int appendToPath)"
.br
.RI "Add an archive, built on a \fBPHYSFS_Io\fP, to the search path\&. "
.ti -1c
.RI "int \fBPHYSFS_mountMemory\fP (const void *buf, \fBPHYSFS_uint64\fP len, void(*del)(void *), const char *newDir, const char *mountPoint, int appendToPath)"
.br
.RI "Add an archive, contained in a memory buffer, to the search path\&. "
.ti -1c
.RI "int \fBPHYSFS_mountHandle\fP (\fBPHYSFS_File\fP *file, const char *newDir, const char *mountPoint, int appendToPath)"
.br
.RI "Add an archive, contained in a \fBPHYSFS_File\fP handle, to the search path\&. "
.ti -1c
.RI "\fBPHYSFS_ErrorCode\fP \fBPHYSFS_getLastErrorCode\fP (void)"
.br
.RI "Get machine-readable error information\&. "
.ti -1c
.RI "const char * \fBPHYSFS_getErrorByCode\fP (\fBPHYSFS_ErrorCode\fP code)"
.br
.RI "Get human-readable description string for a given error code\&. "
.ti -1c
.RI "void \fBPHYSFS_setErrorCode\fP (\fBPHYSFS_ErrorCode\fP code)"
.br
.RI "Set the current thread's error code\&. "
.ti -1c
.RI "const char * \fBPHYSFS_getPrefDir\fP (const char *org, const char *app)"
.br
.RI "Get the user-and-app-specific path where files can be written\&. "
.ti -1c
.RI "int \fBPHYSFS_registerArchiver\fP (const \fBPHYSFS_Archiver\fP *archiver)"
.br
.RI "Add a new archiver to the system\&. "
.ti -1c
.RI "int \fBPHYSFS_deregisterArchiver\fP (const char *ext)"
.br
.RI "Remove an archiver from the system\&. "
.ti -1c
.RI "int \fBPHYSFS_setRoot\fP (const char *archive, const char *subdir)"
.br
.RI "Make a subdirectory of an archive its root directory\&. "
.in -1c
.SH "Detailed Description"
.PP 
Main header file for PhysicsFS\&. 
.SH "Macro Definition Documentation"
.PP 
.SS "#define PHYSFS_file   \fBPHYSFS_File\fP"

.PP
1\&.0 API compatibility define\&. PHYSFS_file is identical to \fBPHYSFS_File\fP\&. This #define is here for backwards compatibility with the 1\&.0 API, which had an inconsistent capitalization convention in this case\&. New code should use \fBPHYSFS_File\fP, as this #define may go away someday\&.
.PP
\fBSee also\fP
.RS 4
\fBPHYSFS_File\fP 
.RE
.PP

.SS "#define PHYSFS_VERSION(x)"
\fBValue:\fP
.PP
.nf
{ \
    (x)->major = PHYSFS_VER_MAJOR; \
    (x)->minor = PHYSFS_VER_MINOR; \
    (x)->patch = PHYSFS_VER_PATCH; \
}
.fi
.PP
Macro to determine PhysicsFS version program was compiled against\&. This macro fills in a \fBPHYSFS_Version\fP structure with the version of the library you compiled against\&. This is determined by what header the compiler uses\&. Note that if you dynamically linked the library, you might have a slightly newer or older version at runtime\&. That version can be determined with \fBPHYSFS_getLinkedVersion()\fP, which, unlike PHYSFS_VERSION, is not a macro\&.
.PP
\fBParameters\fP
.RS 4
\fIx\fP A pointer to a \fBPHYSFS_Version\fP struct to initialize\&.
.RE
.PP
\fBSee also\fP
.RS 4
\fBPHYSFS_Version\fP 
.PP
\fBPHYSFS_getLinkedVersion\fP 
.RE
.PP

.SH "Typedef Documentation"
.PP 
.SS "PHYSFS_EnumerateCallback"

.PP
Possible return values from PHYSFS_EnumerateCallback\&. Function signature for callbacks that enumerate and return results\&.
.PP
These values dictate if an enumeration callback should continue to fire, or stop (and why it is stopping)\&.
.PP
\fBSee also\fP
.RS 4
\fBPHYSFS_EnumerateCallback\fP 
.PP
\fBPHYSFS_enumerate\fP
.RE
.PP
This is the same thing as PHYSFS_EnumFilesCallback from PhysicsFS 2\&.0, except it can return a result from the callback: namely: if you're looking for something specific, once you find it, you can tell PhysicsFS to stop enumerating further\&. This is used with \fBPHYSFS_enumerate()\fP, which we hopefully got right this time\&. :)
.PP
\fBParameters\fP
.RS 4
\fIdata\fP User-defined data pointer, passed through from the API that eventually called the callback\&. 
.br
\fIorigdir\fP A string containing the full path, in platform-independent notation, of the directory containing this file\&. In most cases, this is the directory on which you requested enumeration, passed in the callback for your convenience\&. 
.br
\fIfname\fP The filename that is being enumerated\&. It may not be in alphabetical order compared to other callbacks that have fired, and it will not contain the full path\&. You can recreate the fullpath with $origdir/$fname \&.\&.\&. The file can be a subdirectory, a file, a symlink, etc\&. 
.RE
.PP
\fBReturns\fP
.RS 4
A value from PHYSFS_EnumerateCallbackResult\&. All other values are (currently) undefined; don't use them\&.
.RE
.PP
\fBSee also\fP
.RS 4
\fBPHYSFS_enumerate\fP 
.PP
\fBPHYSFS_EnumerateCallbackResult\fP 
.RE
.PP

.SS "PHYSFS_EnumFilesCallback"

.PP
Function signature for callbacks that enumerate files\&. 
.PP
\fBWarning\fP
.RS 4
As of PhysicsFS 2\&.1, Use PHYSFS_EnumerateCallback with \fBPHYSFS_enumerate()\fP instead; it gives you more control over the process\&.
.RE
.PP
These are used to report a list of directory entries to an original caller, one file/dir/symlink per callback\&. All strings are UTF-8 encoded\&. Functions should not try to modify or free any string's memory\&.
.PP
These callbacks are used, starting in PhysicsFS 1\&.1, as an alternative to functions that would return lists that need to be cleaned up with \fBPHYSFS_freeList()\fP\&. The callback means that the library doesn't need to allocate an entire list and all the strings up front\&.
.PP
Be aware that promised data ordering in the list versions are not necessarily so in the callback versions\&. Check the documentation on specific APIs, but strings may not be sorted as you expect and you might get duplicate strings\&.
.PP
\fBParameters\fP
.RS 4
\fIdata\fP User-defined data pointer, passed through from the API that eventually called the callback\&. 
.br
\fIorigdir\fP A string containing the full path, in platform-independent notation, of the directory containing this file\&. In most cases, this is the directory on which you requested enumeration, passed in the callback for your convenience\&. 
.br
\fIfname\fP The filename that is being enumerated\&. It may not be in alphabetical order compared to other callbacks that have fired, and it will not contain the full path\&. You can recreate the fullpath with $origdir/$fname \&.\&.\&. The file can be a subdirectory, a file, a symlink, etc\&.
.RE
.PP
\fBSee also\fP
.RS 4
\fBPHYSFS_enumerateFilesCallback\fP 
.RE
.PP

.SS "\fBPHYSFS_sint64\fP"

.PP
A signed, 64-bit integer type\&. 
.PP
\fBWarning\fP
.RS 4
on platforms without any sort of 64-bit datatype, this is equivalent to PHYSFS_sint32! 
.RE
.PP

.SS "PHYSFS_StringCallback"

.PP
Function signature for callbacks that report strings\&. These are used to report a list of strings to an original caller, one string per callback\&. All strings are UTF-8 encoded\&. Functions should not try to modify or free the string's memory\&.
.PP
These callbacks are used, starting in PhysicsFS 1\&.1, as an alternative to functions that would return lists that need to be cleaned up with \fBPHYSFS_freeList()\fP\&. The callback means that the library doesn't need to allocate an entire list and all the strings up front\&.
.PP
Be aware that promises data ordering in the list versions are not necessarily so in the callback versions\&. Check the documentation on specific APIs, but strings may not be sorted as you expect\&.
.PP
\fBParameters\fP
.RS 4
\fIdata\fP User-defined data pointer, passed through from the API that eventually called the callback\&. 
.br
\fIstr\fP The string data about which the callback is meant to inform\&.
.RE
.PP
\fBSee also\fP
.RS 4
\fBPHYSFS_getCdRomDirsCallback\fP 
.PP
\fBPHYSFS_getSearchPathCallback\fP 
.RE
.PP

.SS "\fBPHYSFS_uint64\fP"

.PP
An unsigned, 64-bit integer type\&. 
.PP
\fBWarning\fP
.RS 4
on platforms without any sort of 64-bit datatype, this is equivalent to PHYSFS_uint32! 
.RE
.PP

.SH "Enumeration Type Documentation"
.PP 
.SS "enum \fBPHYSFS_EnumerateCallbackResult\fP"

.PP
\fBEnumerator\fP
.in +1c
.TP
\fB\fIPHYSFS_ENUM_ERROR \fP\fP
Stop enumerating, report error to app\&. 
.TP
\fB\fIPHYSFS_ENUM_STOP \fP\fP
Stop enumerating, report success to app\&. 
.TP
\fB\fIPHYSFS_ENUM_OK \fP\fP
Keep enumerating, no problems 
.SS "enum \fBPHYSFS_ErrorCode\fP"

.PP
Values that represent specific causes of failure\&. Most of the time, you should only concern yourself with whether a given operation failed or not, but there may be occasions where you plan to handle a specific failure case gracefully, so we provide specific error codes\&.
.PP
Most of these errors are a little vague, and most aren't things you can fix\&.\&.\&.if there's a permission error, for example, all you can really do is pass that information on to the user and let them figure out how to handle it\&. In most these cases, your program should only care that it failed to accomplish its goals, and not care specifically why\&.
.PP
\fBSee also\fP
.RS 4
\fBPHYSFS_getLastErrorCode\fP 
.PP
\fBPHYSFS_getErrorByCode\fP 
.RE
.PP

.PP
\fBEnumerator\fP
.in +1c
.TP
\fB\fIPHYSFS_ERR_OK \fP\fP
Success; no error\&. 
.br
 
.TP
\fB\fIPHYSFS_ERR_OTHER_ERROR \fP\fP
Error not otherwise covered here\&. 
.br
 
.TP
\fB\fIPHYSFS_ERR_OUT_OF_MEMORY \fP\fP
Memory allocation failed\&. 
.br
 
.TP
\fB\fIPHYSFS_ERR_NOT_INITIALIZED \fP\fP
PhysicsFS is not initialized\&. 
.br
 
.TP
\fB\fIPHYSFS_ERR_IS_INITIALIZED \fP\fP
PhysicsFS is already initialized\&. 
.br
 
.TP
\fB\fIPHYSFS_ERR_ARGV0_IS_NULL \fP\fP
Needed argv[0], but it is NULL\&. 
.br
 
.TP
\fB\fIPHYSFS_ERR_UNSUPPORTED \fP\fP
Operation or feature unsupported\&. 
.br
 
.TP
\fB\fIPHYSFS_ERR_PAST_EOF \fP\fP
Attempted to access past end of file\&. 
.TP
\fB\fIPHYSFS_ERR_FILES_STILL_OPEN \fP\fP
Files still open\&. 
.br
 
.TP
\fB\fIPHYSFS_ERR_INVALID_ARGUMENT \fP\fP
Bad parameter passed to an function\&. 
.br
 
.TP
\fB\fIPHYSFS_ERR_NOT_MOUNTED \fP\fP
Requested archive/dir not mounted\&. 
.br
 
.TP
\fB\fIPHYSFS_ERR_NOT_FOUND \fP\fP
File (or whatever) not found\&. 
.br
 
.TP
\fB\fIPHYSFS_ERR_SYMLINK_FORBIDDEN \fP\fP
Symlink seen when not permitted\&. 
.br
 
.TP
\fB\fIPHYSFS_ERR_NO_WRITE_DIR \fP\fP
No write dir has been specified\&. 
.br
 
.TP
\fB\fIPHYSFS_ERR_OPEN_FOR_READING \fP\fP
Wrote to a file opened for reading\&. 
.br
 
.TP
\fB\fIPHYSFS_ERR_OPEN_FOR_WRITING \fP\fP
Read from a file opened for writing\&. 
.br
 
.TP
\fB\fIPHYSFS_ERR_NOT_A_FILE \fP\fP
Needed a file, got a directory (etc)\&. 
.TP
\fB\fIPHYSFS_ERR_READ_ONLY \fP\fP
Wrote to a read-only filesystem\&. 
.br
 
.TP
\fB\fIPHYSFS_ERR_CORRUPT \fP\fP
Corrupted data encountered\&. 
.br
 
.TP
\fB\fIPHYSFS_ERR_SYMLINK_LOOP \fP\fP
Infinite symbolic link loop\&. 
.br
 
.TP
\fB\fIPHYSFS_ERR_IO \fP\fP
i/o error (hardware failure, etc)\&. 
.br
 
.TP
\fB\fIPHYSFS_ERR_PERMISSION \fP\fP
Permission denied\&. 
.br
 
.TP
\fB\fIPHYSFS_ERR_NO_SPACE \fP\fP
No space (disk full, over quota, etc) 
.TP
\fB\fIPHYSFS_ERR_BAD_FILENAME \fP\fP
Filename is bogus/insecure\&. 
.br
 
.TP
\fB\fIPHYSFS_ERR_BUSY \fP\fP
Tried to modify a file the OS needs\&. 
.br
 
.TP
\fB\fIPHYSFS_ERR_DIR_NOT_EMPTY \fP\fP
Tried to delete dir with files in it\&. 
.TP
\fB\fIPHYSFS_ERR_OS_ERROR \fP\fP
Unspecified OS-level error\&. 
.br
 
.TP
\fB\fIPHYSFS_ERR_DUPLICATE \fP\fP
Duplicate entry\&. 
.br
 
.TP
\fB\fIPHYSFS_ERR_BAD_PASSWORD \fP\fP
Bad password\&. 
.br
 
.TP
\fB\fIPHYSFS_ERR_APP_CALLBACK \fP\fP
Application callback reported error\&. 
.br
 
.SS "enum \fBPHYSFS_FileType\fP"

.PP
Type of a File\&. Possible types of a file\&.
.PP
\fBSee also\fP
.RS 4
\fBPHYSFS_stat\fP 
.RE
.PP

.PP
\fBEnumerator\fP
.in +1c
.TP
\fB\fIPHYSFS_FILETYPE_REGULAR \fP\fP
a normal file 
.TP
\fB\fIPHYSFS_FILETYPE_DIRECTORY \fP\fP
a directory 
.TP
\fB\fIPHYSFS_FILETYPE_SYMLINK \fP\fP
a symlink 
.TP
\fB\fIPHYSFS_FILETYPE_OTHER \fP\fP
something completely different like a device 
.SH "Function Documentation"
.PP 
.SS "int PHYSFS_addToSearchPath (const char * newDir, int appendToPath)"

.PP
Add an archive or directory to the search path\&. 
.PP
\fBDeprecated\fP
.RS 4
As of PhysicsFS 2\&.0, use \fBPHYSFS_mount()\fP instead\&. This function just wraps it anyhow\&.
.RE
.PP
.PP
This function is equivalent to:
.PP
.PP
.nf
PHYSFS_mount(newDir, NULL, appendToPath);
.fi
.PP
.PP
You must use this and not PHYSFS_mount if binary compatibility with PhysicsFS 1\&.0 is important (which it may not be for many people)\&.
.PP
\fBSee also\fP
.RS 4
\fBPHYSFS_mount\fP 
.PP
\fBPHYSFS_removeFromSearchPath\fP 
.PP
\fBPHYSFS_getSearchPath\fP 
.RE
.PP

.SS "int PHYSFS_caseFold (const \fBPHYSFS_uint32\fP from, \fBPHYSFS_uint32\fP * to)"

.PP
'Fold' a Unicode codepoint to a lowercase equivalent\&. (This is for limited, hardcore use\&. If you don't immediately see a need for it, you can probably ignore this forever\&.)
.PP
This will convert a Unicode codepoint into its lowercase equivalent\&. Bogus codepoints and codepoints without a lowercase equivalent will be returned unconverted\&.
.PP
Note that you might get multiple codepoints in return! The German Eszett, for example, will fold down to two lowercase latin 's' codepoints\&. The theory is that if you fold two strings, one with an Eszett and one with 'SS' down, they will match\&.
.PP
\fBWarning\fP
.RS 4
Anyone that is a student of Unicode knows about the 'Turkish I' problem\&. This API does not handle it\&. Assume this one letter in all of Unicode will definitely fold sort of incorrectly\&. If you don't know what this is about, you can probably ignore this problem for most of the planet, but perfection is impossible\&.
.RE
.PP
\fBParameters\fP
.RS 4
\fIfrom\fP The codepoint to fold\&. 
.br
\fIto\fP Buffer to store the folded codepoint values into\&. This should point to space for at least 3 PHYSFS_uint32 slots\&. 
.RE
.PP
\fBReturns\fP
.RS 4
The number of codepoints the folding produced\&. Between 1 and 3\&. 
.RE
.PP

.SS "int PHYSFS_close (\fBPHYSFS_File\fP * handle)"

.PP
Close a PhysicsFS filehandle\&. This call is capable of failing if the operating system was buffering writes to the physical media, and, now forced to write those changes to physical media, can not store the data for some reason\&. In such a case, the filehandle stays open\&. A well-written program should ALWAYS check the return value from the close call in addition to every writing call!
.PP
\fBParameters\fP
.RS 4
\fIhandle\fP handle returned from PHYSFS_open*()\&. 
.RE
.PP
\fBReturns\fP
.RS 4
nonzero on success, zero on error\&. Use \fBPHYSFS_getLastErrorCode()\fP to obtain the specific error\&.
.RE
.PP
\fBSee also\fP
.RS 4
\fBPHYSFS_openRead\fP 
.PP
\fBPHYSFS_openWrite\fP 
.PP
\fBPHYSFS_openAppend\fP 
.RE
.PP

.SS "int PHYSFS_deinit (void)"

.PP
Deinitialize the PhysicsFS library\&. This closes any files opened via PhysicsFS, blanks the search/write paths, frees memory, and invalidates all of your file handles\&.
.PP
Note that this call can FAIL if there's a file open for writing that refuses to close (for example, the underlying operating system was buffering writes to network filesystem, and the fileserver has crashed, or a hard drive has failed, etc)\&. It is usually best to close all write handles yourself before calling this function, so that you can gracefully handle a specific failure\&.
.PP
Once successfully deinitialized, \fBPHYSFS_init()\fP can be called again to restart the subsystem\&. All default API states are restored at this point, with the exception of any custom allocator you might have specified, which survives between initializations\&.
.PP
\fBReturns\fP
.RS 4
nonzero on success, zero on error\&. Specifics of the error can be gleaned from \fBPHYSFS_getLastError()\fP\&. If failure, state of PhysFS is undefined, and probably badly screwed up\&.
.RE
.PP
\fBSee also\fP
.RS 4
\fBPHYSFS_init\fP 
.PP
\fBPHYSFS_isInit\fP 
.RE
.PP

.SS "int PHYSFS_delete (const char * filename)"

.PP
Delete a file or directory\&. (filename) is specified in platform-independent notation in relation to the write dir\&.
.PP
A directory must be empty before this call can delete it\&.
.PP
Deleting a symlink will remove the link, not what it points to, regardless of whether you 'permitSymLinks' or not\&.
.PP
So if you've got the write dir set to 'C:\\mygame\\writedir' and call PHYSFS_delete('downloads/maps/level1\&.map') then the file 'C:\\mygame\\writedir\\downloads\\maps\\level1\&.map' is removed from the physical filesystem, if it exists and the operating system permits the deletion\&.
.PP
Note that on Unix systems, deleting a file may be successful, but the actual file won't be removed until all processes that have an open filehandle to it (including your program) close their handles\&.
.PP
Chances are, the bits that make up the file still exist, they are just made available to be written over at a later point\&. Don't consider this a security method or anything\&. :)
.PP
\fBParameters\fP
.RS 4
\fIfilename\fP Filename to delete\&. 
.RE
.PP
\fBReturns\fP
.RS 4
nonzero on success, zero on error\&. Use \fBPHYSFS_getLastErrorCode()\fP to obtain the specific error\&. 
.RE
.PP

.SS "int PHYSFS_deregisterArchiver (const char * ext)"

.PP
Remove an archiver from the system\&. If for some reason, you only need your previously-registered archiver to live for a portion of your app's lifetime, you can remove it from the system once you're done with it through this function\&.
.PP
This fails if there are any archives still open that use this archiver\&.
.PP
This function can also remove internally-supplied archivers, like \&.zip support or whatnot\&. This could be useful in some situations, like disabling support for them outright or overriding them with your own implementation\&. Once an internal archiver is disabled like this, PhysicsFS provides no mechanism to recover them, short of calling \fBPHYSFS_deinit()\fP and \fBPHYSFS_init()\fP again\&.
.PP
\fBPHYSFS_deinit()\fP will automatically deregister all archivers, so you don't need to explicitly deregister yours if you otherwise shut down cleanly\&.
.PP
\fBParameters\fP
.RS 4
\fIext\fP Filename extension that the archiver handles\&. 
.RE
.PP
\fBReturns\fP
.RS 4
Zero on error, non-zero on success\&.
.RE
.PP
\fBSee also\fP
.RS 4
\fBPHYSFS_Archiver\fP 
.PP
\fBPHYSFS_registerArchiver\fP 
.RE
.PP

.SS "int PHYSFS_enumerate (const char * dir, \fBPHYSFS_EnumerateCallback\fP c, void * d)"

.PP
Get a file listing of a search path's directory, using an application-defined callback, with errors reported\&. Internally, \fBPHYSFS_enumerateFiles()\fP just calls this function and then builds a list before returning to the application, so functionality is identical except for how the information is represented to the application\&.
.PP
Unlike \fBPHYSFS_enumerateFiles()\fP, this function does not return an array\&. Rather, it calls a function specified by the application once per element of the search path:
.PP
.PP
.nf
static PHYSFS_EnumerateCallbackResult printDir(void *data, const char *origdir, const char *fname)
{
    printf(" * We've got [%s] in [%s]\&.\n", fname, origdir);
    return PHYSFS_ENUM_OK;  // give me more data, please\&.
}

// \&.\&.\&.
PHYSFS_enumerate("/some/path", printDir, NULL);
.fi
.PP
.PP
Items sent to the callback are not guaranteed to be in any order whatsoever\&. There is no sorting done at this level, and if you need that, you should probably use \fBPHYSFS_enumerateFiles()\fP instead, which guarantees alphabetical sorting\&. This form reports whatever is discovered in each archive before moving on to the next\&. Even within one archive, we can't guarantee what order it will discover data\&. \fIAny sorting you find in these callbacks is just pure luck\&. Do not rely on it\&.\fP As this walks the entire list of archives, you may receive duplicate filenames\&.
.PP
This API and the callbacks themselves are capable of reporting errors\&. Prior to this API, callbacks had to accept every enumerated item, even if they were only looking for a specific thing and wanted to stop after that, or had a serious error and couldn't alert anyone\&. Furthermore, if PhysicsFS itself had a problem (disk error or whatnot), it couldn't report it to the calling app, it would just have to skip items or stop enumerating outright, and the caller wouldn't know it had lost some data along the way\&.
.PP
Now the caller can be sure it got a complete data set, and its callback has control if it wants enumeration to stop early\&. See the documentation for PHYSFS_EnumerateCallback for details on how your callback should behave\&.
.PP
\fBParameters\fP
.RS 4
\fIdir\fP Directory, in platform-independent notation, to enumerate\&. 
.br
\fIc\fP Callback function to notify about search path elements\&. 
.br
\fId\fP Application-defined data passed to callback\&. Can be NULL\&. 
.RE
.PP
\fBReturns\fP
.RS 4
non-zero on success, zero on failure\&. Use \fBPHYSFS_getLastErrorCode()\fP to obtain the specific error\&. If the callback returns PHYSFS_ENUM_STOP to stop early, this will be considered success\&. Callbacks returning PHYSFS_ENUM_ERROR will make this function return zero and set the error code to PHYSFS_ERR_APP_CALLBACK\&.
.RE
.PP
\fBSee also\fP
.RS 4
\fBPHYSFS_EnumerateCallback\fP 
.PP
\fBPHYSFS_enumerateFiles\fP 
.RE
.PP

.SS "char ** PHYSFS_enumerateFiles (const char * dir)"

.PP
Get a file listing of a search path's directory\&. 
.PP
\fBWarning\fP
.RS 4
In PhysicsFS versions prior to 2\&.1, this function would return as many items as it could in the face of a failure condition (out of memory, disk i/o error, etc)\&. Since this meant apps couldn't distinguish between complete success and partial failure, and since the function could always return NULL to report catastrophic failures anyway, in PhysicsFS 2\&.1 this function's policy changed: it will either return a list of complete results or it will return NULL for any failure of any kind, so we can guarantee that the enumeration ran to completion and has no gaps in its results\&.
.RE
.PP
Matching directories are interpolated\&. That is, if 'C:\\mydir' is in the search path and contains a directory 'savegames' that contains 'x\&.sav', 'y\&.sav', and 'z\&.sav', and there is also a 'C:\\userdir' in the search path that has a 'savegames' subdirectory with 'w\&.sav', then the following code:
.PP
.PP
.nf
char **rc = PHYSFS_enumerateFiles("savegames");
char **i;

for (i = rc; *i != NULL; i++)
    printf(" * We've got [%s]\&.\n", *i);

PHYSFS_freeList(rc);
.fi
.PP
.PP
.\&.\&.will print:
.PP
.PP
.nf
* We've got [x\&.sav]\&.
* We've got [y\&.sav]\&.
* We've got [z\&.sav]\&.
* We've got [w\&.sav]\&..fi
.PP
.PP
Feel free to sort the list however you like\&. However, the returned data will always contain no duplicates, and will be always sorted in alphabetic (rather: case-sensitive Unicode) order for you\&.
.PP
Don't forget to call \fBPHYSFS_freeList()\fP with the return value from this function when you are done with it\&.
.PP
\fBParameters\fP
.RS 4
\fIdir\fP directory in platform-independent notation to enumerate\&. 
.RE
.PP
\fBReturns\fP
.RS 4
Null-terminated array of null-terminated strings, or NULL for failure cases\&.
.RE
.PP
\fBSee also\fP
.RS 4
\fBPHYSFS_enumerate\fP 
.RE
.PP

.SS "void PHYSFS_enumerateFilesCallback (const char * dir, \fBPHYSFS_EnumFilesCallback\fP c, void * d)"

.PP
Get a file listing of a search path's directory, using an application-defined callback\&. 
.PP
\fBDeprecated\fP
.RS 4
As of PhysicsFS 2\&.1, use \fBPHYSFS_enumerate()\fP instead\&. This function has no way to report errors (or to have the callback signal an error or request a stop), so if data will be lost, your callback has no way to direct the process, and your calling app has no way to know\&.
.RE
.PP
.PP
As of PhysicsFS 2\&.1, this function just wraps \fBPHYSFS_enumerate()\fP and ignores errors\&. Consider using \fBPHYSFS_enumerate()\fP or \fBPHYSFS_enumerateFiles()\fP instead\&.
.PP
\fBSee also\fP
.RS 4
\fBPHYSFS_enumerate\fP 
.PP
\fBPHYSFS_enumerateFiles\fP 
.PP
\fBPHYSFS_EnumFilesCallback\fP 
.RE
.PP

.SS "int PHYSFS_eof (\fBPHYSFS_File\fP * handle)"

.PP
Check for end-of-file state on a PhysicsFS filehandle\&. Determine if the end of file has been reached in a PhysicsFS filehandle\&.
.PP
\fBParameters\fP
.RS 4
\fIhandle\fP handle returned from \fBPHYSFS_openRead()\fP\&. 
.RE
.PP
\fBReturns\fP
.RS 4
nonzero if EOF, zero if not\&.
.RE
.PP
\fBSee also\fP
.RS 4
\fBPHYSFS_read\fP 
.PP
\fBPHYSFS_tell\fP 
.RE
.PP

.SS "int PHYSFS_exists (const char * fname)"

.PP
Determine if a file exists in the search path\&. Reports true if there is an entry anywhere in the search path by the name of (fname)\&.
.PP
Note that entries that are symlinks are ignored if PHYSFS_permitSymbolicLinks(1) hasn't been called, so you might end up further down in the search path than expected\&.
.PP
\fBParameters\fP
.RS 4
\fIfname\fP filename in platform-independent notation\&. 
.RE
.PP
\fBReturns\fP
.RS 4
non-zero if filename exists\&. zero otherwise\&. 
.RE
.PP

.SS "\fBPHYSFS_sint64\fP PHYSFS_fileLength (\fBPHYSFS_File\fP * handle)"

.PP
Get total length of a file in bytes\&. Note that if another process/thread is writing to this file at the same time, then the information this function supplies could be incorrect before you get it\&. Use with caution, or better yet, don't use at all\&.
.PP
\fBParameters\fP
.RS 4
\fIhandle\fP handle returned from PHYSFS_open*()\&. 
.RE
.PP
\fBReturns\fP
.RS 4
size in bytes of the file\&. -1 if can't be determined\&.
.RE
.PP
\fBSee also\fP
.RS 4
\fBPHYSFS_tell\fP 
.PP
\fBPHYSFS_seek\fP 
.RE
.PP

.SS "int PHYSFS_flush (\fBPHYSFS_File\fP * handle)"

.PP
Flush a buffered PhysicsFS file handle\&. For buffered files opened for writing, this will put the current contents of the buffer to disk and flag the buffer as empty if possible\&.
.PP
For buffered files opened for reading or unbuffered files, this is a safe no-op, and will report success\&.
.PP
\fBParameters\fP
.RS 4
\fIhandle\fP handle returned from PHYSFS_open*()\&. 
.RE
.PP
\fBReturns\fP
.RS 4
nonzero if successful, zero on error\&.
.RE
.PP
\fBSee also\fP
.RS 4
\fBPHYSFS_setBuffer\fP 
.PP
\fBPHYSFS_close\fP 
.RE
.PP

.SS "void PHYSFS_freeList (void * listVar)"

.PP
Deallocate resources of lists returned by PhysicsFS\&. Certain PhysicsFS functions return lists of information that are dynamically allocated\&. Use this function to free those resources\&.
.PP
It is safe to pass a NULL here, but doing so will cause a crash in versions before PhysicsFS 2\&.1\&.0\&.
.PP
\fBParameters\fP
.RS 4
\fIlistVar\fP List of information specified as freeable by this function\&. Passing NULL is safe; it is a valid no-op\&.
.RE
.PP
\fBSee also\fP
.RS 4
\fBPHYSFS_getCdRomDirs\fP 
.PP
\fBPHYSFS_enumerateFiles\fP 
.PP
\fBPHYSFS_getSearchPath\fP 
.RE
.PP

.SS "const \fBPHYSFS_Allocator\fP * PHYSFS_getAllocator (void)"

.PP
Discover the current allocator\&. (This is for limited, hardcore use\&. If you don't immediately see a need for it, you can probably ignore this forever\&.)
.PP
This function exposes the function pointers that make up the currently used allocator\&. This can be useful for apps that want to access PhysicsFS's internal, default allocation routines, as well as for external code that wants to share the same allocator, even if the application specified their own\&.
.PP
This call is only valid between \fBPHYSFS_init()\fP and \fBPHYSFS_deinit()\fP calls; it will return NULL if the library isn't initialized\&. As we can't guarantee the state of the internal allocators unless the library is initialized, you shouldn't use any allocator returned here after a call to \fBPHYSFS_deinit()\fP\&.
.PP
Do not call the returned allocator's Init() or Deinit() methods under any circumstances\&.
.PP
If you aren't immediately sure what to do with this function, you can safely ignore it altogether\&.
.PP
\fBReturns\fP
.RS 4
Current allocator, as set by \fBPHYSFS_setAllocator()\fP, or PhysicsFS's internal, default allocator if no application defined allocator is currently set\&. Will return NULL if the library is not initialized\&.
.RE
.PP
\fBSee also\fP
.RS 4
\fBPHYSFS_Allocator\fP 
.PP
\fBPHYSFS_setAllocator\fP 
.RE
.PP

.SS "const char * PHYSFS_getBaseDir (void)"

.PP
Get the path where the application resides\&. Helper function\&.
.PP
Get the 'base dir'\&. This is the directory where the application was run from, which is probably the installation directory, and may or may not be the process's current working directory\&.
.PP
You should probably use the base dir in your search path\&.
.PP
\fBWarning\fP
.RS 4
On most platforms, this is a directory; on Android, this gives you the path to the app's package (APK) file\&. As APK files are just \&.zip files, you can mount them in PhysicsFS like regular directories\&. You'll probably want to call PHYSFS_setRoot(basedir, '/assets') after mounting to make your app's actual data available directly without all the Android metadata and directory offset\&. Note that if you passed a NULL to \fBPHYSFS_init()\fP, you will not get the APK file here\&.
.RE
.PP
\fBReturns\fP
.RS 4
READ ONLY string of base dir in platform-dependent notation\&.
.RE
.PP
\fBSee also\fP
.RS 4
\fBPHYSFS_getPrefDir\fP 
.RE
.PP

.SS "char ** PHYSFS_getCdRomDirs (void)"

.PP
Get an array of paths to available CD-ROM drives\&. The dirs returned are platform-dependent ('D:\\' on Win32, '/cdrom' or
 whatnot on Unix)\&. Dirs are only returned if there is a disc ready and
 accessible in the drive\&. So if you've got two drives (D: and E:), and only
 E: has a disc in it, then that's all you get\&. If the user inserts a disc
 in D: and you call this function again, you get both drives\&. If, on a
 Unix box, the user unmounts a disc and remounts it elsewhere, the next
 call to this function will reflect that change\&.

This function refers to 'CD-ROM' media, but it really means 'inserted disc media,' such as DVD-ROM, HD-DVD, CDRW, and Blu-Ray discs\&. It looks for
 filesystems, and as such won't report an audio CD, unless there's a
 mounted filesystem track on it\&.

The returned value is an array of strings, with a NULL entry to signify the
 end of the list:

@code 
char **cds = PHYSFS_getCdRomDirs();
char **i;

for (i = cds; *i != NULL; i++)
    printf('cdrom dir [s] is available\&.
.br
", *i);
.PP
PHYSFS_freeList(cds); 
.PP
This call may block while drives spin up\&. Be forewarned\&.
.PP
When you are done with the returned information, you may dispose of the resources by calling \fBPHYSFS_freeList()\fP with the returned pointer\&.
.PP
\fBReturns\fP
.RS 4
Null-terminated array of null-terminated strings\&.
.RE
.PP
\fBSee also\fP
.RS 4
\fBPHYSFS_getCdRomDirsCallback\fP 
.RE
.PP

.SS "void PHYSFS_getCdRomDirsCallback (\fBPHYSFS_StringCallback\fP c, void * d)"

.PP
Enumerate CD-ROM directories, using an application-defined callback\&. Internally, \fBPHYSFS_getCdRomDirs()\fP just calls this function and then builds a list before returning to the application, so functionality is identical except for how the information is represented to the application\&.
.PP
Unlike \fBPHYSFS_getCdRomDirs()\fP, this function does not return an array\&. Rather, it calls a function specified by the application once per detected disc:
.PP
.PP
.nf
static void foundDisc(void *data, const char *cddir)
{
    printf("cdrom dir [%s] is available\&.\n", cddir);
}

// \&.\&.\&.
PHYSFS_getCdRomDirsCallback(foundDisc, NULL);
.fi
.PP
.PP
This call may block while drives spin up\&. Be forewarned\&.
.PP
\fBParameters\fP
.RS 4
\fIc\fP Callback function to notify about detected drives\&. 
.br
\fId\fP Application-defined data passed to callback\&. Can be NULL\&.
.RE
.PP
\fBSee also\fP
.RS 4
\fBPHYSFS_StringCallback\fP 
.PP
\fBPHYSFS_getCdRomDirs\fP 
.RE
.PP

.SS "const char * PHYSFS_getDirSeparator (void)"

.PP
Get platform-dependent dir separator string\&. This returns '\\\\' on win32, '/' on Unix, and ':" on MacOS\&. It may be more than one character, depending on the platform, and your code should take that into account\&. Note that this is only useful for setting up the search/write paths, since access into those dirs always use '/' (platform-independent notation) to separate directories\&. This is also handy for getting platform-independent access when using stdio calls\&.
.PP
\fBReturns\fP
.RS 4
READ ONLY null-terminated string of platform's dir separator\&. 
.RE
.PP

.SS "const char * PHYSFS_getErrorByCode (\fBPHYSFS_ErrorCode\fP code)"

.PP
Get human-readable description string for a given error code\&. Get a static string, in UTF-8 format, that represents an English description of a given error code\&.
.PP
This string is guaranteed to never change (although we may add new strings for new error codes in later versions of PhysicsFS), so you can use it for keying a localization dictionary\&.
.PP
It is safe to call this function at anytime, even before \fBPHYSFS_init()\fP\&.
.PP
These strings are meant to be passed on directly to the user\&. Generally, applications should only concern themselves with whether a given function failed, but not care about the specifics much\&.
.PP
Do not attempt to free the returned strings; they are read-only and you don't own their memory pages\&.
.PP
\fBParameters\fP
.RS 4
\fIcode\fP Error code to convert to a string\&. 
.RE
.PP
\fBReturns\fP
.RS 4
READ ONLY string of requested error message, NULL if this is not a valid PhysicsFS error code\&. Always check for NULL if you might be looking up an error code that didn't exist in an earlier version of PhysicsFS\&.
.RE
.PP
\fBSee also\fP
.RS 4
\fBPHYSFS_getLastErrorCode\fP 
.RE
.PP

.SS "const char * PHYSFS_getLastError (void)"

.PP
Get human-readable error information\&. 
.PP
\fBDeprecated\fP
.RS 4
Use \fBPHYSFS_getLastErrorCode()\fP and \fBPHYSFS_getErrorByCode()\fP instead\&.
.RE
.PP
.PP
\fBWarning\fP
.RS 4
As of PhysicsFS 2\&.1, this function has been nerfed\&. Before PhysicsFS 2\&.1, this function was the only way to get error details beyond a given function's basic return value\&. This was meant to be a human-readable string in one of several languages, and was not useful for application parsing\&. This was a problem, because the developer and not the user chose the language at compile time, and the PhysicsFS maintainers had to (poorly) maintain a significant amount of localization work\&. The app couldn't parse the strings, even if they counted on a specific language, since some were dynamically generated\&. In 2\&.1 and later, this always returns a static string in English; you may use it as a key string for your own localizations if you like, as we'll promise not to change existing error strings\&. Also, if your application wants to look at specific errors, we now offer a better option: use \fBPHYSFS_getLastErrorCode()\fP instead\&.
.RE
.PP
Get the last PhysicsFS error message as a human-readable, null-terminated string\&. This will return NULL if there's been no error since the last call to this function\&. The pointer returned by this call points to an internal buffer\&. Each thread has a unique error state associated with it, but each time a new error message is set, it will overwrite the previous one associated with that thread\&. It is safe to call this function at anytime, even before \fBPHYSFS_init()\fP\&.
.PP
\fBPHYSFS_getLastError()\fP and \fBPHYSFS_getLastErrorCode()\fP both reset the same thread-specific error state\&. Calling one will wipe out the other's data\&. If you need both, call \fBPHYSFS_getLastErrorCode()\fP, then pass that value to \fBPHYSFS_getErrorByCode()\fP\&.
.PP
As of PhysicsFS 2\&.1, this function only presents text in the English language, but the strings are static, so you can use them as keys into your own localization dictionary\&. These strings are meant to be passed on directly to the user\&.
.PP
Generally, applications should only concern themselves with whether a given function failed; however, if your code require more specifics, you should use \fBPHYSFS_getLastErrorCode()\fP instead of this function\&.
.PP
\fBReturns\fP
.RS 4
READ ONLY string of last error message\&.
.RE
.PP
\fBSee also\fP
.RS 4
\fBPHYSFS_getLastErrorCode\fP 
.PP
\fBPHYSFS_getErrorByCode\fP 
.RE
.PP

.SS "\fBPHYSFS_ErrorCode\fP PHYSFS_getLastErrorCode (void)"

.PP
Get machine-readable error information\&. Get the last PhysicsFS error message as an integer value\&. This will return PHYSFS_ERR_OK if there's been no error since the last call to this function\&. Each thread has a unique error state associated with it, but each time a new error message is set, it will overwrite the previous one associated with that thread\&. It is safe to call this function at anytime, even before \fBPHYSFS_init()\fP\&.
.PP
\fBPHYSFS_getLastError()\fP and \fBPHYSFS_getLastErrorCode()\fP both reset the same thread-specific error state\&. Calling one will wipe out the other's data\&. If you need both, call \fBPHYSFS_getLastErrorCode()\fP, then pass that value to \fBPHYSFS_getErrorByCode()\fP\&.
.PP
Generally, applications should only concern themselves with whether a given function failed; however, if you require more specifics, you can try this function to glean information, if there's some specific problem you're expecting and plan to handle\&. But with most things that involve file systems, the best course of action is usually to give up, report the problem to the user, and let them figure out what should be done about it\&. For that, you might prefer \fBPHYSFS_getErrorByCode()\fP instead\&.
.PP
\fBReturns\fP
.RS 4
Enumeration value that represents last reported error\&.
.RE
.PP
\fBSee also\fP
.RS 4
\fBPHYSFS_getErrorByCode\fP 
.RE
.PP

.SS "\fBPHYSFS_sint64\fP PHYSFS_getLastModTime (const char * filename)"

.PP
Get the last modification time of a file\&. 
.PP
\fBDeprecated\fP
.RS 4
As of PhysicsFS 2\&.1, use \fBPHYSFS_stat()\fP instead\&. This function just wraps it anyhow\&.
.RE
.PP
.PP
The modtime is returned as a number of seconds since the Unix epoch (midnight, Jan 1, 1970)\&. The exact derivation and accuracy of this time depends on the particular archiver\&. If there is no reasonable way to obtain this information for a particular archiver, or there was some sort of error, this function returns (-1)\&.
.PP
You must use this and not \fBPHYSFS_stat()\fP if binary compatibility with PhysicsFS 2\&.0 is important (which it may not be for many people)\&.
.PP
\fBParameters\fP
.RS 4
\fIfilename\fP filename to check, in platform-independent notation\&. 
.RE
.PP
\fBReturns\fP
.RS 4
last modified time of the file\&. -1 if it can't be determined\&.
.RE
.PP
\fBSee also\fP
.RS 4
\fBPHYSFS_stat\fP 
.RE
.PP

.SS "void PHYSFS_getLinkedVersion (\fBPHYSFS_Version\fP * ver)"

.PP
Get the version of PhysicsFS that is linked against your program\&. If you are using a shared library (DLL) version of PhysFS, then it is possible that it will be different than the version you compiled against\&.
.PP
This is a real function; the macro PHYSFS_VERSION tells you what version of PhysFS you compiled against:
.PP
.PP
.nf
PHYSFS_Version compiled;
PHYSFS_Version linked;

PHYSFS_VERSION(&compiled);
PHYSFS_getLinkedVersion(&linked);
printf("We compiled against PhysFS version %d\&.%d\&.%d \&.\&.\&.\n",
          compiled\&.major, compiled\&.minor, compiled\&.patch);
printf("But we linked against PhysFS version %d\&.%d\&.%d\&.\n",
          linked\&.major, linked\&.minor, linked\&.patch);
.fi
.PP
.PP
This function may be called safely at any time, even before \fBPHYSFS_init()\fP\&.
.PP
\fBSee also\fP
.RS 4
\fBPHYSFS_VERSION\fP 
.RE
.PP

.SS "int PHYSFS_getMountPoint (const char * dir)"

.PP
Determine a mounted archive's mountpoint\&. You give this function the name of an archive or dir you successfully added to the search path, and it reports the location in the interpolated tree where it is mounted\&. Files mounted with a NULL mountpoint or through \fBPHYSFS_addToSearchPath()\fP will report '/'\&. The return value is READ ONLY and valid until the archive is removed from the search path\&.
.PP
\fBParameters\fP
.RS 4
\fIdir\fP directory or archive previously added to the path, in platform-dependent notation\&. This must match the string used when adding, even if your string would also reference the same file with a different string of characters\&. 
.RE
.PP
\fBReturns\fP
.RS 4
READ-ONLY string of mount point if added to path, NULL on failure (bogus archive, etc)\&. Use \fBPHYSFS_getLastErrorCode()\fP to obtain the specific error\&.
.RE
.PP
\fBSee also\fP
.RS 4
\fBPHYSFS_removeFromSearchPath\fP 
.PP
\fBPHYSFS_getSearchPath\fP 
.PP
\fBPHYSFS_getMountPoint\fP 
.RE
.PP

.SS "const char * PHYSFS_getPrefDir (const char * org, const char * app)"

.PP
Get the user-and-app-specific path where files can be written\&. Helper function\&.
.PP
Get the 'pref dir'\&. This is meant to be where users can write personal files (preferences and save games, etc) that are specific to your application\&. This directory is unique per user, per application\&.
.PP
This function will decide the appropriate location in the native filesystem, create the directory if necessary, and return a string in platform-dependent notation, suitable for passing to \fBPHYSFS_setWriteDir()\fP\&.
.PP
On Windows, this might look like: 'C:\\\\Users\\\\bob\\\\AppData\\\\Roaming\\\\My Company\\\\My Program Name'
.PP
On Linux, this might look like: '/home/bob/\&.local/share/My Program Name'
.PP
On Mac OS X, this might look like: '/Users/bob/Library/Application Support/My Program Name'
.PP
(etc\&.)
.PP
You should probably use the pref dir for your write dir, and also put it near the beginning of your search path\&. Older versions of PhysicsFS offered only \fBPHYSFS_getUserDir()\fP and left you to figure out where the files should go under that tree\&. This finds the correct location for whatever platform, which not only changes between operating systems, but also versions of the same operating system\&.
.PP
You specify the name of your organization (if it's not a real organization, your name or an Internet domain you own might do) and the name of your application\&. These should be proper names\&.
.PP
Both the (org) and (app) strings may become part of a directory name, so please follow these rules:
.PP
.IP "\(bu" 2
Try to use the same org string (including case-sensitivity) for all your applications that use this function\&.
.IP "\(bu" 2
Always use a unique app string for each one, and make sure it never changes for an app once you've decided on it\&.
.IP "\(bu" 2
Unicode characters are legal, as long as it's UTF-8 encoded, but\&.\&.\&.
.IP "\(bu" 2
\&.\&.\&.only use letters, numbers, and spaces\&. Avoid punctuation like 'Game Name 2: Bad Guy's Revenge!' \&.\&.\&. 'Game Name 2' is sufficient\&.
.PP
.PP
The pointer returned by this function remains valid until you call this function again, or call \fBPHYSFS_deinit()\fP\&. This is not necessarily a fast call, though, so you should call this once at startup and copy the string if you need it\&.
.PP
You should assume the path returned by this function is the only safe place to write files (and that \fBPHYSFS_getUserDir()\fP and \fBPHYSFS_getBaseDir()\fP, while they might be writable, or even parents of the returned path, aren't where you should be writing things)\&.
.PP
\fBParameters\fP
.RS 4
\fIorg\fP The name of your organization\&. 
.br
\fIapp\fP The name of your application\&. 
.RE
.PP
\fBReturns\fP
.RS 4
READ ONLY string of user dir in platform-dependent notation\&. NULL if there's a problem (creating directory failed, etc)\&.
.RE
.PP
\fBSee also\fP
.RS 4
\fBPHYSFS_getBaseDir\fP 
.PP
\fBPHYSFS_getUserDir\fP 
.RE
.PP

.SS "const char * PHYSFS_getRealDir (const char * filename)"

.PP
Figure out where in the search path a file resides\&. The file is specified in platform-independent notation\&. The returned filename will be the element of the search path where the file was found, which may be a directory, or an archive\&. Even if there are multiple matches in different parts of the search path, only the first one found is used, just like when opening a file\&.
.PP
So, if you look for 'maps/level1\&.map', and C:\\mygame is in your search path and C:\\mygame\\maps\\level1\&.map exists, then 'C:\\mygame' is returned\&.
.PP
If a any part of a match is a symbolic link, and you've not explicitly permitted symlinks, then it will be ignored, and the search for a match will continue\&.
.PP
If you specify a fake directory that only exists as a mount point, it'll be associated with the first archive mounted there, even though that directory isn't necessarily contained in a real archive\&.
.PP
\fBWarning\fP
.RS 4
This will return NULL if there is no real directory associated with (filename)\&. Specifically, \fBPHYSFS_mountIo()\fP, \fBPHYSFS_mountMemory()\fP, and \fBPHYSFS_mountHandle()\fP will return NULL even if the filename is found in the search path\&. Plan accordingly\&.
.RE
.PP
\fBParameters\fP
.RS 4
\fIfilename\fP file to look for\&. 
.RE
.PP
\fBReturns\fP
.RS 4
READ ONLY string of element of search path containing the the file in question\&. NULL if not found\&. 
.RE
.PP

.SS "char ** PHYSFS_getSearchPath (void)"

.PP
Get the current search path\&. The default search path is an empty list\&.
.PP
The returned value is an array of strings, with a NULL entry to signify the end of the list:
.PP
.PP
.nf
char **i;

for (i = PHYSFS_getSearchPath(); *i != NULL; i++)
    printf("[%s] is in the search path\&.\n", *i);
.fi
.PP
.PP
When you are done with the returned information, you may dispose of the resources by calling \fBPHYSFS_freeList()\fP with the returned pointer\&.
.PP
\fBReturns\fP
.RS 4
Null-terminated array of null-terminated strings\&. NULL if there was a problem (read: OUT OF MEMORY)\&.
.RE
.PP
\fBSee also\fP
.RS 4
\fBPHYSFS_getSearchPathCallback\fP 
.PP
\fBPHYSFS_addToSearchPath\fP 
.PP
\fBPHYSFS_removeFromSearchPath\fP 
.RE
.PP

.SS "void PHYSFS_getSearchPathCallback (\fBPHYSFS_StringCallback\fP c, void * d)"

.PP
Enumerate the search path, using an application-defined callback\&. Internally, \fBPHYSFS_getSearchPath()\fP just calls this function and then builds a list before returning to the application, so functionality is identical except for how the information is represented to the application\&.
.PP
Unlike \fBPHYSFS_getSearchPath()\fP, this function does not return an array\&. Rather, it calls a function specified by the application once per element of the search path:
.PP
.PP
.nf
static void printSearchPath(void *data, const char *pathItem)
{
    printf("[%s] is in the search path\&.\n", pathItem);
}

// \&.\&.\&.
PHYSFS_getSearchPathCallback(printSearchPath, NULL);
.fi
.PP
.PP
Elements of the search path are reported in order search priority, so the first archive/dir that would be examined when looking for a file is the first element passed through the callback\&.
.PP
\fBParameters\fP
.RS 4
\fIc\fP Callback function to notify about search path elements\&. 
.br
\fId\fP Application-defined data passed to callback\&. Can be NULL\&.
.RE
.PP
\fBSee also\fP
.RS 4
\fBPHYSFS_StringCallback\fP 
.PP
\fBPHYSFS_getSearchPath\fP 
.RE
.PP

.SS "const char * PHYSFS_getUserDir (void)"

.PP
Get the path where user's home directory resides\&. 
.PP
\fBDeprecated\fP
.RS 4
As of PhysicsFS 2\&.1, you probably want \fBPHYSFS_getPrefDir()\fP\&.
.RE
.PP
.PP
Helper function\&.
.PP
Get the 'user dir'\&. This is meant to be a suggestion of where a specific user of the system can store files\&. On Unix, this is her home directory\&. On systems with no concept of multiple home directories (MacOS, win95), this will default to something like 'C:\\mybasedir\\users\\username' where 'username' will either be the login name, or 'default' if the platform doesn't support multiple users, either\&.
.PP
\fBReturns\fP
.RS 4
READ ONLY string of user dir in platform-dependent notation\&.
.RE
.PP
\fBSee also\fP
.RS 4
\fBPHYSFS_getBaseDir\fP 
.PP
\fBPHYSFS_getPrefDir\fP 
.RE
.PP

.SS "const char * PHYSFS_getWriteDir (void)"

.PP
Get path where PhysicsFS will allow file writing\&. Get the current write dir\&. The default write dir is NULL\&.
.PP
\fBReturns\fP
.RS 4
READ ONLY string of write dir in platform-dependent notation, OR NULL IF NO WRITE PATH IS CURRENTLY SET\&.
.RE
.PP
\fBSee also\fP
.RS 4
\fBPHYSFS_setWriteDir\fP 
.RE
.PP

.SS "int PHYSFS_init (const char * argv0)"

.PP
Initialize the PhysicsFS library\&. This must be called before any other PhysicsFS function\&.
.PP
This should be called prior to any attempts to change your process's current working directory\&.
.PP
\fBWarning\fP
.RS 4
On Android, argv0 should be a non-NULL pointer to a PHYSFS_AndroidInit struct\&. This struct must hold a valid JNIEnv * and a JNI jobject of a Context (either the application context or the current Activity is fine)\&. Both are cast to a void * so we don't need jni\&.h included wherever \fBphysfs\&.h\fP is\&. PhysicsFS uses these objects to query some system details\&. PhysicsFS does not hold a reference to the JNIEnv or Context past the call to \fBPHYSFS_init()\fP\&. If you pass a NULL here, PHYSFS_init can still succeed, but \fBPHYSFS_getBaseDir()\fP and \fBPHYSFS_getPrefDir()\fP will be incorrect\&.
.RE
.PP
\fBParameters\fP
.RS 4
\fIargv0\fP the argv[0] string passed to your program's mainline\&. This may be NULL on most platforms (such as ones without a standard main() function), but you should always try to pass something in here\&. Many Unix-like systems \fIneed\fP to pass argv[0] from main() in here\&. See warning about Android, too! 
.RE
.PP
\fBReturns\fP
.RS 4
nonzero on success, zero on error\&. Specifics of the error can be gleaned from \fBPHYSFS_getLastError()\fP\&.
.RE
.PP
\fBSee also\fP
.RS 4
\fBPHYSFS_deinit\fP 
.PP
\fBPHYSFS_isInit\fP 
.RE
.PP

.SS "int PHYSFS_isDirectory (const char * fname)"

.PP
Determine if a file in the search path is really a directory\&. 
.PP
\fBDeprecated\fP
.RS 4
As of PhysicsFS 2\&.1, use \fBPHYSFS_stat()\fP instead\&. This function just wraps it anyhow\&.
.RE
.PP
.PP
Determine if the first occurence of (fname) in the search path is really a directory entry\&.
.PP
Note that entries that are symlinks are ignored if PHYSFS_permitSymbolicLinks(1) hasn't been called, so you might end up further down in the search path than expected\&.
.PP
\fBParameters\fP
.RS 4
\fIfname\fP filename in platform-independent notation\&. 
.RE
.PP
\fBReturns\fP
.RS 4
non-zero if filename exists and is a directory\&. zero otherwise\&.
.RE
.PP
\fBSee also\fP
.RS 4
\fBPHYSFS_stat\fP 
.PP
\fBPHYSFS_exists\fP 
.RE
.PP

.SS "int PHYSFS_isInit (void)"

.PP
Determine if the PhysicsFS library is initialized\&. Once \fBPHYSFS_init()\fP returns successfully, this will return non-zero\&. Before a successful \fBPHYSFS_init()\fP and after \fBPHYSFS_deinit()\fP returns successfully, this will return zero\&. This function is safe to call at any time\&.
.PP
\fBReturns\fP
.RS 4
non-zero if library is initialized, zero if library is not\&.
.RE
.PP
\fBSee also\fP
.RS 4
\fBPHYSFS_init\fP 
.PP
\fBPHYSFS_deinit\fP 
.RE
.PP

.SS "int PHYSFS_isSymbolicLink (const char * fname)"

.PP
Determine if a file in the search path is really a symbolic link\&. 
.PP
\fBDeprecated\fP
.RS 4
As of PhysicsFS 2\&.1, use \fBPHYSFS_stat()\fP instead\&. This function just wraps it anyhow\&.
.RE
.PP
.PP
Determine if the first occurence of (fname) in the search path is really a symbolic link\&.
.PP
Note that entries that are symlinks are ignored if PHYSFS_permitSymbolicLinks(1) hasn't been called, and as such, this function will always return 0 in that case\&.
.PP
\fBParameters\fP
.RS 4
\fIfname\fP filename in platform-independent notation\&. 
.RE
.PP
\fBReturns\fP
.RS 4
non-zero if filename exists and is a symlink\&. zero otherwise\&.
.RE
.PP
\fBSee also\fP
.RS 4
\fBPHYSFS_stat\fP 
.PP
\fBPHYSFS_exists\fP 
.RE
.PP

.SS "int PHYSFS_mkdir (const char * dirName)"

.PP
Create a directory\&. This is specified in platform-independent notation in relation to the write dir\&. All missing parent directories are also created if they don't exist\&.
.PP
So if you've got the write dir set to 'C:\\mygame\\writedir' and call PHYSFS_mkdir('downloads/maps') then the directories 'C:\\mygame\\writedir\\downloads' and 'C:\\mygame\\writedir\\downloads\\maps' will be created if possible\&. If the creation of 'maps' fails after we have successfully created 'downloads', then the function leaves the created directory behind and reports failure\&.
.PP
\fBParameters\fP
.RS 4
\fIdirName\fP New dir to create\&. 
.RE
.PP
\fBReturns\fP
.RS 4
nonzero on success, zero on error\&. Use \fBPHYSFS_getLastErrorCode()\fP to obtain the specific error\&.
.RE
.PP
\fBSee also\fP
.RS 4
\fBPHYSFS_delete\fP 
.RE
.PP

.SS "int PHYSFS_mount (const char * newDir, const char * mountPoint, int appendToPath)"

.PP
Add an archive or directory to the search path\&. If this is a duplicate, the entry is not added again, even though the function succeeds\&. You may not add the same archive to two different mountpoints: duplicate checking is done against the archive and not the mountpoint\&.
.PP
When you mount an archive, it is added to a virtual file system\&.\&.\&.all files in all of the archives are interpolated into a single hierachical file tree\&. Two archives mounted at the same place (or an archive with files overlapping another mountpoint) may have overlapping files: in such a case, the file earliest in the search path is selected, and the other files are inaccessible to the application\&. This allows archives to be used to override previous revisions; you can use the mounting mechanism to place archives at a specific point in the file tree and prevent overlap; this is useful for downloadable mods that might trample over application data or each other, for example\&.
.PP
The mountpoint does not need to exist prior to mounting, which is different than those familiar with the Unix concept of 'mounting' may expect\&. As well, more than one archive can be mounted to the same mountpoint, or mountpoints and archive contents can overlap\&.\&.\&.the interpolation mechanism still functions as usual\&.
.PP
Specifying a symbolic link to an archive or directory is allowed here, regardless of the state of \fBPHYSFS_permitSymbolicLinks()\fP\&. That function only deals with symlinks inside the mounted directory or archive\&.
.PP
\fBParameters\fP
.RS 4
\fInewDir\fP directory or archive to add to the path, in platform-dependent notation\&. 
.br
\fImountPoint\fP Location in the interpolated tree that this archive will be 'mounted', in platform-independent notation\&. NULL or '' is equivalent to '/'\&. 
.br
\fIappendToPath\fP nonzero to append to search path, zero to prepend\&. 
.RE
.PP
\fBReturns\fP
.RS 4
nonzero if added to path, zero on failure (bogus archive, dir missing, etc)\&. Use \fBPHYSFS_getLastErrorCode()\fP to obtain the specific error\&.
.RE
.PP
\fBSee also\fP
.RS 4
\fBPHYSFS_removeFromSearchPath\fP 
.PP
\fBPHYSFS_getSearchPath\fP 
.PP
\fBPHYSFS_getMountPoint\fP 
.PP
\fBPHYSFS_mountIo\fP 
.RE
.PP

.SS "int PHYSFS_mountHandle (\fBPHYSFS_File\fP * file, const char * newDir, const char * mountPoint, int appendToPath)"

.PP
Add an archive, contained in a \fBPHYSFS_File\fP handle, to the search path\&. 
.PP
\fBWarning\fP
.RS 4
Unless you have some special, low-level need, you should be using \fBPHYSFS_mount()\fP instead of this\&.
.PP
Archives-in-archives may be very slow! While a \fBPHYSFS_File\fP can seek even when the data is compressed, it may do so by rewinding to the start and decompressing everything before the seek point\&. Normal archive usage may do a lot of seeking behind the scenes\&. As such, you might find normal archive usage extremely painful if mounted this way\&. Plan accordingly: if you, say, have a self-extracting \&.zip file, and want to mount something in it, compress the contents of the inner archive and make sure the outer \&.zip file doesn't compress the inner archive too\&.
.RE
.PP
This function operates just like \fBPHYSFS_mount()\fP, but takes a \fBPHYSFS_File\fP handle instead of a pathname\&. This handle contains all the data of the archive, and is used instead of a real file in the physical filesystem\&. The \fBPHYSFS_File\fP may be backed by a real file in the physical filesystem, but isn't necessarily\&. The most popular use for this is likely to mount archives stored inside other archives\&.
.PP
(newDir) must be a unique string to identify this archive\&. It is used to optimize archiver selection (if you name it XXXXX\&.zip, we might try the ZIP archiver first, for example, or directly choose an archiver that can only trust the data is valid by filename extension)\&. It doesn't need to refer to a real file at all\&. If the filename extension isn't helpful, the system will try every archiver until one works or none of them do\&. This filename must be unique, as the system won't allow you to have two archives with the same name\&.
.PP
(file) must remain until the archive is unmounted\&. When the archive is unmounted, the system will call PHYSFS_close(file)\&. If you need this handle to survive, you will have to wrap this in a \fBPHYSFS_Io\fP and use \fBPHYSFS_mountIo()\fP instead\&.
.PP
If this function fails, PHYSFS_close(file) is not called\&.
.PP
\fBParameters\fP
.RS 4
\fIfile\fP The \fBPHYSFS_File\fP handle containing archive data\&. 
.br
\fInewDir\fP Filename that can represent this stream\&. 
.br
\fImountPoint\fP Location in the interpolated tree that this archive will be 'mounted', in platform-independent notation\&. NULL or '' is equivalent to '/'\&. 
.br
\fIappendToPath\fP nonzero to append to search path, zero to prepend\&. 
.RE
.PP
\fBReturns\fP
.RS 4
nonzero if added to path, zero on failure (bogus archive, etc)\&. Use \fBPHYSFS_getLastErrorCode()\fP to obtain the specific error\&.
.RE
.PP
\fBSee also\fP
.RS 4
\fBPHYSFS_unmount\fP 
.PP
\fBPHYSFS_getSearchPath\fP 
.PP
\fBPHYSFS_getMountPoint\fP 
.RE
.PP

.SS "int PHYSFS_mountIo (\fBPHYSFS_Io\fP * io, const char * newDir, const char * mountPoint, int appendToPath)"

.PP
Add an archive, built on a \fBPHYSFS_Io\fP, to the search path\&. 
.PP
\fBWarning\fP
.RS 4
Unless you have some special, low-level need, you should be using \fBPHYSFS_mount()\fP instead of this\&.
.RE
.PP
This function operates just like \fBPHYSFS_mount()\fP, but takes a \fBPHYSFS_Io\fP instead of a pathname\&. Behind the scenes, \fBPHYSFS_mount()\fP calls this function with a physical-filesystem-based \fBPHYSFS_Io\fP\&.
.PP
(newDir) must be a unique string to identify this archive\&. It is used to optimize archiver selection (if you name it XXXXX\&.zip, we might try the ZIP archiver first, for example, or directly choose an archiver that can only trust the data is valid by filename extension)\&. It doesn't need to refer to a real file at all\&. If the filename extension isn't helpful, the system will try every archiver until one works or none of them do\&. This filename must be unique, as the system won't allow you to have two archives with the same name\&.
.PP
(io) must remain until the archive is unmounted\&. When the archive is unmounted, the system will call (io)->destroy(io), which will give you a chance to free your resources\&.
.PP
If this function fails, (io)->destroy(io) is not called\&.
.PP
\fBParameters\fP
.RS 4
\fIio\fP i/o instance for archive to add to the path\&. 
.br
\fInewDir\fP Filename that can represent this stream\&. 
.br
\fImountPoint\fP Location in the interpolated tree that this archive will be 'mounted', in platform-independent notation\&. NULL or '' is equivalent to '/'\&. 
.br
\fIappendToPath\fP nonzero to append to search path, zero to prepend\&. 
.RE
.PP
\fBReturns\fP
.RS 4
nonzero if added to path, zero on failure (bogus archive, stream i/o issue, etc)\&. Use \fBPHYSFS_getLastErrorCode()\fP to obtain the specific error\&.
.RE
.PP
\fBSee also\fP
.RS 4
\fBPHYSFS_unmount\fP 
.PP
\fBPHYSFS_getSearchPath\fP 
.PP
\fBPHYSFS_getMountPoint\fP 
.RE
.PP

.SS "int PHYSFS_mountMemory (const void * buf, \fBPHYSFS_uint64\fP len, void(*)(void *) del, const char * newDir, const char * mountPoint, int appendToPath)"

.PP
Add an archive, contained in a memory buffer, to the search path\&. 
.PP
\fBWarning\fP
.RS 4
Unless you have some special, low-level need, you should be using \fBPHYSFS_mount()\fP instead of this\&.
.RE
.PP
This function operates just like \fBPHYSFS_mount()\fP, but takes a memory buffer instead of a pathname\&. This buffer contains all the data of the archive, and is used instead of a real file in the physical filesystem\&.
.PP
(newDir) must be a unique string to identify this archive\&. It is used to optimize archiver selection (if you name it XXXXX\&.zip, we might try the ZIP archiver first, for example, or directly choose an archiver that can only trust the data is valid by filename extension)\&. It doesn't need to refer to a real file at all\&. If the filename extension isn't helpful, the system will try every archiver until one works or none of them do\&. This filename must be unique, as the system won't allow you to have two archives with the same name\&.
.PP
(ptr) must remain until the archive is unmounted\&. When the archive is unmounted, the system will call (del)(ptr), which will notify you that the system is done with the buffer, and give you a chance to free your resources\&. (del) can be NULL, in which case the system will make no attempt to free the buffer\&.
.PP
If this function fails, (del) is not called\&.
.PP
\fBParameters\fP
.RS 4
\fIbuf\fP Address of the memory buffer containing the archive data\&. 
.br
\fIlen\fP Size of memory buffer, in bytes\&. 
.br
\fIdel\fP A callback that triggers upon unmount\&. Can be NULL\&. 
.br
\fInewDir\fP Filename that can represent this stream\&. 
.br
\fImountPoint\fP Location in the interpolated tree that this archive will be 'mounted', in platform-independent notation\&. NULL or '' is equivalent to '/'\&. 
.br
\fIappendToPath\fP nonzero to append to search path, zero to prepend\&. 
.RE
.PP
\fBReturns\fP
.RS 4
nonzero if added to path, zero on failure (bogus archive, etc)\&. Use \fBPHYSFS_getLastErrorCode()\fP to obtain the specific error\&.
.RE
.PP
\fBSee also\fP
.RS 4
\fBPHYSFS_unmount\fP 
.PP
\fBPHYSFS_getSearchPath\fP 
.PP
\fBPHYSFS_getMountPoint\fP 
.RE
.PP

.SS "\fBPHYSFS_File\fP * PHYSFS_openAppend (const char * filename)"

.PP
Open a file for appending\&. Open a file for writing, in platform-independent notation and in relation to the write dir as the root of the writable filesystem\&. The specified file is created if it doesn't exist\&. If it does exist, the writing offset is set to the end of the file, so the first write will be the byte after the end\&.
.PP
Note that entries that are symlinks are ignored if PHYSFS_permitSymbolicLinks(1) hasn't been called, and opening a symlink with this function will fail in such a case\&.
.PP
\fBParameters\fP
.RS 4
\fIfilename\fP File to open\&. 
.RE
.PP
\fBReturns\fP
.RS 4
A valid PhysicsFS filehandle on success, NULL on error\&. Use \fBPHYSFS_getLastErrorCode()\fP to obtain the specific error\&.
.RE
.PP
\fBSee also\fP
.RS 4
\fBPHYSFS_openRead\fP 
.PP
\fBPHYSFS_openWrite\fP 
.PP
\fBPHYSFS_write\fP 
.PP
\fBPHYSFS_close\fP 
.RE
.PP

.SS "\fBPHYSFS_File\fP * PHYSFS_openRead (const char * filename)"

.PP
Open a file for reading\&. Open a file for reading, in platform-independent notation\&. The search path is checked one at a time until a matching file is found, in which case an abstract filehandle is associated with it, and reading may be done\&. The reading offset is set to the first byte of the file\&.
.PP
Note that entries that are symlinks are ignored if PHYSFS_permitSymbolicLinks(1) hasn't been called, and opening a symlink with this function will fail in such a case\&.
.PP
\fBParameters\fP
.RS 4
\fIfilename\fP File to open\&. 
.RE
.PP
\fBReturns\fP
.RS 4
A valid PhysicsFS filehandle on success, NULL on error\&. Use \fBPHYSFS_getLastErrorCode()\fP to obtain the specific error\&.
.RE
.PP
\fBSee also\fP
.RS 4
\fBPHYSFS_openWrite\fP 
.PP
\fBPHYSFS_openAppend\fP 
.PP
\fBPHYSFS_read\fP 
.PP
\fBPHYSFS_close\fP 
.RE
.PP

.SS "\fBPHYSFS_File\fP * PHYSFS_openWrite (const char * filename)"

.PP
Open a file for writing\&. Open a file for writing, in platform-independent notation and in relation to the write dir as the root of the writable filesystem\&. The specified file is created if it doesn't exist\&. If it does exist, it is truncated to zero bytes, and the writing offset is set to the start\&.
.PP
Note that entries that are symlinks are ignored if PHYSFS_permitSymbolicLinks(1) hasn't been called, and opening a symlink with this function will fail in such a case\&.
.PP
\fBParameters\fP
.RS 4
\fIfilename\fP File to open\&. 
.RE
.PP
\fBReturns\fP
.RS 4
A valid PhysicsFS filehandle on success, NULL on error\&. Use \fBPHYSFS_getLastErrorCode()\fP to obtain the specific error\&.
.RE
.PP
\fBSee also\fP
.RS 4
\fBPHYSFS_openRead\fP 
.PP
\fBPHYSFS_openAppend\fP 
.PP
\fBPHYSFS_write\fP 
.PP
\fBPHYSFS_close\fP 
.RE
.PP

.SS "void PHYSFS_permitSymbolicLinks (int allow)"

.PP
Enable or disable following of symbolic links\&. Some physical filesystems and archives contain files that are just pointers to other files\&. On the physical filesystem, opening such a link will (transparently) open the file that is pointed to\&.
.PP
By default, PhysicsFS will check if a file is really a symlink during open calls and fail if it is\&. Otherwise, the link could take you outside the write and search paths, and compromise security\&.
.PP
If you want to take that risk, call this function with a non-zero parameter\&. Note that this is more for sandboxing a program's scripting language, in case untrusted scripts try to compromise the system\&. Generally speaking, a user could very well have a legitimate reason to set up a symlink, so unless you feel there's a specific danger in allowing them, you should permit them\&.
.PP
Symlinks are only explicitly checked when dealing with filenames in platform-independent notation\&. That is, when setting up your search and write paths, etc, symlinks are never checked for\&.
.PP
Please note that \fBPHYSFS_stat()\fP will always check the path specified; if that path is a symlink, it will not be followed in any case\&. If symlinks aren't permitted through this function, \fBPHYSFS_stat()\fP ignores them, and would treat the query as if the path didn't exist at all\&.
.PP
Symbolic link permission can be enabled or disabled at any time after you've called \fBPHYSFS_init()\fP, and is disabled by default\&.
.PP
\fBParameters\fP
.RS 4
\fIallow\fP nonzero to permit symlinks, zero to deny linking\&.
.RE
.PP
\fBSee also\fP
.RS 4
\fBPHYSFS_symbolicLinksPermitted\fP 
.RE
.PP

.SS "\fBPHYSFS_sint64\fP PHYSFS_read (\fBPHYSFS_File\fP * handle, void * buffer, \fBPHYSFS_uint32\fP objSize, \fBPHYSFS_uint32\fP objCount)"

.PP
Read data from a PhysicsFS filehandle\&. The file must be opened for reading\&.
.PP
\fBDeprecated\fP
.RS 4
As of PhysicsFS 2\&.1, use \fBPHYSFS_readBytes()\fP instead\&. This function just wraps it anyhow\&. This function never clarified what would happen if you managed to read a partial object, so working at the byte level makes this cleaner for everyone, especially now that \fBPHYSFS_Io\fP interfaces can be supplied by the application\&.
.RE
.PP
.PP
\fBParameters\fP
.RS 4
\fIhandle\fP handle returned from \fBPHYSFS_openRead()\fP\&. 
.br
\fIbuffer\fP buffer to store read data into\&. 
.br
\fIobjSize\fP size in bytes of objects being read from (handle)\&. 
.br
\fIobjCount\fP number of (objSize) objects to read from (handle)\&. 
.RE
.PP
\fBReturns\fP
.RS 4
number of objects read\&. \fBPHYSFS_getLastErrorCode()\fP can shed light on the reason this might be < (objCount), as can \fBPHYSFS_eof()\fP\&. -1 if complete failure\&.
.RE
.PP
\fBSee also\fP
.RS 4
\fBPHYSFS_readBytes\fP 
.PP
\fBPHYSFS_eof\fP 
.RE
.PP

.SS "\fBPHYSFS_sint64\fP PHYSFS_readBytes (\fBPHYSFS_File\fP * handle, void * buffer, \fBPHYSFS_uint64\fP len)"

.PP
Read bytes from a PhysicsFS filehandle\&. The file must be opened for reading\&.
.PP
\fBParameters\fP
.RS 4
\fIhandle\fP handle returned from \fBPHYSFS_openRead()\fP\&. 
.br
\fIbuffer\fP buffer of at least (len) bytes to store read data into\&. 
.br
\fIlen\fP number of bytes being read from (handle)\&. 
.RE
.PP
\fBReturns\fP
.RS 4
number of bytes read\&. This may be less than (len); this does not signify an error, necessarily (a short read may mean EOF)\&. \fBPHYSFS_getLastErrorCode()\fP can shed light on the reason this might be < (len), as can \fBPHYSFS_eof()\fP\&. -1 if complete failure\&.
.RE
.PP
\fBSee also\fP
.RS 4
\fBPHYSFS_eof\fP 
.RE
.PP

.SS "int PHYSFS_readSBE16 (\fBPHYSFS_File\fP * file, \fBPHYSFS_sint16\fP * val)"

.PP
Read and convert a signed 16-bit bigendian value\&. Convenience function\&. Read a signed 16-bit bigendian value from a file and convert it to the platform's native byte order\&.
.PP
\fBParameters\fP
.RS 4
\fIfile\fP PhysicsFS file handle from which to read\&. 
.br
\fIval\fP pointer to where value should be stored\&. 
.RE
.PP
\fBReturns\fP
.RS 4
zero on failure, non-zero on success\&. If successful, (*val) will store the result\&. On failure, you can find out what went wrong from \fBPHYSFS_getLastErrorCode()\fP\&. 
.RE
.PP

.SS "int PHYSFS_readSBE32 (\fBPHYSFS_File\fP * file, \fBPHYSFS_sint32\fP * val)"

.PP
Read and convert a signed 32-bit bigendian value\&. Convenience function\&. Read a signed 32-bit bigendian value from a file and convert it to the platform's native byte order\&.
.PP
\fBParameters\fP
.RS 4
\fIfile\fP PhysicsFS file handle from which to read\&. 
.br
\fIval\fP pointer to where value should be stored\&. 
.RE
.PP
\fBReturns\fP
.RS 4
zero on failure, non-zero on success\&. If successful, (*val) will store the result\&. On failure, you can find out what went wrong from \fBPHYSFS_getLastErrorCode()\fP\&. 
.RE
.PP

.SS "int PHYSFS_readSBE64 (\fBPHYSFS_File\fP * file, \fBPHYSFS_sint64\fP * val)"

.PP
Read and convert a signed 64-bit bigendian value\&. Convenience function\&. Read a signed 64-bit bigendian value from a file and convert it to the platform's native byte order\&.
.PP
\fBParameters\fP
.RS 4
\fIfile\fP PhysicsFS file handle from which to read\&. 
.br
\fIval\fP pointer to where value should be stored\&. 
.RE
.PP
\fBReturns\fP
.RS 4
zero on failure, non-zero on success\&. If successful, (*val) will store the result\&. On failure, you can find out what went wrong from \fBPHYSFS_getLastErrorCode()\fP\&.
.RE
.PP
\fBWarning\fP
.RS 4
Remember, PHYSFS_sint64 is only 32 bits on platforms without any sort of 64-bit support\&. 
.RE
.PP

.SS "int PHYSFS_readSLE16 (\fBPHYSFS_File\fP * file, \fBPHYSFS_sint16\fP * val)"

.PP
Read and convert a signed 16-bit littleendian value\&. Convenience function\&. Read a signed 16-bit littleendian value from a file and convert it to the platform's native byte order\&.
.PP
\fBParameters\fP
.RS 4
\fIfile\fP PhysicsFS file handle from which to read\&. 
.br
\fIval\fP pointer to where value should be stored\&. 
.RE
.PP
\fBReturns\fP
.RS 4
zero on failure, non-zero on success\&. If successful, (*val) will store the result\&. On failure, you can find out what went wrong from \fBPHYSFS_getLastErrorCode()\fP\&. 
.RE
.PP

.SS "int PHYSFS_readSLE32 (\fBPHYSFS_File\fP * file, \fBPHYSFS_sint32\fP * val)"

.PP
Read and convert a signed 32-bit littleendian value\&. Convenience function\&. Read a signed 32-bit littleendian value from a file and convert it to the platform's native byte order\&.
.PP
\fBParameters\fP
.RS 4
\fIfile\fP PhysicsFS file handle from which to read\&. 
.br
\fIval\fP pointer to where value should be stored\&. 
.RE
.PP
\fBReturns\fP
.RS 4
zero on failure, non-zero on success\&. If successful, (*val) will store the result\&. On failure, you can find out what went wrong from \fBPHYSFS_getLastErrorCode()\fP\&. 
.RE
.PP

.SS "int PHYSFS_readSLE64 (\fBPHYSFS_File\fP * file, \fBPHYSFS_sint64\fP * val)"

.PP
Read and convert a signed 64-bit littleendian value\&. Convenience function\&. Read a signed 64-bit littleendian value from a file and convert it to the platform's native byte order\&.
.PP
\fBParameters\fP
.RS 4
\fIfile\fP PhysicsFS file handle from which to read\&. 
.br
\fIval\fP pointer to where value should be stored\&. 
.RE
.PP
\fBReturns\fP
.RS 4
zero on failure, non-zero on success\&. If successful, (*val) will store the result\&. On failure, you can find out what went wrong from \fBPHYSFS_getLastErrorCode()\fP\&.
.RE
.PP
\fBWarning\fP
.RS 4
Remember, PHYSFS_sint64 is only 32 bits on platforms without any sort of 64-bit support\&. 
.RE
.PP

.SS "int PHYSFS_readUBE16 (\fBPHYSFS_File\fP * file, \fBPHYSFS_uint16\fP * val)"

.PP
Read and convert an unsigned 16-bit bigendian value\&. Convenience function\&. Read an unsigned 16-bit bigendian value from a file and convert it to the platform's native byte order\&.
.PP
\fBParameters\fP
.RS 4
\fIfile\fP PhysicsFS file handle from which to read\&. 
.br
\fIval\fP pointer to where value should be stored\&. 
.RE
.PP
\fBReturns\fP
.RS 4
zero on failure, non-zero on success\&. If successful, (*val) will store the result\&. On failure, you can find out what went wrong from \fBPHYSFS_getLastErrorCode()\fP\&. 
.RE
.PP

.SS "int PHYSFS_readUBE32 (\fBPHYSFS_File\fP * file, \fBPHYSFS_uint32\fP * val)"

.PP
Read and convert an unsigned 32-bit bigendian value\&. Convenience function\&. Read an unsigned 32-bit bigendian value from a file and convert it to the platform's native byte order\&.
.PP
\fBParameters\fP
.RS 4
\fIfile\fP PhysicsFS file handle from which to read\&. 
.br
\fIval\fP pointer to where value should be stored\&. 
.RE
.PP
\fBReturns\fP
.RS 4
zero on failure, non-zero on success\&. If successful, (*val) will store the result\&. On failure, you can find out what went wrong from \fBPHYSFS_getLastErrorCode()\fP\&. 
.RE
.PP

.SS "int PHYSFS_readUBE64 (\fBPHYSFS_File\fP * file, \fBPHYSFS_uint64\fP * val)"

.PP
Read and convert an unsigned 64-bit bigendian value\&. Convenience function\&. Read an unsigned 64-bit bigendian value from a file and convert it to the platform's native byte order\&.
.PP
\fBParameters\fP
.RS 4
\fIfile\fP PhysicsFS file handle from which to read\&. 
.br
\fIval\fP pointer to where value should be stored\&. 
.RE
.PP
\fBReturns\fP
.RS 4
zero on failure, non-zero on success\&. If successful, (*val) will store the result\&. On failure, you can find out what went wrong from \fBPHYSFS_getLastErrorCode()\fP\&.
.RE
.PP
\fBWarning\fP
.RS 4
Remember, PHYSFS_uint64 is only 32 bits on platforms without any sort of 64-bit support\&. 
.RE
.PP

.SS "int PHYSFS_readULE16 (\fBPHYSFS_File\fP * file, \fBPHYSFS_uint16\fP * val)"

.PP
Read and convert an unsigned 16-bit littleendian value\&. Convenience function\&. Read an unsigned 16-bit littleendian value from a file and convert it to the platform's native byte order\&.
.PP
\fBParameters\fP
.RS 4
\fIfile\fP PhysicsFS file handle from which to read\&. 
.br
\fIval\fP pointer to where value should be stored\&. 
.RE
.PP
\fBReturns\fP
.RS 4
zero on failure, non-zero on success\&. If successful, (*val) will store the result\&. On failure, you can find out what went wrong from \fBPHYSFS_getLastErrorCode()\fP\&. 
.RE
.PP

.SS "int PHYSFS_readULE32 (\fBPHYSFS_File\fP * file, \fBPHYSFS_uint32\fP * val)"

.PP
Read and convert an unsigned 32-bit littleendian value\&. Convenience function\&. Read an unsigned 32-bit littleendian value from a file and convert it to the platform's native byte order\&.
.PP
\fBParameters\fP
.RS 4
\fIfile\fP PhysicsFS file handle from which to read\&. 
.br
\fIval\fP pointer to where value should be stored\&. 
.RE
.PP
\fBReturns\fP
.RS 4
zero on failure, non-zero on success\&. If successful, (*val) will store the result\&. On failure, you can find out what went wrong from \fBPHYSFS_getLastErrorCode()\fP\&. 
.RE
.PP

.SS "int PHYSFS_readULE64 (\fBPHYSFS_File\fP * file, \fBPHYSFS_uint64\fP * val)"

.PP
Read and convert an unsigned 64-bit littleendian value\&. Convenience function\&. Read an unsigned 64-bit littleendian value from a file and convert it to the platform's native byte order\&.
.PP
\fBParameters\fP
.RS 4
\fIfile\fP PhysicsFS file handle from which to read\&. 
.br
\fIval\fP pointer to where value should be stored\&. 
.RE
.PP
\fBReturns\fP
.RS 4
zero on failure, non-zero on success\&. If successful, (*val) will store the result\&. On failure, you can find out what went wrong from \fBPHYSFS_getLastErrorCode()\fP\&.
.RE
.PP
\fBWarning\fP
.RS 4
Remember, PHYSFS_uint64 is only 32 bits on platforms without any sort of 64-bit support\&. 
.RE
.PP

.SS "int PHYSFS_registerArchiver (const \fBPHYSFS_Archiver\fP * archiver)"

.PP
Add a new archiver to the system\&. 
.PP
\fBWarning\fP
.RS 4
This is advanced, hardcore stuff\&. You don't need this unless you really know what you're doing\&. Most apps will not need this\&.
.RE
.PP
If you want to provide your own archiver (for example, a custom archive file format, or some virtual thing you want to make look like a filesystem that you can access through the usual PhysicsFS APIs), this is where you start\&. Once an archiver is successfully registered, then you can use \fBPHYSFS_mount()\fP to add archives that your archiver supports to the search path, or perhaps use it as the write dir\&. Internally, PhysicsFS uses this function to register its own built-in archivers, like \&.zip support, etc\&.
.PP
You may not have two archivers that handle the same extension\&. If you are going to have a clash, you can deregister the other archiver (including built-in ones) with \fBPHYSFS_deregisterArchiver()\fP\&.
.PP
The data in (archiver) is copied; you may free this pointer when this function returns\&.
.PP
Once this function returns successfully, PhysicsFS will be able to support archives of this type until you deregister the archiver again\&.
.PP
\fBParameters\fP
.RS 4
\fIarchiver\fP The archiver to register\&. 
.RE
.PP
\fBReturns\fP
.RS 4
Zero on error, non-zero on success\&.
.RE
.PP
\fBSee also\fP
.RS 4
\fBPHYSFS_Archiver\fP 
.PP
\fBPHYSFS_deregisterArchiver\fP 
.RE
.PP

.SS "int PHYSFS_removeFromSearchPath (const char * oldDir)"

.PP
Remove a directory or archive from the search path\&. 
.PP
\fBDeprecated\fP
.RS 4
As of PhysicsFS 2\&.1, use \fBPHYSFS_unmount()\fP instead\&. This function just wraps it anyhow\&. There's no functional difference except the vocabulary changed from 'adding to the search path' to 'mounting' when that functionality was extended, and thus the preferred way to accomplish this function's work is now called 'unmounting\&.'
.RE
.PP
.PP
This function is equivalent to:
.PP
.PP
.nf
PHYSFS_unmount(oldDir);
.fi
.PP
.PP
You must use this and not PHYSFS_unmount if binary compatibility with PhysicsFS 1\&.0 is important (which it may not be for many people)\&.
.PP
\fBSee also\fP
.RS 4
\fBPHYSFS_addToSearchPath\fP 
.PP
\fBPHYSFS_getSearchPath\fP 
.PP
\fBPHYSFS_unmount\fP 
.RE
.PP

.SS "int PHYSFS_seek (\fBPHYSFS_File\fP * handle, \fBPHYSFS_uint64\fP pos)"

.PP
Seek to a new position within a PhysicsFS filehandle\&. The next read or write will occur at that place\&. Seeking past the beginning or end of the file is not allowed, and causes an error\&.
.PP
\fBParameters\fP
.RS 4
\fIhandle\fP handle returned from PHYSFS_open*()\&. 
.br
\fIpos\fP number of bytes from start of file to seek to\&. 
.RE
.PP
\fBReturns\fP
.RS 4
nonzero on success, zero on error\&. Use \fBPHYSFS_getLastErrorCode()\fP to obtain the specific error\&.
.RE
.PP
\fBSee also\fP
.RS 4
\fBPHYSFS_tell\fP 
.RE
.PP

.SS "int PHYSFS_setAllocator (const \fBPHYSFS_Allocator\fP * allocator)"

.PP
Hook your own allocation routines into PhysicsFS\&. (This is for limited, hardcore use\&. If you don't immediately see a need for it, you can probably ignore this forever\&.)
.PP
By default, PhysicsFS will use whatever is reasonable for a platform to manage dynamic memory (usually ANSI C malloc/realloc/free, but some platforms might use something else), but in some uncommon cases, the app might want more control over the library's memory management\&. This lets you redirect PhysicsFS to use your own allocation routines instead\&. You can only call this function before \fBPHYSFS_init()\fP; if the library is initialized, it'll reject your efforts to change the allocator mid-stream\&. You may call this function after \fBPHYSFS_deinit()\fP if you are willing to shut down the library and restart it with a new allocator; this is a safe and supported operation\&. The allocator remains intact between deinit/init calls\&. If you want to return to the platform's default allocator, pass a NULL in here\&.
.PP
If you aren't immediately sure what to do with this function, you can safely ignore it altogether\&.
.PP
\fBParameters\fP
.RS 4
\fIallocator\fP Structure containing your allocator's entry points\&. 
.RE
.PP
\fBReturns\fP
.RS 4
zero on failure, non-zero on success\&. This call only fails when used between \fBPHYSFS_init()\fP and \fBPHYSFS_deinit()\fP calls\&. 
.RE
.PP

.SS "int PHYSFS_setBuffer (\fBPHYSFS_File\fP * handle, \fBPHYSFS_uint64\fP bufsize)"

.PP
Set up buffering for a PhysicsFS file handle\&. Define an i/o buffer for a file handle\&. A memory block of (bufsize) bytes will be allocated and associated with (handle)\&.
.PP
For files opened for reading, up to (bufsize) bytes are read from (handle) and stored in the internal buffer\&. Calls to \fBPHYSFS_read()\fP will pull from this buffer until it is empty, and then refill it for more reading\&. Note that compressed files, like ZIP archives, will decompress while buffering, so this can be handy for offsetting CPU-intensive operations\&. The buffer isn't filled until you do your next read\&.
.PP
For files opened for writing, data will be buffered to memory until the buffer is full or the buffer is flushed\&. Closing a handle implicitly causes a flush\&.\&.\&.check your return values!
.PP
Seeking, etc transparently accounts for buffering\&.
.PP
You can resize an existing buffer by calling this function more than once on the same file\&. Setting the buffer size to zero will free an existing buffer\&.
.PP
PhysicsFS file handles are unbuffered by default\&.
.PP
Please check the return value of this function! Failures can include not being able to seek backwards in a read-only file when removing the buffer, not being able to allocate the buffer, and not being able to flush the buffer to disk, among other unexpected problems\&.
.PP
\fBParameters\fP
.RS 4
\fIhandle\fP handle returned from PHYSFS_open*()\&. 
.br
\fIbufsize\fP size, in bytes, of buffer to allocate\&. 
.RE
.PP
\fBReturns\fP
.RS 4
nonzero if successful, zero on error\&.
.RE
.PP
\fBSee also\fP
.RS 4
\fBPHYSFS_flush\fP 
.PP
\fBPHYSFS_read\fP 
.PP
\fBPHYSFS_write\fP 
.PP
\fBPHYSFS_close\fP 
.RE
.PP

.SS "void PHYSFS_setErrorCode (\fBPHYSFS_ErrorCode\fP code)"

.PP
Set the current thread's error code\&. This lets you set the value that will be returned by the next call to \fBPHYSFS_getLastErrorCode()\fP\&. This will replace any existing error code, whether set by your application or internally by PhysicsFS\&.
.PP
Error codes are stored per-thread; what you set here will not be accessible to another thread\&.
.PP
Any call into PhysicsFS may change the current error code, so any code you set here is somewhat fragile, and thus you shouldn't build any serious error reporting framework on this function\&. The primary goal of this function is to allow \fBPHYSFS_Io\fP implementations to set the error state, which generally will be passed back to your application when PhysicsFS makes a \fBPHYSFS_Io\fP call that fails internally\&.
.PP
This function doesn't care if the error code is a value known to PhysicsFS or not (but \fBPHYSFS_getErrorByCode()\fP will return NULL for unknown values)\&. The value will be reported unmolested by \fBPHYSFS_getLastErrorCode()\fP\&.
.PP
\fBParameters\fP
.RS 4
\fIcode\fP Error code to become the current thread's new error state\&.
.RE
.PP
\fBSee also\fP
.RS 4
\fBPHYSFS_getLastErrorCode\fP 
.PP
\fBPHYSFS_getErrorByCode\fP 
.RE
.PP

.SS "int PHYSFS_setRoot (const char * archive, const char * subdir)"

.PP
Make a subdirectory of an archive its root directory\&. This lets you narrow down the accessible files in a specific archive\&. For example, if you have x\&.zip with a file in y/z\&.txt, mounted to /a, if you call PHYSFS_setRoot('x\&.zip', '/y'), then the call PHYSFS_openRead('/a/z\&.txt') will succeed\&.
.PP
You can change an archive's root at any time, altering the interpolated file tree (depending on where paths shift, a different archive may be providing various files)\&. If you set the root to NULL or '/', the archive will be treated as if no special root was set (as if the archive was just mounted normally)\&.
.PP
Changing the root only affects future operations on pathnames; a file that was opened from a path that changed due to a setRoot will not be affected\&.
.PP
Setting a new root is not limited to archives in the search path; you may set one on the write dir, too, which might be useful if you have files open for write and thus can't change the write dir at the moment\&.
.PP
It is not an error to set a subdirectory that does not exist to be the root of an archive; however, no files will be visible in this case\&. If the missing directories end up getting created (a mkdir to the physical filesystem, etc) then this will be reflected in the interpolated tree\&.
.PP
\fBParameters\fP
.RS 4
\fIarchive\fP dir/archive on which to change root\&. 
.br
\fIsubdir\fP new subdirectory to make the root of this archive\&. 
.RE
.PP
\fBReturns\fP
.RS 4
nonzero on success, zero on failure\&. Use \fBPHYSFS_getLastErrorCode()\fP to obtain the specific error\&. 
.RE
.PP

.SS "int PHYSFS_setSaneConfig (const char * organization, const char * appName, const char * archiveExt, int includeCdRoms, int archivesFirst)"

.PP
Set up sane, default paths\&. Helper function\&.
.PP
The write dir will be set to the pref dir returned by 
.PP
.nf
PHYSFS_getPrefDir(organization, appName) 

.fi
.PP
, which is created if it doesn't exist\&.
.PP
The above is sufficient to make sure your program's configuration directory is separated from other clutter, and platform-independent\&.
.PP
The search path will be:
.PP
.IP "\(bu" 2
The Write Dir (created if it doesn't exist)
.IP "\(bu" 2
The Base Dir (\fBPHYSFS_getBaseDir()\fP)
.IP "\(bu" 2
All found CD-ROM dirs (optionally)
.PP
.PP
These directories are then searched for files ending with the extension (archiveExt), which, if they are valid and supported archives, will also be added to the search path\&. If you specified 'PKG' for (archiveExt), and there's a file named data\&.PKG in the base dir, it'll be checked\&. Archives can either be appended or prepended to the search path in alphabetical order, regardless of which directories they were found in\&. All archives are mounted in the root of the virtual file system ('/')\&.
.PP
All of this can be accomplished from the application, but this just does it all for you\&. Feel free to add more to the search path manually, too\&.
.PP
\fBParameters\fP
.RS 4
\fIorganization\fP Name of your company/group/etc to be used as a dirname, so keep it small, and no-frills\&.
.br
\fIappName\fP Program-specific name of your program, to separate it from other programs using PhysicsFS\&.
.br
\fIarchiveExt\fP File extension used by your program to specify an archive\&. For example, Quake 3 uses 'pk3', even though they are just zipfiles\&. Specify NULL to not dig out archives automatically\&. Do not specify the '\&.' char; If you want to look for ZIP files, specify 'ZIP' and not '\&.ZIP' \&.\&.\&. the archive search is case-insensitive\&.
.br
\fIincludeCdRoms\fP Non-zero to include CD-ROMs in the search path, and (if (archiveExt) != NULL) search them for archives\&. This may cause a significant amount of blocking while discs are accessed, and if there are no discs in the drive (or even not mounted on Unix systems), then they may not be made available anyhow\&. You may want to specify zero and handle the disc setup yourself\&.
.br
\fIarchivesFirst\fP Non-zero to prepend the archives to the search path\&. Zero to append them\&. Ignored if !(archiveExt)\&.
.RE
.PP
\fBReturns\fP
.RS 4
nonzero on success, zero on error\&. Use \fBPHYSFS_getLastErrorCode()\fP to obtain the specific error\&. 
.RE
.PP

.SS "int PHYSFS_setWriteDir (const char * newDir)"

.PP
Tell PhysicsFS where it may write files\&. Set a new write dir\&. This will override the previous setting\&.
.PP
This call will fail (and fail to change the write dir) if the current write dir still has files open in it\&.
.PP
\fBParameters\fP
.RS 4
\fInewDir\fP The new directory to be the root of the write dir, specified in platform-dependent notation\&. Setting to NULL disables the write dir, so no files can be opened for writing via PhysicsFS\&. 
.RE
.PP
\fBReturns\fP
.RS 4
non-zero on success, zero on failure\&. All attempts to open a file for writing via PhysicsFS will fail until this call succeeds\&. Use \fBPHYSFS_getLastErrorCode()\fP to obtain the specific error\&.
.RE
.PP
\fBSee also\fP
.RS 4
\fBPHYSFS_getWriteDir\fP 
.RE
.PP

.SS "int PHYSFS_stat (const char * fname, \fBPHYSFS_Stat\fP * stat)"

.PP
Get various information about a directory or a file\&. Obtain various information about a file or directory from the meta data\&.
.PP
This function will never follow symbolic links\&. If you haven't enabled symlinks with \fBPHYSFS_permitSymbolicLinks()\fP, stat'ing a symlink will be treated like stat'ing a non-existant file\&. If symlinks are enabled, stat'ing a symlink will give you information on the link itself and not what it points to\&.
.PP
\fBParameters\fP
.RS 4
\fIfname\fP filename to check, in platform-indepedent notation\&. 
.br
\fIstat\fP pointer to structure to fill in with data about (fname)\&. 
.RE
.PP
\fBReturns\fP
.RS 4
non-zero on success, zero on failure\&. On failure, (stat)'s contents are undefined\&.
.RE
.PP
\fBSee also\fP
.RS 4
\fBPHYSFS_Stat\fP 
.RE
.PP

.SS "const \fBPHYSFS_ArchiveInfo\fP ** PHYSFS_supportedArchiveTypes (void)"

.PP
Get a list of supported archive types\&. Get a list of archive types supported by this implementation of PhysicFS\&. These are the file formats usable for search path entries\&. This is for informational purposes only\&. Note that the extension listed is merely convention: if we list 'ZIP', you can open a PkZip-compatible archive with an extension of 'XYZ', if you like\&.
.PP
The returned value is an array of pointers to \fBPHYSFS_ArchiveInfo\fP structures, with a NULL entry to signify the end of the list:
.PP
.PP
.nf
PHYSFS_ArchiveInfo **i;

for (i = PHYSFS_supportedArchiveTypes(); *i != NULL; i++)
{
    printf("Supported archive: [%s], which is [%s]\&.\n",
             (*i)->extension, (*i)->description);
}
.fi
.PP
.PP
The return values are pointers to internal memory, and should be considered READ ONLY, and never freed\&. The returned values are valid until the next call to \fBPHYSFS_deinit()\fP, \fBPHYSFS_registerArchiver()\fP, or \fBPHYSFS_deregisterArchiver()\fP\&.
.PP
\fBReturns\fP
.RS 4
READ ONLY Null-terminated array of READ ONLY structures\&.
.RE
.PP
\fBSee also\fP
.RS 4
\fBPHYSFS_registerArchiver\fP 
.PP
\fBPHYSFS_deregisterArchiver\fP 
.RE
.PP

.SS "\fBPHYSFS_sint16\fP PHYSFS_swapSBE16 (\fBPHYSFS_sint16\fP val)"

.PP
Swap bigendian signed 16 to platform's native byte order\&. Take a 16-bit signed value in bigendian format and convert it to the platform's native byte order\&.
.PP
\fBParameters\fP
.RS 4
\fIval\fP value to convert 
.RE
.PP
\fBReturns\fP
.RS 4
converted value\&. 
.RE
.PP

.SS "\fBPHYSFS_sint32\fP PHYSFS_swapSBE32 (\fBPHYSFS_sint32\fP val)"

.PP
Swap bigendian signed 32 to platform's native byte order\&. Take a 32-bit signed value in bigendian format and convert it to the platform's native byte order\&.
.PP
\fBParameters\fP
.RS 4
\fIval\fP value to convert 
.RE
.PP
\fBReturns\fP
.RS 4
converted value\&. 
.RE
.PP

.SS "\fBPHYSFS_sint64\fP PHYSFS_swapSBE64 (\fBPHYSFS_sint64\fP val)"

.PP
Swap bigendian signed 64 to platform's native byte order\&. Take a 64-bit signed value in bigendian format and convert it to the platform's native byte order\&.
.PP
\fBParameters\fP
.RS 4
\fIval\fP value to convert 
.RE
.PP
\fBReturns\fP
.RS 4
converted value\&.
.RE
.PP
\fBWarning\fP
.RS 4
Remember, PHYSFS_sint64 is only 32 bits on platforms without any sort of 64-bit support\&. 
.RE
.PP

.SS "\fBPHYSFS_sint16\fP PHYSFS_swapSLE16 (\fBPHYSFS_sint16\fP val)"

.PP
Swap littleendian signed 16 to platform's native byte order\&. Take a 16-bit signed value in littleendian format and convert it to the platform's native byte order\&.
.PP
\fBParameters\fP
.RS 4
\fIval\fP value to convert 
.RE
.PP
\fBReturns\fP
.RS 4
converted value\&. 
.RE
.PP

.SS "\fBPHYSFS_sint32\fP PHYSFS_swapSLE32 (\fBPHYSFS_sint32\fP val)"

.PP
Swap littleendian signed 32 to platform's native byte order\&. Take a 32-bit signed value in littleendian format and convert it to the platform's native byte order\&.
.PP
\fBParameters\fP
.RS 4
\fIval\fP value to convert 
.RE
.PP
\fBReturns\fP
.RS 4
converted value\&. 
.RE
.PP

.SS "\fBPHYSFS_sint64\fP PHYSFS_swapSLE64 (\fBPHYSFS_sint64\fP val)"

.PP
Swap littleendian signed 64 to platform's native byte order\&. Take a 64-bit signed value in littleendian format and convert it to the platform's native byte order\&.
.PP
\fBParameters\fP
.RS 4
\fIval\fP value to convert 
.RE
.PP
\fBReturns\fP
.RS 4
converted value\&.
.RE
.PP
\fBWarning\fP
.RS 4
Remember, PHYSFS_sint64 is only 32 bits on platforms without any sort of 64-bit support\&. 
.RE
.PP

.SS "\fBPHYSFS_uint16\fP PHYSFS_swapUBE16 (\fBPHYSFS_uint16\fP val)"

.PP
Swap bigendian unsigned 16 to platform's native byte order\&. Take a 16-bit unsigned value in bigendian format and convert it to the platform's native byte order\&.
.PP
\fBParameters\fP
.RS 4
\fIval\fP value to convert 
.RE
.PP
\fBReturns\fP
.RS 4
converted value\&. 
.RE
.PP

.SS "\fBPHYSFS_uint32\fP PHYSFS_swapUBE32 (\fBPHYSFS_uint32\fP val)"

.PP
Swap bigendian unsigned 32 to platform's native byte order\&. Take a 32-bit unsigned value in bigendian format and convert it to the platform's native byte order\&.
.PP
\fBParameters\fP
.RS 4
\fIval\fP value to convert 
.RE
.PP
\fBReturns\fP
.RS 4
converted value\&. 
.RE
.PP

.SS "\fBPHYSFS_uint64\fP PHYSFS_swapUBE64 (\fBPHYSFS_uint64\fP val)"

.PP
Swap bigendian unsigned 64 to platform's native byte order\&. Take a 64-bit unsigned value in bigendian format and convert it to the platform's native byte order\&.
.PP
\fBParameters\fP
.RS 4
\fIval\fP value to convert 
.RE
.PP
\fBReturns\fP
.RS 4
converted value\&.
.RE
.PP
\fBWarning\fP
.RS 4
Remember, PHYSFS_uint64 is only 32 bits on platforms without any sort of 64-bit support\&. 
.RE
.PP

.SS "\fBPHYSFS_uint16\fP PHYSFS_swapULE16 (\fBPHYSFS_uint16\fP val)"

.PP
Swap littleendian unsigned 16 to platform's native byte order\&. Take a 16-bit unsigned value in littleendian format and convert it to the platform's native byte order\&.
.PP
\fBParameters\fP
.RS 4
\fIval\fP value to convert 
.RE
.PP
\fBReturns\fP
.RS 4
converted value\&. 
.RE
.PP

.SS "\fBPHYSFS_uint32\fP PHYSFS_swapULE32 (\fBPHYSFS_uint32\fP val)"

.PP
Swap littleendian unsigned 32 to platform's native byte order\&. Take a 32-bit unsigned value in littleendian format and convert it to the platform's native byte order\&.
.PP
\fBParameters\fP
.RS 4
\fIval\fP value to convert 
.RE
.PP
\fBReturns\fP
.RS 4
converted value\&. 
.RE
.PP

.SS "\fBPHYSFS_uint64\fP PHYSFS_swapULE64 (\fBPHYSFS_uint64\fP val)"

.PP
Swap littleendian unsigned 64 to platform's native byte order\&. Take a 64-bit unsigned value in littleendian format and convert it to the platform's native byte order\&.
.PP
\fBParameters\fP
.RS 4
\fIval\fP value to convert 
.RE
.PP
\fBReturns\fP
.RS 4
converted value\&.
.RE
.PP
\fBWarning\fP
.RS 4
Remember, PHYSFS_uint64 is only 32 bits on platforms without any sort of 64-bit support\&. 
.RE
.PP

.SS "int PHYSFS_symbolicLinksPermitted (void)"

.PP
Determine if the symbolic links are permitted\&. This reports the setting from the last call to \fBPHYSFS_permitSymbolicLinks()\fP\&. If \fBPHYSFS_permitSymbolicLinks()\fP hasn't been called since the library was last initialized, symbolic links are implicitly disabled\&.
.PP
\fBReturns\fP
.RS 4
non-zero if symlinks are permitted, zero if not\&.
.RE
.PP
\fBSee also\fP
.RS 4
\fBPHYSFS_permitSymbolicLinks\fP 
.RE
.PP

.SS "\fBPHYSFS_sint64\fP PHYSFS_tell (\fBPHYSFS_File\fP * handle)"

.PP
Determine current position within a PhysicsFS filehandle\&. 
.PP
\fBParameters\fP
.RS 4
\fIhandle\fP handle returned from PHYSFS_open*()\&. 
.RE
.PP
\fBReturns\fP
.RS 4
offset in bytes from start of file\&. -1 if error occurred\&. Use \fBPHYSFS_getLastErrorCode()\fP to obtain the specific error\&.
.RE
.PP
\fBSee also\fP
.RS 4
\fBPHYSFS_seek\fP 
.RE
.PP

.SS "int PHYSFS_ucs4stricmp (const \fBPHYSFS_uint32\fP * str1, const \fBPHYSFS_uint32\fP * str2)"

.PP
Case-insensitive compare of two UCS-4 strings\&. This is a strcasecmp/stricmp replacement that expects both strings to be in UCS-4 (aka UTF-32) encoding\&. It will do 'case folding' to decide if the Unicode codepoints in the strings match\&.
.PP
It will report which string is 'greater than' the other, but be aware that this doesn't necessarily mean anything: 'a' may be 'less than' 'b', but a Japanese kuten has no meaningful alphabetically relationship to a Greek lambda, but being able to assign a reliable 'value' makes sorting algorithms possible, if not entirely sane\&. Most cases should treat the return value as 'equal' or 'not equal'\&.
.PP
Like stricmp, this expects both strings to be NULL-terminated\&.
.PP
\fBParameters\fP
.RS 4
\fIstr1\fP First string to compare\&. 
.br
\fIstr2\fP Second string to compare\&. 
.RE
.PP
\fBReturns\fP
.RS 4
-1 if str1 is 'less than' str2, 1 if 'greater than', 0 if equal\&. 
.RE
.PP

.SS "int PHYSFS_unmount (const char * oldDir)"

.PP
Remove a directory or archive from the search path\&. This is functionally equivalent to \fBPHYSFS_removeFromSearchPath()\fP, but that function is deprecated to keep the vocabulary paired with \fBPHYSFS_mount()\fP\&.
.PP
This must be a (case-sensitive) match to a dir or archive already in the search path, specified in platform-dependent notation\&.
.PP
This call will fail (and fail to remove from the path) if the element still has files open in it\&.
.PP
\fBWarning\fP
.RS 4
This function wants the path to the archive or directory that was mounted (the same string used for the 'newDir' argument of PHYSFS_addToSearchPath or any of the mount functions), not the path where it is mounted in the tree (the 'mountPoint' argument to any of the mount functions)\&.
.RE
.PP
\fBParameters\fP
.RS 4
\fIoldDir\fP dir/archive to remove\&. 
.RE
.PP
\fBReturns\fP
.RS 4
nonzero on success, zero on failure\&. Use \fBPHYSFS_getLastErrorCode()\fP to obtain the specific error\&.
.RE
.PP
\fBSee also\fP
.RS 4
\fBPHYSFS_getSearchPath\fP 
.PP
\fBPHYSFS_mount\fP 
.RE
.PP

.SS "int PHYSFS_utf16stricmp (const \fBPHYSFS_uint16\fP * str1, const \fBPHYSFS_uint16\fP * str2)"

.PP
Case-insensitive compare of two UTF-16 strings\&. This is a strcasecmp/stricmp replacement that expects both strings to be in UTF-16 encoding\&. It will do 'case folding' to decide if the Unicode codepoints in the strings match\&.
.PP
It will report which string is 'greater than' the other, but be aware that this doesn't necessarily mean anything: 'a' may be 'less than' 'b', but a Japanese kuten has no meaningful alphabetically relationship to a Greek lambda, but being able to assign a reliable 'value' makes sorting algorithms possible, if not entirely sane\&. Most cases should treat the return value as 'equal' or 'not equal'\&.
.PP
Like stricmp, this expects both strings to be NULL-terminated\&.
.PP
\fBParameters\fP
.RS 4
\fIstr1\fP First string to compare\&. 
.br
\fIstr2\fP Second string to compare\&. 
.RE
.PP
\fBReturns\fP
.RS 4
-1 if str1 is 'less than' str2, 1 if 'greater than', 0 if equal\&. 
.RE
.PP

.SS "void PHYSFS_utf8FromLatin1 (const char * src, char * dst, \fBPHYSFS_uint64\fP len)"

.PP
Convert a UTF-8 string to a Latin1 string\&. Latin1 strings are 8-bits per character: a popular 'high ASCII' encoding\&.
.PP
To ensure that the destination buffer is large enough for the conversion, please allocate a buffer that is double the size of the source buffer\&. UTF-8 expands latin1 codepoints over 127 from 1 to 2 bytes, so the string may grow in some cases\&.
.PP
Strings that don't fit in the destination buffer will be truncated, but will always be null-terminated and never have an incomplete UTF-8 sequence at the end\&. If the buffer length is 0, this function does nothing\&.
.PP
Please note that we do not supply a UTF-8 to Latin1 converter, since Latin1 can't express most Unicode codepoints\&. It's a legacy encoding; you should be converting away from it at all times\&.
.PP
\fBParameters\fP
.RS 4
\fIsrc\fP Null-terminated source string in Latin1 format\&. 
.br
\fIdst\fP Buffer to store converted UTF-8 string\&. 
.br
\fIlen\fP Size, in bytes, of destination buffer\&. 
.RE
.PP

.SS "void PHYSFS_utf8FromUcs2 (const \fBPHYSFS_uint16\fP * src, char * dst, \fBPHYSFS_uint64\fP len)"

.PP
Convert a UCS-2 string to a UTF-8 string\&. 
.PP
\fBWarning\fP
.RS 4
you almost certainly should use \fBPHYSFS_utf8FromUtf16()\fP, which became available in PhysicsFS 2\&.1, unless you know what you're doing\&.
.PP
This function will not report an error if there are invalid UCS-2 values in the source string\&. It will replace them with a '?' character and continue on\&.
.RE
.PP
UCS-2 strings are 16-bits per character: \fCTCHAR\fP on Windows, when building with Unicode support\&. Please note that modern versions of Windows use UTF-16, which is an extended form of UCS-2, and not UCS-2 itself\&. You almost certainly want \fBPHYSFS_utf8FromUtf16()\fP instead\&.
.PP
To ensure that the destination buffer is large enough for the conversion, please allocate a buffer that is double the size of the source buffer\&. UTF-8 never uses more than 32-bits per character, so while it may shrink a UCS-2 string, it may also expand it\&.
.PP
Strings that don't fit in the destination buffer will be truncated, but will always be null-terminated and never have an incomplete UTF-8 sequence at the end\&. If the buffer length is 0, this function does nothing\&.
.PP
\fBParameters\fP
.RS 4
\fIsrc\fP Null-terminated source string in UCS-2 format\&. 
.br
\fIdst\fP Buffer to store converted UTF-8 string\&. 
.br
\fIlen\fP Size, in bytes, of destination buffer\&.
.RE
.PP
\fBSee also\fP
.RS 4
\fBPHYSFS_utf8FromUtf16\fP 
.RE
.PP

.SS "void PHYSFS_utf8FromUcs4 (const \fBPHYSFS_uint32\fP * src, char * dst, \fBPHYSFS_uint64\fP len)"

.PP
Convert a UCS-4 string to a UTF-8 string\&. 
.PP
\fBWarning\fP
.RS 4
This function will not report an error if there are invalid UCS-4 values in the source string\&. It will replace them with a '?' character and continue on\&.
.RE
.PP
UCS-4 (aka UTF-32) strings are 32-bits per character: \fCwchar_t\fP on Unix\&.
.PP
To ensure that the destination buffer is large enough for the conversion, please allocate a buffer that is the same size as the source buffer\&. UTF-8 never uses more than 32-bits per character, so while it may shrink a UCS-4 string, it will never expand it\&.
.PP
Strings that don't fit in the destination buffer will be truncated, but will always be null-terminated and never have an incomplete UTF-8 sequence at the end\&. If the buffer length is 0, this function does nothing\&.
.PP
\fBParameters\fP
.RS 4
\fIsrc\fP Null-terminated source string in UCS-4 format\&. 
.br
\fIdst\fP Buffer to store converted UTF-8 string\&. 
.br
\fIlen\fP Size, in bytes, of destination buffer\&. 
.RE
.PP

.SS "void PHYSFS_utf8FromUtf16 (const \fBPHYSFS_uint16\fP * src, char * dst, \fBPHYSFS_uint64\fP len)"

.PP
Convert a UTF-16 string to a UTF-8 string\&. 
.PP
\fBWarning\fP
.RS 4
This function will not report an error if there are invalid UTF-16 sequences in the source string\&. It will replace them with a '?' character and continue on\&.
.RE
.PP
UTF-16 strings are 16-bits per character (except some chars, which are 32-bits): \fCTCHAR\fP on Windows, when building with Unicode support\&. Modern Windows releases use UTF-16\&. Windows releases before 2000 used TCHAR, but only handled UCS-2\&. UTF-16 \fIis\fP UCS-2, except for the characters that are 4 bytes, which aren't representable in UCS-2 at all anyhow\&. If you aren't sure, you should be using UTF-16 at this point on Windows\&.
.PP
To ensure that the destination buffer is large enough for the conversion, please allocate a buffer that is double the size of the source buffer\&. UTF-8 never uses more than 32-bits per character, so while it may shrink a UTF-16 string, it may also expand it\&.
.PP
Strings that don't fit in the destination buffer will be truncated, but will always be null-terminated and never have an incomplete UTF-8 sequence at the end\&. If the buffer length is 0, this function does nothing\&.
.PP
\fBParameters\fP
.RS 4
\fIsrc\fP Null-terminated source string in UTF-16 format\&. 
.br
\fIdst\fP Buffer to store converted UTF-8 string\&. 
.br
\fIlen\fP Size, in bytes, of destination buffer\&. 
.RE
.PP

.SS "int PHYSFS_utf8stricmp (const char * str1, const char * str2)"

.PP
Case-insensitive compare of two UTF-8 strings\&. This is a strcasecmp/stricmp replacement that expects both strings to be in UTF-8 encoding\&. It will do 'case folding' to decide if the Unicode codepoints in the strings match\&.
.PP
If both strings are exclusively low-ASCII characters, this will do the right thing, as that is also valid UTF-8\&. If there are any high-ASCII chars, this will not do what you expect!
.PP
It will report which string is 'greater than' the other, but be aware that this doesn't necessarily mean anything: 'a' may be 'less than' 'b', but a Japanese kuten has no meaningful alphabetically relationship to a Greek lambda, but being able to assign a reliable 'value' makes sorting algorithms possible, if not entirely sane\&. Most cases should treat the return value as 'equal' or 'not equal'\&.
.PP
Like stricmp, this expects both strings to be NULL-terminated\&.
.PP
\fBParameters\fP
.RS 4
\fIstr1\fP First string to compare\&. 
.br
\fIstr2\fP Second string to compare\&. 
.RE
.PP
\fBReturns\fP
.RS 4
-1 if str1 is 'less than' str2, 1 if 'greater than', 0 if equal\&. 
.RE
.PP

.SS "PHYSFS_utf8ToUcs2 (const char * src, \fBPHYSFS_uint16\fP * dst, \fBPHYSFS_uint64\fP len)"

.PP
Convert a UTF-8 string to a UCS-2 string\&. 
.PP
\fBWarning\fP
.RS 4
you almost certainly should use \fBPHYSFS_utf8ToUtf16()\fP, which became available in PhysicsFS 2\&.1, unless you know what you're doing\&.
.PP
This function will not report an error if there are invalid UTF-8 sequences in the source string\&. It will replace them with a '?' character and continue on\&.
.RE
.PP
UCS-2 strings are 16-bits per character: \fCTCHAR\fP on Windows, when building with Unicode support\&. Please note that modern versions of Windows use UTF-16, which is an extended form of UCS-2, and not UCS-2 itself\&. You almost certainly want \fBPHYSFS_utf8ToUtf16()\fP instead, but you need to understand how that changes things, too\&.
.PP
To ensure that the destination buffer is large enough for the conversion, please allocate a buffer that is double the size of the source buffer\&. UTF-8 uses from one to four bytes per character, but UCS-2 always uses two, so an entirely low-ASCII string will double in size!
.PP
Strings that don't fit in the destination buffer will be truncated, but will always be null-terminated and never have an incomplete UCS-2 sequence at the end\&. If the buffer length is 0, this function does nothing\&.
.PP
\fBParameters\fP
.RS 4
\fIsrc\fP Null-terminated source string in UTF-8 format\&. 
.br
\fIdst\fP Buffer to store converted UCS-2 string\&. 
.br
\fIlen\fP Size, in bytes, of destination buffer\&.
.RE
.PP
\fBSee also\fP
.RS 4
\fBPHYSFS_utf8ToUtf16\fP 
.RE
.PP

.SS "void PHYSFS_utf8ToUcs4 (const char * src, \fBPHYSFS_uint32\fP * dst, \fBPHYSFS_uint64\fP len)"

.PP
Convert a UTF-8 string to a UCS-4 string\&. 
.PP
\fBWarning\fP
.RS 4
This function will not report an error if there are invalid UTF-8 sequences in the source string\&. It will replace them with a '?' character and continue on\&.
.RE
.PP
UCS-4 (aka UTF-32) strings are 32-bits per character: \fCwchar_t\fP on Unix\&.
.PP
To ensure that the destination buffer is large enough for the conversion, please allocate a buffer that is four times the size of the source buffer\&. UTF-8 uses from one to four bytes per character, but UCS-4 always uses four, so an entirely low-ASCII string will quadruple in size!
.PP
Strings that don't fit in the destination buffer will be truncated, but will always be null-terminated and never have an incomplete UCS-4 sequence at the end\&. If the buffer length is 0, this function does nothing\&.
.PP
\fBParameters\fP
.RS 4
\fIsrc\fP Null-terminated source string in UTF-8 format\&. 
.br
\fIdst\fP Buffer to store converted UCS-4 string\&. 
.br
\fIlen\fP Size, in bytes, of destination buffer\&. 
.RE
.PP

.SS "PHYSFS_utf8ToUtf16 (const char * src, \fBPHYSFS_uint16\fP * dst, \fBPHYSFS_uint64\fP len)"

.PP
Convert a UTF-8 string to a UTF-16 string\&. 
.PP
\fBWarning\fP
.RS 4
This function will not report an error if there are invalid UTF-8 sequences in the source string\&. It will replace them with a '?' character and continue on\&.
.RE
.PP
UTF-16 strings are 16-bits per character (except some chars, which are 32-bits): \fCTCHAR\fP on Windows, when building with Unicode support\&. Modern Windows releases use UTF-16\&. Windows releases before 2000 used TCHAR, but only handled UCS-2\&. UTF-16 \fIis\fP UCS-2, except for the characters that are 4 bytes, which aren't representable in UCS-2 at all anyhow\&. If you aren't sure, you should be using UTF-16 at this point on Windows\&.
.PP
To ensure that the destination buffer is large enough for the conversion, please allocate a buffer that is double the size of the source buffer\&. UTF-8 uses from one to four bytes per character, but UTF-16 always uses two to four, so an entirely low-ASCII string will double in size! The UTF-16 characters that would take four bytes also take four bytes in UTF-8, so you don't need to allocate 4x the space just in case: double will do\&.
.PP
Strings that don't fit in the destination buffer will be truncated, but will always be null-terminated and never have an incomplete UTF-16 surrogate pair at the end\&. If the buffer length is 0, this function does nothing\&.
.PP
\fBParameters\fP
.RS 4
\fIsrc\fP Null-terminated source string in UTF-8 format\&. 
.br
\fIdst\fP Buffer to store converted UTF-16 string\&. 
.br
\fIlen\fP Size, in bytes, of destination buffer\&.
.RE
.PP
\fBSee also\fP
.RS 4
\fBPHYSFS_utf8ToUtf16\fP 
.RE
.PP

.SS "\fBPHYSFS_sint64\fP PHYSFS_write (\fBPHYSFS_File\fP * handle, const void * buffer, \fBPHYSFS_uint32\fP objSize, \fBPHYSFS_uint32\fP objCount)"

.PP
Write data to a PhysicsFS filehandle\&. The file must be opened for writing\&.
.PP
\fBDeprecated\fP
.RS 4
As of PhysicsFS 2\&.1, use \fBPHYSFS_writeBytes()\fP instead\&. This function just wraps it anyhow\&. This function never clarified what would happen if you managed to write a partial object, so working at the byte level makes this cleaner for everyone, especially now that \fBPHYSFS_Io\fP interfaces can be supplied by the application\&.
.RE
.PP
.PP
\fBParameters\fP
.RS 4
\fIhandle\fP retval from \fBPHYSFS_openWrite()\fP or \fBPHYSFS_openAppend()\fP\&. 
.br
\fIbuffer\fP buffer of bytes to write to (handle)\&. 
.br
\fIobjSize\fP size in bytes of objects being written to (handle)\&. 
.br
\fIobjCount\fP number of (objSize) objects to write to (handle)\&. 
.RE
.PP
\fBReturns\fP
.RS 4
number of objects written\&. \fBPHYSFS_getLastErrorCode()\fP can shed light on the reason this might be < (objCount)\&. -1 if complete failure\&.
.RE
.PP
\fBSee also\fP
.RS 4
\fBPHYSFS_writeBytes\fP 
.RE
.PP

.SS "\fBPHYSFS_sint64\fP PHYSFS_writeBytes (\fBPHYSFS_File\fP * handle, const void * buffer, \fBPHYSFS_uint64\fP len)"

.PP
Write data to a PhysicsFS filehandle\&. The file must be opened for writing\&.
.PP
Please note that while (len) is an unsigned 64-bit integer, you are limited to 63 bits (9223372036854775807 bytes), so we can return a negative value on error\&. If length is greater than 0x7FFFFFFFFFFFFFFF, this function will immediately fail\&. For systems without a 64-bit datatype, you are limited to 31 bits (0x7FFFFFFF, or 2147483647 bytes)\&. We trust most things won't need to do multiple gigabytes of i/o in one call anyhow, but why limit things?
.PP
\fBParameters\fP
.RS 4
\fIhandle\fP retval from \fBPHYSFS_openWrite()\fP or \fBPHYSFS_openAppend()\fP\&. 
.br
\fIbuffer\fP buffer of (len) bytes to write to (handle)\&. 
.br
\fIlen\fP number of bytes being written to (handle)\&. 
.RE
.PP
\fBReturns\fP
.RS 4
number of bytes written\&. This may be less than (len); in the case of an error, the system may try to write as many bytes as possible, so an incomplete write might occur\&. \fBPHYSFS_getLastErrorCode()\fP can shed light on the reason this might be < (len)\&. -1 if complete failure\&. 
.RE
.PP

.SS "int PHYSFS_writeSBE16 (\fBPHYSFS_File\fP * file, \fBPHYSFS_sint16\fP val)"

.PP
Convert and write a signed 16-bit bigendian value\&. Convenience function\&. Convert a signed 16-bit value from the platform's native byte order to bigendian and write it to a file\&.
.PP
\fBParameters\fP
.RS 4
\fIfile\fP PhysicsFS file handle to which to write\&. 
.br
\fIval\fP Value to convert and write\&. 
.RE
.PP
\fBReturns\fP
.RS 4
zero on failure, non-zero on success\&. On failure, you can find out what went wrong from \fBPHYSFS_getLastErrorCode()\fP\&. 
.RE
.PP

.SS "int PHYSFS_writeSBE32 (\fBPHYSFS_File\fP * file, \fBPHYSFS_sint32\fP val)"

.PP
Convert and write a signed 32-bit bigendian value\&. Convenience function\&. Convert a signed 32-bit value from the platform's native byte order to bigendian and write it to a file\&.
.PP
\fBParameters\fP
.RS 4
\fIfile\fP PhysicsFS file handle to which to write\&. 
.br
\fIval\fP Value to convert and write\&. 
.RE
.PP
\fBReturns\fP
.RS 4
zero on failure, non-zero on success\&. On failure, you can find out what went wrong from \fBPHYSFS_getLastErrorCode()\fP\&. 
.RE
.PP

.SS "int PHYSFS_writeSBE64 (\fBPHYSFS_File\fP * file, \fBPHYSFS_sint64\fP val)"

.PP
Convert and write a signed 64-bit bigending value\&. Convenience function\&. Convert a signed 64-bit value from the platform's native byte order to bigendian and write it to a file\&.
.PP
\fBParameters\fP
.RS 4
\fIfile\fP PhysicsFS file handle to which to write\&. 
.br
\fIval\fP Value to convert and write\&. 
.RE
.PP
\fBReturns\fP
.RS 4
zero on failure, non-zero on success\&. On failure, you can find out what went wrong from \fBPHYSFS_getLastErrorCode()\fP\&.
.RE
.PP
\fBWarning\fP
.RS 4
Remember, PHYSFS_sint64 is only 32 bits on platforms without any sort of 64-bit support\&. 
.RE
.PP

.SS "int PHYSFS_writeSLE16 (\fBPHYSFS_File\fP * file, \fBPHYSFS_sint16\fP val)"

.PP
Convert and write a signed 16-bit littleendian value\&. Convenience function\&. Convert a signed 16-bit value from the platform's native byte order to littleendian and write it to a file\&.
.PP
\fBParameters\fP
.RS 4
\fIfile\fP PhysicsFS file handle to which to write\&. 
.br
\fIval\fP Value to convert and write\&. 
.RE
.PP
\fBReturns\fP
.RS 4
zero on failure, non-zero on success\&. On failure, you can find out what went wrong from \fBPHYSFS_getLastErrorCode()\fP\&. 
.RE
.PP

.SS "int PHYSFS_writeSLE32 (\fBPHYSFS_File\fP * file, \fBPHYSFS_sint32\fP val)"

.PP
Convert and write a signed 32-bit littleendian value\&. Convenience function\&. Convert a signed 32-bit value from the platform's native byte order to littleendian and write it to a file\&.
.PP
\fBParameters\fP
.RS 4
\fIfile\fP PhysicsFS file handle to which to write\&. 
.br
\fIval\fP Value to convert and write\&. 
.RE
.PP
\fBReturns\fP
.RS 4
zero on failure, non-zero on success\&. On failure, you can find out what went wrong from \fBPHYSFS_getLastErrorCode()\fP\&. 
.RE
.PP

.SS "int PHYSFS_writeSLE64 (\fBPHYSFS_File\fP * file, \fBPHYSFS_sint64\fP val)"

.PP
Convert and write a signed 64-bit littleendian value\&. Convenience function\&. Convert a signed 64-bit value from the platform's native byte order to littleendian and write it to a file\&.
.PP
\fBParameters\fP
.RS 4
\fIfile\fP PhysicsFS file handle to which to write\&. 
.br
\fIval\fP Value to convert and write\&. 
.RE
.PP
\fBReturns\fP
.RS 4
zero on failure, non-zero on success\&. On failure, you can find out what went wrong from \fBPHYSFS_getLastErrorCode()\fP\&.
.RE
.PP
\fBWarning\fP
.RS 4
Remember, PHYSFS_sint64 is only 32 bits on platforms without any sort of 64-bit support\&. 
.RE
.PP

.SS "int PHYSFS_writeUBE16 (\fBPHYSFS_File\fP * file, \fBPHYSFS_uint16\fP val)"

.PP
Convert and write an unsigned 16-bit bigendian value\&. Convenience function\&. Convert an unsigned 16-bit value from the platform's native byte order to bigendian and write it to a file\&.
.PP
\fBParameters\fP
.RS 4
\fIfile\fP PhysicsFS file handle to which to write\&. 
.br
\fIval\fP Value to convert and write\&. 
.RE
.PP
\fBReturns\fP
.RS 4
zero on failure, non-zero on success\&. On failure, you can find out what went wrong from \fBPHYSFS_getLastErrorCode()\fP\&. 
.RE
.PP

.SS "int PHYSFS_writeUBE32 (\fBPHYSFS_File\fP * file, \fBPHYSFS_uint32\fP val)"

.PP
Convert and write an unsigned 32-bit bigendian value\&. Convenience function\&. Convert an unsigned 32-bit value from the platform's native byte order to bigendian and write it to a file\&.
.PP
\fBParameters\fP
.RS 4
\fIfile\fP PhysicsFS file handle to which to write\&. 
.br
\fIval\fP Value to convert and write\&. 
.RE
.PP
\fBReturns\fP
.RS 4
zero on failure, non-zero on success\&. On failure, you can find out what went wrong from \fBPHYSFS_getLastErrorCode()\fP\&. 
.RE
.PP

.SS "int PHYSFS_writeUBE64 (\fBPHYSFS_File\fP * file, \fBPHYSFS_uint64\fP val)"

.PP
Convert and write an unsigned 64-bit bigendian value\&. Convenience function\&. Convert an unsigned 64-bit value from the platform's native byte order to bigendian and write it to a file\&.
.PP
\fBParameters\fP
.RS 4
\fIfile\fP PhysicsFS file handle to which to write\&. 
.br
\fIval\fP Value to convert and write\&. 
.RE
.PP
\fBReturns\fP
.RS 4
zero on failure, non-zero on success\&. On failure, you can find out what went wrong from \fBPHYSFS_getLastErrorCode()\fP\&.
.RE
.PP
\fBWarning\fP
.RS 4
Remember, PHYSFS_uint64 is only 32 bits on platforms without any sort of 64-bit support\&. 
.RE
.PP

.SS "int PHYSFS_writeULE16 (\fBPHYSFS_File\fP * file, \fBPHYSFS_uint16\fP val)"

.PP
Convert and write an unsigned 16-bit littleendian value\&. Convenience function\&. Convert an unsigned 16-bit value from the platform's native byte order to littleendian and write it to a file\&.
.PP
\fBParameters\fP
.RS 4
\fIfile\fP PhysicsFS file handle to which to write\&. 
.br
\fIval\fP Value to convert and write\&. 
.RE
.PP
\fBReturns\fP
.RS 4
zero on failure, non-zero on success\&. On failure, you can find out what went wrong from \fBPHYSFS_getLastErrorCode()\fP\&. 
.RE
.PP

.SS "int PHYSFS_writeULE32 (\fBPHYSFS_File\fP * file, \fBPHYSFS_uint32\fP val)"

.PP
Convert and write an unsigned 32-bit littleendian value\&. Convenience function\&. Convert an unsigned 32-bit value from the platform's native byte order to littleendian and write it to a file\&.
.PP
\fBParameters\fP
.RS 4
\fIfile\fP PhysicsFS file handle to which to write\&. 
.br
\fIval\fP Value to convert and write\&. 
.RE
.PP
\fBReturns\fP
.RS 4
zero on failure, non-zero on success\&. On failure, you can find out what went wrong from \fBPHYSFS_getLastErrorCode()\fP\&. 
.RE
.PP

.SS "int PHYSFS_writeULE64 (\fBPHYSFS_File\fP * file, \fBPHYSFS_uint64\fP val)"

.PP
Convert and write an unsigned 64-bit littleendian value\&. Convenience function\&. Convert an unsigned 64-bit value from the platform's native byte order to littleendian and write it to a file\&.
.PP
\fBParameters\fP
.RS 4
\fIfile\fP PhysicsFS file handle to which to write\&. 
.br
\fIval\fP Value to convert and write\&. 
.RE
.PP
\fBReturns\fP
.RS 4
zero on failure, non-zero on success\&. On failure, you can find out what went wrong from \fBPHYSFS_getLastErrorCode()\fP\&.
.RE
.PP
\fBWarning\fP
.RS 4
Remember, PHYSFS_uint64 is only 32 bits on platforms without any sort of 64-bit support\&. 
.RE
.PP

.SH "Author"
.PP 
Generated automatically by Doxygen for physfs from the source code\&.