ActiveState is your friend. Do a PerlMonks search on "Win" to find a few of the gimmes'n'gotchas.
A few things you should be aware of:
- I don't know if Win95 is supported. I've only ever used ActivePerl on Win2000. Just letting you know.
- ActivePerl will do the right thing when it comes to filenames and directories. Use the Unix-style.
- she-bang options will work just fine. The Perl interpreter reads that line, even if Windows doesn't.
- You cannot bind STDIN and STDOUT under Windows. To get this behavior, you'll need to telnet to yourself. (If you don't know what I'm talking about, ignore it.)
- exec and system may or may not work as you expect.
The biggest thing to be aware of is that a lot of things that Unix lets you get away with, Windows won't. A lot of things Windows forces you to do may or may not break your Unix code. There is a way to tell what OS you're on, but I would be very careful about sprinkling your code with it. That's a good way to give yourself heartburn.