FILE_TEST

The FILE_TEST function checks files for existence and other attributes without having to first open the file.

Syntax

Return Value

FILE_TEST returns 1 (true), if the specified file exists and all of the attributes specified by the keywords are also true. If no keywords are present, a simple test for existence is performed. If the file does not exist or one of the specified attributes is not true, then FILE_TEST returns 0 (false).

Arguments

File

A scalar or array of file names to be tested. The result is of type integer with the same number of elements as File.

Keywords

BLOCK_SPECIAL (UNIX Only)

Set this keyword to return 1 (true) if File exists and is a block special device.

CHARACTER_SPECIAL (UNIX Only)

Set this keyword to return 1 (true) if File exists and is a character special device.

DANGLING_SYMLINK (UNIX Only)

Set this keyword to return 1 (true) if File is a symbolic link that points at a non-existent file.

DIRECTORY

EXECUTABLE

Set this keyword to return 1 (true) if File exists and is executable. The source of this information differs between operating systems:

UNIX: IDL checks the per-file information (the execute bit) maintained by the operating system.

Microsoft Windows: The determination is made on the basis of the file name extension (e.g. .exe).

GET_MODE

Set this keyword to a named variable to receive the UNIX style mode (permission) mask for the specified file. The bits in these masks correspond to those used by the UNIX chmod(2) system call, and are explained in detail in the description of the Mode argument to the FILE_CHMOD procedure. When interpreting the value returned by this keyword, the following platform specific details should be kept in mind:

The setuid, setgid, and sticky bits are specific to the UNIX operating system, and will never be returned on any other platform. Consult the chmod(2) man page and/or other UNIX programming documentation for more details.

The Microsoft Windows operating system does not have 3 permission classes like UNIX does. Therefore, IDL returns the same settings for all three classes.

The Microsoft Windows operating system does not maintain an execute bit for files, but instead uses the file suffix to decide if a file is executable.

GROUP (UNIX Only)

Set this keyword to return 1 (true) if File exists and belongs to the same effective group ID (GID) as the IDL process.

NAMED_PIPE (UNIX Only)

Set this keyword to return 1 (true) if File exists and is a named pipe (fifo) device.

NOEXPAND_PATH

Set this keyword to cause FILE_TEST to use the File argument exactly as specified, without applying the usual file path expansion.

READ

Set this keyword to return 1 (true) if File exists and is readable by the user.

REGULAR

Set this keyword to return 1 (true) if File exists and is a regular disk file and not a directory, pipe, socket, or other special file type.

SETGID (UNIX Only)

Set this keyword to return 1 (true) if File exists and has its Set-Group-ID bit set.

SETUID (UNIX Only)

Set this keyword to return 1 (true) if File exists and has its Set-User-ID bit set.

SOCKET (UNIX Only)

Set this keyword to return 1 (true) if File exists and is a UNIX domain socket.

STICKY_BIT (UNIX Only)

Set this keyword to return 1 (true) if File exists and has its sticky bit set.

SYMLINK (UNIX Only)

Set this keyword to return 1 (true) if File exists and is a symbolic link that points at an existing file.

USER (UNIX Only)

Set this keyword to return 1 (true) if File exists and belongs to the same effective user ID (UID) as the IDL process.

WRITE

Set this keyword to return 1 (true) if File exists and is writable by the user.

ZERO_LENGTH

Examples

result = FILE_TEST (!DIR + '/bin/bin.sgi', /DIRECTORY)  
PRINT, 'IRIX IDL Installed: ', result ? 'yes' : 'no'