develooper Front page | perl.perl5.porters | Postings from April 2007

Re: Bug in File::Find on Windows when target dir is bare drive letter and no_chdir = 1 [41555]

Thread Next
From:
Spiros Denaxas
Date:
April 3, 2007 13:22
Subject:
Re: Bug in File::Find on Windows when target dir is bare drive letter and no_chdir = 1 [41555]
Message ID:
bba689ec0704031322g6230d5camc54ce004dd5a76b6@mail.gmail.com
Hello,

The latest open bug review  contains an open bug regarding File::Find
and bare drive letters.
More info : http://rt.perl.org/rt3/Public/Bug/Display.html?id=41555

I am not convinced entirely that this can actually be considerd a bug
as is since 'c:' is not a valid path to begin with. Files and
directory on the NTFS filesystem are stored are record in a special
structure known as the Master File Table (MFT). The root directory of
a physical drive is in the MFT as a special record and not as a normal
directory. A quick look on the MFT records on my drive reveal that
most of them have a full path \foo\bar when defined, meaning the root
directory is always present in that definition as '\'.

In this context, using a bare drive letter does not make sense so I
what I humbly propose is for File::Find to issue a warning, prompting
the user to specify the full canonical path to the root dir (
drive_letter:\ ). Alternatively, the module could append the '\' when
a drive letter is used but i am not entirely sure if thats a good idea
or not thus i am more inclined towards the warning solution ( and
actually more than happy to implement, test and make a patch for it if
you agree ).

Apologies if i am talking nonsense,

Spiros

Thread Next


nntp.perl.org: Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at ask@perl.org | Group listing | About