I normally develop perl code on unix system, but recently I've had to develop some applications that run on both unix & windows machines. My code goes through distinct development, testing, & operational stages on the same machine & standard (for us) programming practice is to keep all variables whose values are unique in these 3 environments in a file named env.pm. This allows us to deploy the same piece of software to any one of the 3 environments without having to change the core code.
We've done this with countless applications running on unix systems, but using the environment file fails under Windows. If I rename env.pm to something like penv.pm, everything is OK, but Windows seems unable to handle a file named env.pm. I suspect that there is a conflict with some other file named env.pm that is part of ActiveState's perl distribution. Can anyone advise?