> -----Original Message----- > From: Chas. Owens [mailto:[EMAIL PROTECTED] > Sent: 24 November 2008 20:18 > To: Jenda Krynicky > Cc: Perl Beginners > Subject: Re: perl version for windows > > On Mon, Nov 24, 2008 at 10:34, Jenda Krynicky <[EMAIL PROTECTED]> wrote: > > From: "Chas. Owens" <[EMAIL PROTECTED]> > >> 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. > > > > fork() and kill() is just as OS specific as Win32::Process is. One > > just got a builtin, the other did not. One presents itself as if it > > was general, the other says clearly it's OS specific. If you wrote a > > list of caveats from the point of a Win32 developer it would be just > > as long. And would list the same things, just with different wording. > > fork() is not THE or even THE ONLY way to create processes, it's THE > > UNIX way to create processes. > > I wasn't claiming that UNIX was the only way. I was calling bull on > Rob's claim " > 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." > > >> Then start to look at what > >> modules simply won't work on Win32 due to the lack of supporting > >> libraries. > > > > If you start your development on Unix, you notice the modules that > > work under Unix and do not under Win32 and never even notice those > > that work under Win32 and not under Unix. Besides, those that are > > Win32 specific prettymuch always say so in the name. The unix ones do > > not bother. "Everyone's using Unix and if he doesn't he bloody well > > should!" > > Well, I am a UNIX bigot, but the Win32 modules are tied to one OS > (well, one that is still in common usage, three in total), the modules > you are referring to work across many OSes; however, many of the them > require third party libraries that are simply not available on the > Win32 platform, that is not a problem with the module, it is a problem > of lack of availability of the library. > > Now I need to see if some of the Win32::* modules work with wine. > > > > >> 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). > > > > I've moved between California, Colorado, Kansas, North Carolina, > > Massachusetts and probably I couple I am forgetting and never had to > > change anything but a few addresse for snailmail. I have also visited > > France and it was an uphill fight. My gosh them bastards speak > > french! > > Exactly. Moving between UNIXes is easy (like moving between states in > the US). Moving outside of UNIX is much more difficult. Even when it > looks like it will be easy (US->UK), there are tons of gotchas (I need > to look up why they call apartments flats). > > > > -- > 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/ >
Flat as in no stairs Lol I made that up but it sounds crappy enough to be plausible Information in this email including any attachments may be privileged, confidential and is intended exclusively for the addressee. The views expressed may not be official policy, but the personal views of the originator. If you have received it in error, please notify the sender by return e-mail and delete it from your system. You should not reproduce, distribute, store, retransmit, use or disclose its contents to anyone. Please note we reserve the right to monitor all e-mail communication through our internal and external networks. SKY and the SKY marks are trade marks of British Sky Broadcasting Group plc and are used under licence. British Sky Broadcasting Limited (Registration No. 2906991), Sky Interactive Limited (Registration No. 3554332), Sky-In-Home Service Limited (Registration No. 2067075) and Sky Subscribers Services Limited (Registration No. 2340150) are direct or indirect subsidiaries of British Sky Broadcasting Group plc (Registration No. 2247735). All of the companies mentioned in this paragraph are incorporated in England and Wales and share the same registered office at Grant Way, Isleworth, Middlesex TW7 5QD. -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] http://learn.perl.org/
