Creates a symbolic linklink with its target set totarget as if by POSIXsymlink(): the pathnametarget may be invalid or non-existing.

Some operating systems require symlink creation to identify that the link is to a directory. Portable code should use(3,4) to create directory symlinks rather than(1,2), even though there is no distinction on POSIX systems.

[edit]Parameters

[edit]Return value

(none)

[edit]Exceptions

Any overload not markednoexcept may throwstd::bad_alloc if memory allocation fails.

[edit]Notes

Some operating systems do not support symbolic links at all or support them only for regular files.

Some file systems do not support symbolic links regardless of the operating system, for example the FAT system used on some memory cards and flash drives.

Like a hard link, a symbolic link allows a file to have multiple logical names. The presence of a hard link guarantees the existence of a file, even after the original name has been removed. A symbolic link provides no such assurance; in fact, the file named by thetarget argument need not exist when the link is created. A symbolic link can cross file system boundaries.

[edit]Example

#include <cassert>#include <filesystem>#include <iostream>namespace fs= std::filesystem; int main(){    fs::create_directories("sandbox/subdir");    fs::create_symlink("target","sandbox/sym1");    fs::create_directory_symlink("subdir","sandbox/sym2"); for(auto it= fs::directory_iterator("sandbox"); it!= fs::directory_iterator();++it)if(is_symlink(it->symlink_status()))std::cout<<*it<<"->"<< read_symlink(*it)<<'\n'; assert(std::filesystem::equivalent("sandbox/sym2","sandbox/subdir"));    fs::remove_all("sandbox");}

"sandbox/sym1"->"target""sandbox/sym2"->"subdir"

[edit]See also

• In other languages

• Español
• 日本語
• 中文