Win2k and ActiveState Perl

blackjudas has asked for the wisdom of the Perl Monks concerning the following question:

What's the success rate on the combination of Perl and Win2k in a production environment, offering both Linux and Win2k solutions for both production and development environments is my hope for the near future. I've never used perl on Win32 systems. Therefore what kind of major snags and differences between the UNIX and WIN environments should I expect?

I realize that this may be a FAQ, but a smooth transition (to running both) is what I hope for, and who better to ask than the "experienced" ones.

Any good documentation anyone can point me to? Not the docs that come with the distros, but some experiences others may have had in using Win2k and Perl on a production machine?

BlackJudas

Comment on Win2k and ActiveState Perl

Replies are listed 'Best First'.
Re: Win2k and ActiveState Perl by LD2 (Curate) on Oct 05, 2001 at 10:49 UTC
Take a look at this node: Platform Differences - it'll give you some ideas on the differences between Win32 and Unix.	[reply]
Re: Win2k and ActiveState Perl by John M. Dlugosz (Monsignor) on Oct 05, 2001 at 19:04 UTC
The file ActivePerl-Winfaq5 that comes with ActiveState Perl includes the following topics: Certain functions don't seem to work on ActivePerl. The exec function doesn't seem to work under Perl for ISAPI, Perl for WebSite, or PerlScript. Why not? What's the history of ActivePerl? What's the difference between running ActivePerl on Windows NT Why don't the examples from the Camel book work? Why don't certain standard library modules work? How do I make a UNIX-based script work? How does the chmod function work on Win32 platforms? 4DOS doesn't recognize \" on the command line. STDIN and STDOUT, and Piping don't always work on NT. Why doesn't signal handling work on Windows.	[reply]