fix `rename-file-or-directory' docs to more accurately report OS behavior
This commit is contained in:
parent
045aac4daf
commit
723b41b3e6
|
@ -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,
|
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[new] cannot refer to an existing file or directory. Even if
|
||||||
@racket[exists-ok?] is true, @racket[new] cannot refer to an existing
|
@racket[exists-ok?] is true, @racket[new] cannot refer to an existing
|
||||||
file when @racket[old] is a directory, and vice versa. (If
|
file when @racket[old] is a directory, and vice versa.
|
||||||
@racket[new] exists and is replaced, the replacement is atomic in the
|
|
||||||
filesystem, except under Windows 95, 98, or Me. However, the check for
|
If @racket[new] exists and is replaced, the replacement is atomic
|
||||||
existence is not included in the atomic action, which means that race
|
under Unix and Mac OS X, but it is not guaranteed to be atomic under
|
||||||
conditions are possible when @racket[exists-ok?] is false or not
|
Windows. Furthermore, if @racket[new] exists and is opened by any
|
||||||
supplied.)
|
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
|
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
|
destination of the link, and it counts as a file for replacing any
|
||||||
|
|
Loading…
Reference in New Issue
Block a user