On Sun, Nov 23, 2008 at 19:39, Rob Dixon <[EMAIL PROTECTED]> wrote: snip >> All Perl functionality works on UNIX. Some Perl functionality does >> not work on Windows. > > No, not all Perl functionality works on all Unix platforms. You are as likely > to > find a compatibility issue moving from one Unix to another Unix as from Unix > to, > say, VMS or Windows. > > It is misleading to suggest that Perl on Unix is fine, and Perl anywhere else > is > risky. It is usually a simple matter to write portable software, as described > in > > perldoc perlport snip
Alright, I have to call bull on this. There are a total three functions that may not behave in the expected way between the UNIXes: atan (HPUX does some non-standard things), sockatmark (it is fairly new and may not exist on some UNIXes), and system (Does not automatically flush output handles on some platforms). Compare that to Win32; I lost count of the caveats and warnings after thirty or so. The big ones being fork, open, and kill. Then start to look at what modules simply won't work on Win32 due to the lack of supporting libraries. I have moved Perl scripts amongst HP-UX, AIX, Solaris, multiple flavors of Linux, various BSDs, OS X, and probably a couple I am forgetting and never had to change anything but a few arguments to external commands. I have also ported Perl code to a few Win32 platforms (Win9X, WinNT, and WinXP) and it was generally an uphill fight (mostly due to the lack of support for modules, but also because of the whole drive letter crap). -- Chas. Owens wonkden.net The most important skill a programmer can have is the ability to read. -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] http://learn.perl.org/
