I don't think the filesystem is relevant. It is true that on my Windows NTFS filesystem that the shell command "rename" will not rename OLDNAME to NEWNAME if NEWNAME already exists, but we're talking about Perl...
The perlfunc manpage entry for Perl's built-in rename() function says:
Changes the name of a file; an existing file NEWNAME will be clobbered.
and it's quite correct (I just tried it to make sure!).
Any more thoughts on my temporary file issue?
- Steve | [reply] |
I really never knew that. How dumb. Both my assumption in not checking what I knew could never be so and the logic that makes me wrong. You'll have to decide for yourself which is dumber:)
It will be a while before I stop thinking about the logic that allows a rename function to become a "delete target and then copy over" command.
You could consider this.
#! perl -slw
use strict;
use Win32::API::Prototype;
ApiLink(
'kernel32',
'UINT GetTempFileName(
LPCTSTR lpPathName,
LPCTSTR lpPrefixString,
UINT uUnique,
LPTSTR lpTempFileName
)'
) or die $^E;
my $tempFileName = ' ' x 254;
my $path = '.';
my $prefix = 'temp0000';
GetTempFileName( $path, $prefix, 0, $tempFileName ) or die $^E;
print $tempFileName;
After the above code has been run, the an empty file with the name returned will have been created. You can then open and use it as you need to.
Examine what is said, not who speaks.
"Efficiency is intelligent laziness." -David Dunham
"Think for yourself!" - Abigail
"Memory, processor, disk in that order on the hardware side. Algorithm, algoritm, algorithm on the code side." - tachyon
| [reply]
[d/l] |
