Bug #70869 for Perl-Critic: False Positive Package Declaration

I can't claim to speak for other developers, but my take on this is that it is a true positive. Perl requires that the file name be the same as the module name. You told perlcritic to analyze "file/glob.pm", and it found no 'package file::glob'. The fact that the file system merrily hands you the contents of "File/Glob.pm" when you ask for "file/glob.pm" does not change this, because it's still not portable. Perl itself behaves exactly the same way, as you can see from $ perl -Mfile::glob=bsd_glob -le 'for (bsd_glob( "*" ) ) {print}' Lest you think I'm unsympathetic because I'm a Unix geek, I type this on a machine running Mac OS 10.5, which displays exactly the same behavior. And there are times when I very much wish it were different. Try $ perldoc CPAN and $ perldoc cpan You get the documentation for the 'cpan' command for both, and so do I. A Unix person gets the documentation for CPAN.pm from the first example. I believe I have seen discussion among the Perl developers on this, but there has been no resolution. And, frankly, that's another reason the behavior of perlcritic will not be changed (by me, anyway) even if we grant that it's wrong: if the core Perl maintainers are not smart enough to sort this out, I'm certainly not. One of the issues, I believe, is that there is really no good way to tell whether you are dealing with a case-sensitive file system. Operating system does not tell you this. You or I could mount a disk having the Unix file system, and we would get 'file not found' in the example you submit. A Unix user could mount an NTFS, DOS, or HFS (the Mac OS native file system) disk, and get the same behavior we got.