std::filesystem::is_block_file (3) - Linux Manuals
std::filesystem::is_block_file: std::filesystem::is_block_file
NAME
std::filesystem::is_block_file - std::filesystem::is_block_file
Synopsis
Defined in header <filesystem>
bool is_block_file( std::filesystem::file_status s ) noexcept; (1) (since C++17)
bool is_block_file( const std::filesystem::path& p ); (2) (since C++17)
bool is_block_file( const std::filesystem::path& p, std::error_code& ec ) noexcept;
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
2) The overload that does not take a std::error_code& parameter throws filesystem_error on underlying OS API errors, constructed with p as the first path argument and the OS error code as the error code argument. The overload taking a std::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. Any overload not marked noexcept may throw std::bad_alloc if memory allocation fails.
Example
// Run this code
Possible output:
See also
status determines file attributes
symlink_status determines file attributes, checking the symlink target
(C++17)
(C++17)
file_status represents file type and permissions
(C++17)
status_known checks whether file status is known
(C++17)
is_character_file checks whether the given path refers to a character device