On Windows, the path name to Perl is "controllable". Module names, etc are "controllable". By "controllable" I mean that this path can be specified at installation time. The path to user data is not "controllable" and the Perl code should work with any Windows path name to user data.

Unfortunately there are some "landmines" to be tripped over when trying to use the Windows "spaces allowed" names with Perl installation, library paths, module names,etc. I wish it wasn't so. I merely suggest that Windows users try to avoid installing their version of Perl into paths with spaces. This is a "your mileage may vary" situation.

I also find some of the *nix file name glitches amazing. I find more problems with Windows now, but that is just because I use it more not that *nix doesn't have problems too!