Re: ActivePerl vs Perl on UNIX

Unless you are using:

WIN32-specific modules,
modules that are not installed on your UNIX box, or
WIN32 system calls

there should not be any syntax errors if it worked on Windows.

I often use ActivePerl on WIN32 and then transfer the files to UNIX. Mostly because I'm lazy and want the same scripts on both platforms.

Also, be sure to use Strict; and the -w flag. This way you can minimize other kinds of errors, or at least track them down a lot more easily.( I guess we can't say enough of this )

Mick

Comment on Re: ActivePerl vs Perl on UNIX

Replies are listed 'Best First'.
RE: Re: ActivePerl vs Perl on UNIX by Anonymous Monk on Jul 13, 2000 at 22:33 UTC
The differences between ActivePerl on Windows & Unix are unclear from the docs. How does an ActivePerl install under Unix (specifically Redhat6.x) and a plain perl source code recompile compare? Have they disabled the unix specific functionality as the FAQ described (IPC etc.) or does that section only apply to ActivePerl Win32?	[reply]
RE: RE: Re: ActivePerl vs Perl on UNIX by mrmick (Curate) on Jul 14, 2000 at 05:38 UTC
Although I haven't used ActivePerl for UNIX / LINUX, I can say with some degree of comfort that I don't think ActiveState would take away the power that is Perl. One of the great things about Perl is that, while you can write portable code, you can also take advantage of the platform it runs on. They would be doing Perl and themselves injustice if they took away useful features. Besides, it's Perl. Nothing will change that for now. Mick	[reply]