Quoting Jan Dubois <j...@activestate.com>: > I suspect that you are doing some operation that is not updating a file, > but deleting and re-creating it. This will always break hard links.
I went over my test methodology with a fine-tooth comb, and discovered that I had indeed messed up the order of operations. I was doing link-delete-link, when it should have been link-link-delete. PEBKAC strikes again. One thing I forgot to mention is that I ended up creating a function named safecopy(), because I wasn't happy with how the builtin copy() silently clobbers an existing "copy to" file -- which behavior link() very nicely does not exhibit. I was probably expending skull sweat on safecopy() when I overlooked my ordering problem. >> One final question: since symlinks were enabled in NTFS.sys v6.0 >> (Windows Vista) and above, is there any possibility that the builtin >> symlink() function can be made to silently Do the Right Thing on >> recent versions of Windows? > > Yes, there is, but I'm not sure it can still be done in time for > Perl 5.14. There is just one more 5.13.11 dev release planned for > March, and then 5.14 should come out in April/May, and new features > may no longer be allowed into the tree (besides I don't think I have > time to do this right away anyways). I'll keep a sharp eye out for Perl 5.42.... :-) Thanks again, -Brian _______________________________________________ Perl-Win32-Users mailing list Perl-Win32-Users@listserv.ActiveState.com To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
