Am 19.10.2010 13:45, schrieb Steffen Mueller: > Hi Roderich, > > thank you, once again, for your analysis of the problem! > > Roderich Schupp wrote: >> The module's name is actually Socket.pm (not the uppercase S). >> Usually you'll get away with "use socket;" because of Windows' case >> insensitive >> filesystem. But not in this case (note that a packed executable is also >> a zip file, you can just run unzip etc on it): > > While it'd be nice to do the user-friendly thing and warn about such > issues whereever possible, I don't think this is a PAR bug. Loading a > module using the wrong name is an accidental "feature" of the module > loading mechanism. > > I vote "not a bug". > > --Steffen > > PS: IMNSHO case-insensitive file systems must die. >
Thanks for your clear analysis! That's exactly the problem - never thought about this. In the described case, "socket.pm" (wrong case) is required by a CPAN module which is not in my hand (so I can point with my fingers to others ;-) ... I agree completly with your conclusion: "case-insensitive file systems must die" -Johannes
