Re: namespaces that differ only in case
[email protected] (Eric Wilhelm)
| Newsgroups | perl.cpan.workers |
|---|---|
| Message-ID | <[email protected]> |
# from Alexandr Ciornii
# on Sunday 01 April 2012 04:10:
>> Perfectly distinct. Get similar results for attribute vs Attribute.
>
>Possibly difference is in using Windows.
>
>cpan> m integer
>...
> INST_FILE C:\strawberry514\perl\lib\integer.pm
>
>cpan> m INTEGER
>...
> INST_FILE C:\strawberry514\perl\lib\INTEGER.pm
The uppercase INTEGER.pm does not actually exists (even though the
broken fs is saying yes to -e)? If so, this is a bug in the cpan shell
(albeit one which requires a big workaround to deal with the broken
fs.)
Does this then mean that the Class-PObject distribution somehow get
accidentally installed during a routine update?
As for those who would claim that a case-insensitive filesystem is not
broken, they will kindly explain how it could possibly be correct
behavior to arbitrarily substitute the character 3 for the character 5
(or to see it another way: removing 26 characters from the set.)
Perhaps ExtUtils::Install should refuse to overwrite a file of differing
case?
--Eric
--
"Beware of bugs in the above code; I have only proved it correct, not
tried it."
--Donald Knuth
---------------------------------------------------
http://scratchcomputing.com
---------------------------------------------------