30 seconds or less, depending on your hardware!
Only if you are upgrading to a newer version.
IBM's Object REXX was available in two formats; an Interpreter Edition and a Development Edition. ooRexx will be available in one format which is half way between the two IBM offerings.
There will be no functional difference between the Object REXX and ooRexx interpreters; code written for Object REXX will work with ooRexx with the following minor exceptions related to product versioning:
OBJREXX 6.00 dd mon yyyyThe result from PARSE VERSION using the first version of ooRexx is:
REXX-ooRexx(MT) 6.00 dd mon yyyyThis change was done for two reasons; the first is that ooRexx is a different product, and the format of the result is now ANSI compliant.
IBM Object REXX Interpreter Version 2.1.3 Build date: Mar 31 2004 Copyright (c) IBM Corporation 1996, 2004. All Rights Reserved.The output from rexx -v using the 3.1.1 version of ooRexx for Linux is:
Open Object Rexx Interpreter Version 3.1.1 for LINUX Build date: Nov 13 2006 Copyright (c) IBM Corporation 1995, 2004. Copyright (c) RexxLA 2005-2006. All Rights Reserved. This program and the accompanying materials are made available under the terms of the Common Public License v1.0 which accompanies this distribution. http://www.oorexx.org/license.html
Due to licensing issues related to components of Object REXX, not all portions of the developer edition were made available to RexxLA. Therefore the following components are not available in ooRexx:
Due to licensing issues mentioned above, the rxftp function package is not available. For this reason ooRexx supplies a full (and more powerful) replacement in the form of the easy to use rxFtp class which is fully documented in the rxftp.pdf document or as an HTML document.
The differences with the versioning details as described in the Windows differences above is also applicable to these ports.
ooRexx for AIX is available starting with the 3.1 release.
The source code provided to RexxLA was maintained by one group of IBM developers. The source code for OS/2 is maintained by a different group of IBM developers, and that source code base was not supplied to RexxLA.
Any POSIX-based, Un*x-like platform is likely to already be available in the source distribution due to the use of the autoconf toolset. If not, then support for the particular platform will need to be implemented in a future version of ooRexx.
Now the initial release of ooRexx has been made and the source code made publically accessible via SourceForge's CVS servers, ooRexx Development Team, will be accepting submissions for changes and expanding the devlopment team with suitably enthusiastic and qualified developers to assist in the future development of ooRexx.