in reply to what is bad scripting in windows based perl

The best facets of Perl work quite well on Windows. It's only when you start getting into the more escoteric vestiges of the language that you run into problems. Getting a process id, for example, is a breeze in Unix, but on Win32 platforms the same breeziness requires a module (Win32::Process).

Thread emulation, sendmail, and taint mode are other common sources of angst.

As tachyon points out, the docs are a good starting point. I've personally been rescued regarding specific issues on several occasions by the vast resources available with Super Search. If that fails, ask specific questions and provide code examples (use <CODE> tags). People here are very willing to help if you meet us half way and do a good job framing the question.

  • Comment on Re: what is bad scripting in windows based perl