Apr 26, 2001, 2:55 AM
Post #12 of 14
Checking them visually isn't always enough and Perl won't catch all of your errors and warn you about them. The only way you'll know for sure if a script will crash a server is to run it.
I write CGI scripts all day every day and I still crash my server (LOCAL server) at least once a week (ok, maybe twice). If you're not crashing your server than you aren't writing enough code, or experimenting with new ideas. It's not a crime to crash your *LOCAL* server, all you have to do is restart it and you're up and running to crash it again. But it's NOT ok to crash a server that you share with others.
If you have any problems with the install you may also try idigo perl.
It's a complete package including perl, apache, and I believe, mod_perl. I've never used it but I've seen a lot of people recommend it and it looks like it would be easy to install.
You'll be much happier developing locally and everything will come together a lot quicker when you don't have to develop scripts using ftp and telnet.
If you have any problems, one of the first places I'd look is http://groups.google.com/ using Perl, Apache Windows, win98, etc. as keywords.
Personally, I have Perl, PHP, mySQL, ColdFusion, and three web servers (Apache 1.3.19, Apache 1.3.19 with mod_perl, PWS) running on Windows 98. I can develop Perl, PHP, mySQL on the Apache servers and Perl, PHP, ColdFusion, and ASP (VBScript, JScript) on PWS. I can even boot into Linux 7.1 if I want to work in that environment. It's not really that difficult to set up, it just takes a little time and effort.