std::experimental::filesystem::is_block_file (3) - Linux Manuals
std::experimental::filesystem::is_block_file: std::experimental::filesystem::is_block_file
NAME
std::experimental::filesystem::is_block_file - std::experimental::filesystem::is_block_file
Synopsis
Defined in header <experimental/filesystem>
bool is_block_file( file_status s ); (1) (filesystem TS)
bool is_block_file( const path& p ); (2) (filesystem TS)
bool is_block_file( const path& p, error_code& ec );
Checks if the given file status or path corresponds to a block special file, as if determined by the POSIX S_ISBLK. Examples of block special files are block devices such as /dev/sda or /dev/loop0 on Linux.
1) Equivalent to s.type() == file_type::block.
2) Equivalent to is_block_file(status(p)) or is_block_file(status(p, ec)).
Parameters
s - file status to check
p - path to examine
ec - out-parameter for error reporting in the non-throwing overload
Return value
true if the file indicated by p or if the type indicated s refers to a block device. The non-throwing overload returns false if an error occurs.
Exceptions
1)
noexcept specification:
noexcept
2,3) The overload that does not take a error_code& parameter throws filesystem_error on underlying OS API errors, constructed with p as the first argument and the OS error code as the error code argument. std::bad_alloc may be thrown if memory allocation fails. The overload taking a error_code& parameter sets it to the OS API error code if an OS API call fails, and executes ec.clear() if no errors occur. This overload has
noexcept specification:
noexcept
Notes
The information provided by this function is usually also provided as a byproduct of directory iteration. During directory iteration, calling is_block_file(*iterator) is less efficient than is_block_file(iterator->status())
Example
// Run this code
Possible output:
See also
status determines file attributes, checking the symlink target
symlink_status (function)
file_status (class)
status_known (function)