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.
