Re^4: Perl Scripts on systems without perl environments.

in reply to Re^3: Perl Scripts on systems without perl environments.
in thread Perl Scripts on systems without perl environments.

No. From Par's Faq:

On what platforms can I run PAR? On what platforms will the resulting executable run?

Win32 (with VC++ or MinGW), FreeBSD, NetBSD, Linux, MacOSX, Cygwin, AIX, Solaris, HP-UX, Tru64.

The resulting executable will run on any platforms that supports the binary format of the generating platform.

Update: You might remind them that IBM has published (I forget where) an End-Of-Support date of Dec. 31, 2006 for OS/2. So whatever solution you come up with will likely need to be changed in about a year.

"Cogito cogito ergo cogito sum - I think that I think, therefore I think that I am." Ambrose Bierce

Comment on Re^4: Perl Scripts on systems without perl environments.

Replies are listed 'Best First'.
Re^5: Perl Scripts on systems without perl environments. by Tanktalus (Canon) on Nov 07, 2005 at 21:44 UTC
IBM has published end-of-market date as December, 2005. Contract support will continue to 2007 or 2008. My guess is that if someone is actively deploying OS/2 for anything, they're paying for extensive support contracts, and this won't really bother them too much. IBM's withdrawal page. In case the OP's client isn't aware. (Unlikely.) Former member, Team OS/2. Which means pretty much nothing other than I still have an OS/2 server running at home... ;-)	[reply]
Re^6: Perl Scripts on systems without perl environments. by SkipHuffman (Monk) on Nov 07, 2005 at 23:16 UTC
This is not a new deployment. End of life cycle will last for several years though. Skip	[reply] [d/l]
Re^6: Perl Scripts on systems without perl environments. by SkipHuffman (Monk) on Nov 08, 2005 at 13:13 UTC
By the way, I also still have an OS/2 system. Two actually if you count the second partition on my main Linux system. OS/2 is still my favorite OS. C'mon IBM! Open Source it! Skip	[reply] [d/l]
Re^5: Perl Scripts on systems without perl environments. by SkipHuffman (Monk) on Nov 07, 2005 at 21:02 UTC
The end of support is exactly why this solution is being put into place. Then windows support is new and needs to have the same sort of automation that was available for the old OS/2 functionality. OS/2 has Rexx native, windows does not. So a change begins, and the two databases must be kept in sync until the OS/2 is gone. Oh, and that is an end of SALES support. You won't be able to buy new copies of OS/2 after that. IBM typically supports products for three to seven years after dropping sales. Skip	[reply] [d/l]
Re^6: Perl Scripts on systems without perl environments. by husker (Chaplain) on Nov 07, 2005 at 22:25 UTC
So what you really need is a Rexx-to-Perl converter. Develop in Rexx for OS/2 .. when it works, translate to Perl for the Windows platform, and run PAR on the result.	[reply]
Re^7: Perl Scripts on systems without perl environments. by parv (Parson) on Nov 08, 2005 at 00:42 UTC
That reminds there is/may be a Rexx-to-NetRexx converter; use NetRexx language to write (access) Java code (libraries) in Rexx.	[reply]

In Section Seekers of Perl Wisdom