Re: [ID 20000114.001] Perl rename function can delete files

[Jan Dubois <jand@ActiveState.com>]

On Thu, 20 Jan 2000 08:09:58 -0500, "Moss, Jeff" <jmoss@huffmancorp.com>
wrote:

>I really hadn't thought of this as a Microsoft bug.  The
>MFC doc says the MOVEFILE_COPY_ALLOWED mask uses CopyFile
>then DeleteFile.  So I guess it does what I expected it to.

It only uses CopyFile when the source and destination are not on the same
volume.

>I wasn't going to use the MOVEFILE_COPY_ALLOWED mask
>unless I was sure the new file name was on a different
>volume than the old file.

The problem isn't really the MOVEFILE_COPY_ALLOWED flag, but the
MOVEFILE_REPLACE_EXISTING one.  We want to use this bit to get consistent
behavior with the rename() function on UNIX, which will also potentially
delete the target file before doing the rename.

>I hadn't thought about UNC paths.

So it looks like a simple check for case insensitive equality is the best
we can do I guess.

-Jan

---

References to:

"Moss, Jeff" <jmoss@huffmancorp.com>

---

[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index][Thread Index][Top&Search][Original]

---