suzanne.soy/racket
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix `rename-file-or-directory' docs to more accurately report OS behavior

Browse Source
This commit is contained in:
Matthew Flatt 2011-01-13 14:08:34 -07:00
parent 045aac4daf
commit 723b41b3e6
1 changed files with 7 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
collects/scribblings/reference/filesystem.scrbl
View File

@ -248,12 +248,13 @@ directory (on the same disk) as well as rename a file/directory within
a directory. Unless @racket[exists-ok?] is provided as a true value,
@racket[new] cannot refer to an existing file or directory. Even if
@racket[exists-ok?] is true, @racket[new] cannot refer to an existing
file when @racket[old] is a directory, and vice versa. (If
@racket[new] exists and is replaced, the replacement is atomic in the
filesystem, except under Windows 95, 98, or Me. However, the check for
existence is not included in the atomic action, which means that race
conditions are possible when @racket[exists-ok?] is false or not
supplied.)
file when @racket[old] is a directory, and vice versa.
If @racket[new] exists and is replaced, the replacement is atomic
under Unix and Mac OS X, but it is not guaranteed to be atomic under
Windows. Furthermore, if @racket[new] exists and is opened by any
process for reading or writing, then attempting to replace it will
typically fail under Windows.
If @racket[old] is a link, the link is renamed rather than the
destination of the link, and it counts as a file for replacing any