Object REXX

Object REXX

Paradigm	Multi-paradigm: object-oriented (class-based), procedural (imperative), structured
Designed by	Simon C. Nash (IBM)
First appeared	1988 (1988)
Stable release	5.0.0 / 10 May 2023 (10 May 2023)
Preview release	5.1.0
Implementation language	C++
Platform	IA-32, x86-64, ARM, s390x
OS	Cross-platform: Linux, Microsoft Windows, macOS, Solaris, OpenIndiana, AIX, FreeBSD, OS/2
License	CPL 1.0, GPLv2
Filename extensions	.rxs, .rex, .rexx, .cls
Website	www.rexxla.org
Major implementations
Object REXX (until 2004) ooRexx (since 2005)
Influenced by
Rexx, Smalltalk
Influenced
NetRexx

Object REXX is a high-level, general-purpose, interpreted, object-oriented (class-based) programming language.

It is a follow-on and a significant extension of the Rexx programming language (often called "Classic Rexx"). Object REXX retains all the features and syntax of "Classic Rexx" while adding full object-oriented programming (OOP) capabilities. Although Object REXX does not implement all aspects of the "Information Technology – Programming Language REXX" ANSI X3.274-1996 standard, it offers many new features of its own. Following its "Classic Rexx" influence, Object REXX is designed to be easy to learn, use, and maintain.

There are several object-oriented implementations of "Classic Rexx", including Open Object Rexx ("ooRexx") the open-source successor to Object REXX and the unmaintained Rexx Object Oriented ("roo!"), which was originally developed by Kilowatt Software.

History

In 1988, the "Oryx" project at IBM, under the technical direction of Simon C. Nash, experimented with merging "Classic Rexx" with the object model of Smalltalk. The motivation behind the project was to transfer the advantages of OOP to "Classic Rexx" while remaining compatible and thus transferring the usability of "Classic Rexx" to OOP. Early on, the projects focused on OOP aspect such as treating everything as an object, object-based encapsulation and message passing, object-based concurrency, classes and inheritance.

This initial work later led under the direction of Rick McGuire to the first prototype of Object REXX, which was presented in 1992. In 1994, IBM announced that Object REXX would replace "Classic Rexx" as the standard REXX interpreter in the next version of OS/2. In 1996, Object REXX was released as part of the OS/2 Warp 4 operating system. In 1997, versions for Windows 95, Windows NT and Linux followed. In 1999 an Object REXX version for AIX V4.1.5 or higher was released. In 2000, versions for zLinux and Sun/Solaris followed. For Windows 2000, Windows Me, Windows 98 and Windows NT 4.0, the last major update for Object REXX was released in 2001.

On 12 October 2004, IBM announced the discontinuation of Object REXX and transferred the source code and licensing rights to the non-profit Special Interest Group (SIG), the Rexx Language Association (RexxLA). The code that IBM released to open source did not include the classes for IBM System Object Model (SOM) and Workplace Shell (WPS) support. The OS/2 version of Object REXX includes classes to support SOM and WPS. These are also included OS/2's initial follow-on product, eComStation, and also in its current descendant, ArcaOS, for which IBM's original Object REXX interpreter continues to be available.

In 2005, the RexxLA released ooRexx as a new incarnation of Object REXX as free and open-source software under the Common Public License. This first version of ooRexx 3.0.0 has been heavily refactored compared to the original IBM source code in order to increase readability. Later, the ooRexx kernel was rewritten in pure C++, and a new architecture and native interface were designed and implemented under the technical direction of Rick McGuire. This work enabled the RexxLA to release ooRexx 4.0.0 with support for 64-bit in 2009. To this day, the RexxLA continues to develop, support and maintain ooRexx as well as "Classic Rexx" and NetRexx. Furthermore, the RexxLA organizes annual symposia.

Releases

The following table contains noteworthy features and changes of major Object REXX and ooRexx interpreter versions. All ooRexx releases and the necessary documentation are available on Sourceforge. For Arch Linux based distributions the current and the development version are available as Arch User Repository. Since version 5.0.0 there are portable versions of the interpreter that can be used without installation, and an unofficial port to OS/2 also exists. For Intellij IDEA, the ooRexxPlugin adds support for syntax highlighting, syntax checking, code completion and documentation support modeled after Javadoc using annotations.

Legend:

Old version

Old version, still maintained

Latest version

Latest preview version

Future release

Major Releases	Release Date	Notable Features and Changes
Old version, no longer maintained: Object REXX 1.0.0 (OS/2)	1996-09-25	First official release as part of OS/2 Warp 4
Old version, no longer maintained: Object REXX 1.0.0 (Windows)	1997-02-28 (IE) 1997-05-30 (DE)	First releases for Windows as "Interpreter Edition" (IE) and "Development Edition" (DE) DE additionally provides a dialogue class library, a graphical dialogue editor and a built-in tokeniser Provides structured programming constructs such as select, do loops, if-then-else branching and subroutine calls Provides array handling, arithmetic and other built-in functions Support for OOP concepts such as classes, object, methods, encapsulation, messaging, polymorphism, inheritance and multiple inheritance (metaclasses and mix-in classes) Includes interfaces to DB2, TCP/IP sockets and C/C++ applications
Old version, no longer maintained: Object REXX 1.1.0 (AIX)	1999-04-09	First release for AIX V4.1.5 Addition of an interface to the file transfer protocol
Old version, no longer maintained: Object REXX 2.1.0 (Windows)	2001-04-21	Support for Windows 98, Windows Me, Windows 2000, and Windows NT Support for Object Linking and Embedding/ActiveX, Windows Script Host (WSH) engine Support for Unicode functions and addition of mathematical function package Support for subroutine, procedure and function calls Support for stems and compound variables
Old version, no longer maintained: ooRexx 3.0.0	2005-03-30	First release of ooRexx as the open-source successor to Object REXX Supports 28 keyword instructions, four directives, 29 classes with associated methods and 75 built-in functions ooDialog 3.0.0 for creating graphical user interfaces on Windows systems Includes extension classes for mathematical calculation, dealing with TCP/IP sockets, regular expressions and the file transfer protocol Improved PDF documentation that supports links, meta information and document indexing
Old version, no longer maintained: ooRexx 3.1.0	2006-08-21	Various enhancements Separate documentation for ooDialog
Old version, no longer maintained: ooRexx 3.1.1	2006-11-23	Support for Linux, Windows, AIX and Solaris Additional functions for the RexxUtil library Additional methods for several classes Addition of CircularQueue class and associated methods
Old version, no longer maintained: ooRexx 3.1.2	2007-09-17	Added support for MacOS Additional methods for the MutableBuffer, String and Object classes Provides interface to Open Office
Old version, no longer maintained: ooRexx 3.2.0	2008-01-22	Several enhancements
Old version, no longer maintained: ooRexx 4.0.0	2009-09-30	Support for 64bit versions of Linux, AIX and Windows Improved C++ application programming interface Restructuring of ooDialog and addition of 7 classes and 24 methods Addition of Buffer, IdentityTable, Orderable, Package, Pointer, RexxContext, Routine, WeakReference and SocketClass classes and associated methods Addition of 17 samples to illustrate ooRexx concepts Separate documentation for Windows extension library Four new methods for the RexxQueue, three for the Object, four for the DateTime and one each for the Method, Stem and String classes The MutableBuffer class now supports most of the String class methods Addition of seven methods to the OLEObject class, responsible for the Object Linking and Embedding/ActiveX interface Drop support for the Windows Script Host (WSH) engine
Old version, no longer maintained: ooRexx 4.1.0	2011-09-28	Addition of File class including four new methods and 29 instance methods Addition of extension library for Unix systems (49 functions) Separate documentation for Rexx extensions library and Unix extensions library Addition of extension classes for handling the comma-separated values, multipurpose internet mail extensions and simple mail transfer protocol Addition of ooSQLite extension to create, modify, and query SQL based databases Enhancement of TCP/IP socket support Additional class and method for ooDialog Additional method for DateTime class
Old version, no longer maintained: ooRexx 4.2.0	2014-02-23	More than 43 enhancements Standalone installer for ooDialog 4.2.3 and several new classes and methods Separate documentation for ooSQLite external library Systemd support for Linux system and compliance with Linux Standard Base Add trace information about method invocations Additional method each for the String, Mutablebuffer, StackFrame, Queue and OrderedCollection classes Additional methods for the Relation class, several sorting methods for OrderedCollections and methods for inserting and deleting elements for the Array class
Current stable version: ooRexx 5.0.0	2022-12-22	A total of 86 new features and 76 enhancements Addition of several new keyword instructions and directives A total of 57 classes and associated methods Addition of AlarmNotification, Json, MessageNotification, RexxInfo, StringTable, StringTable and Validate classes and associated methods Additional methods for Alarm, Class, Collection, Directory, Message, Method, MutableBuffer, Object, Package, Routine, String and RxFtp classes Separate documentation for a) ooRexxUnit (unit testing framework), b) using ncurses for writing text-based user interfaces, c) the C++ application programming interfaces and d) explaining the release and build environment
Latest preview version of a future release: ooRexx 5.1.0	2024-09-19	Addition of the TraceObject class to support the tracing of multi-threaded programs

Design philosophy

ooRexx follows the design philosophy of "Classic Rexx" to create a "human-centered" programming language that is easy to learn, code, remember and maintain. This is achieved, in part, by keeping the language small and following the principle of least astonishment. A readable syntax is enabled by being case-insensitive, free-form, requiring as little punctuation as possible, and using instructions that are straightforward English. In addition, it is a dynamic programming language that offers flexibility and allows to focus on development rather than language constraints.

Following the "documentation before implementation" design principle of “Classic Rexx”, ooRexx offers comprehensive documentation in accordance with the IBM Style Guide that includes syntax diagrams and examples.

Instructions

As in "Classic Rexx", there are assignment instructions, keyword instructions and command instructions, and in ooRexx there are also the directive instructions. In line with the desire to keep the language small, there are only thirty keyword instructions in ooRexx 5.0.0. Unlike many other languages, no keywords are reserved, so there is no need to memorize a long list of reserved words. In cases where the string is neither an assignment nor a keyword instruction, it must be a valid expression and is considered a command instruction, which causes the interpreter to evaluate the expression and pass the value to the operating system for execution and set a variable RC for the return code. In addition, the ADDRESS instruction allows commands to be redirected to specific environments such as Bourne Shell, Bash, Z-Shell, Command Prompt and others, some editors including ISPF, TSO EDIT, XEDIT and its adaptations, as well as intercepting errors.

a = "hello world"                             /* assignment instruction       */
do i = 1 to 2                                 /* keyword instruction "DO"     */
  say "round #" i":" a                        /* keyword instruction "SAY"    */
end                                           /* keyword instruction "END"    */
"echo Hello World"                            /* command to operating system  */
say "RC:" rc                                  /* return code                  */

Free-form

ooRexx has a free-form syntax where the positioning of the program code is irrelevant, which allows a high degree of flexibility. Before execution, the interpreter merges multiple unquoted blanks into one, while a character string enclosed in quotation marks (single or double) is not changed. Concatenation can be requested explicitly with two vertical bars (||), or implicitly by separating terms with spaces or by abutting terms. Optionally, clauses can be spread over several lines by using the comma (,) or the minus sign (-) as a continuation character, or several clauses can be used in a single line, separated by a semicolon (;). Since a free-form language provides flexibility and requires fewer syntactic rules to be considered, it is assumed that it eases the learning effort by reducing the intrinsic cognitive load.

say   "Hello World!"                           /* output: Hello World!        */
say "   This"     'is' -                       /* minus sign for continuation */
        "REXX"   || "!"                        /* output:    This is REXX!    */

Case-insensitive

As "Classic Rexx", ooRexx is a case-insensitive programming language. The interpreter capitalizes all characters outside quotation marks before executing them. Because the cases do not need to be differentiated, fewer additional details need to be learned and frustrating syntax errors are avoided.

a = "This is REXX!"
Say A                                               /* output: This is REXX!  */
SAY a                                               /* output: This is REXX!  */

Everything is an Object

While "Classic Rexx" follows the "Everything is a String" philosophy and has string as its only data type, ooRexx considers everything as objects, including non-string objects such as arrays, streams and many more. Objects are manipulated using methods instead of traditional functions.

In ooRexx, a string variable is a reference to a string object and does not need to be declared, which reduces the effort for programmers compared to strictly typed languages. A string object can be of any length and contain any characters, including numerical values. It is therefore possible to change numerical values with string manipulations and methods of the String class. In addition, a string variable can contain any type of expression, including executable instructions, which can be evaluated or executed with the INTERPRET keyword instruction.

a = 2                                       /* string with numerical value    */
a = a || '0'                                /* string manipulation            */

counter = "do i = 1 to "a"; say i; end"     /* string containing instructions */
interpret counter                           /* interpret string: count to 20  */

Message paradigm

Similar to the messaging paradigm implemented by Alan Kay in Smalltalk, everything in ooRexx is an object that can be communicated with by sending messages naming a method. The notion of sending messages to objects as if they were living beings helps beginners to learn OOP concepts.

In contrast to Smalltalk, there is an explicit message operator, the tilde (~), where the receiving object is placed to the left of it and the result of the operation is returned. Sending a message leads to the activation of a method with the corresponding name and to the manipulation of the receiving object. Like Smalltallk, ooRexx messages can be cascaded if two tildes (~~) are used instead of one, returning the object that received the method rather than the result produced.

The default behavior of most methods can be changed by specifying an option, which can be either spelled out or abbreviated and is not case-sensitive. This enables a literal understanding and reduces the learning effort for beginners. For example the strip method by default removes leading and trailing blanks. This behavior can be changed, for example, by specifying "leading" or "l" as an option. While functions are nested in "Classic Rexx", messages can be chained in ooRexx, which improves the readability of a statement.

a = "   I am ooRexx!"
say a                                              /* output:    I am ooRexx! */
say a~Strip("Leading")                             /* output: I am ooRexx!    */
say a~strip("l")~reverse                           /* output: !xxeRoo ma I    */

Features

ooRexx is designed to retain all the features of "Classic Rexx". It conforms with the ANSI standard for the Rexx language (X3.274-1996, “Programming Language Rexx”) to ensure cross-platform interoperability with other compliant implementations. Thus "Classic Rexx" programs typically run under ooRexx without any changes. This makes it easy to transport both program code and developer knowledge from "Classic Rexx" to ooRexx. To this, ooRexx adds all the features of OOP, such as subclassing, polymorphism, and data encapsulation. Further features include multiple inheritance via mixin classes. The interpreter includes the rexxc utility, which makes it possible to translate programs into base64 encoding, a source-less file that starts faster since the initial parsing has already been done.

Parsing

The PARSE keyword instruction makes it possible to quickly and flexibly parse a string and assign parts of it to variables in a single step. Subsequent instruction is used to specify the source of the string, for example ARG for arguments that are listed when the program or function is called, VAR for variables, PULL for data queues or standard input (typically the keyboard), VALUE for any expression. When using VALUE, the WITH keyword is required to specify the end of an expression, followed by a parsing pattern. This pattern can be a list of variables, a position number or literal delimiters; it is possible to use these patterns in combination. Optionally, the upper and lower case of the string can be converted before parsing.

aString = "Person: Rick McGuire" 
parse value aString with type ":" first second   /* delimiter & variable list */
say first second                                 /* output: Rick McGuire      */

Routines

In addition to the three instruction types of "Classic Rexx", ooRexx adds directive instructions that allow the explicit definition of routines, classes, methods, attributes and others. Directive instructions are not executable, but define the execution environment, with the first directive marking the end of the executable part of a program. To make directive instructions readily recognizable, they are introduced with two consecutive colons (::).

Functions that are not specific to a particular class are organized with the ::ROUTINE directive. The CALL instruction can be used to invoke a routine. In addition, routines that return objects via the RETURN keyword instructions can be called using function calls by specifying the name of the routine followed by brackets in which arguments can be sent to the routine. The PARSE instruction can be used to parse the received arguments and assign them to variables.

call DoSomething                             /* call keyword instruction      */
Sum = ReturnObject("2","4")                  /* function call                 */
say Sum                                      /* output: 6                     */

::Routine DoSomething                        /* routine directive             */
  say "I did something!"                     /* output: I did something!      */

::Routine ReturnObject                       /* routine directive             */
  parse arg FirstVar, SecondVar              /* assign arguments to variables */
  Sum = FirstVar + SecondVar                 /* do calculation                */
return Sum                                   /* return result                 */

Classes and Methods

The ::CLASS directive followed by a class name causes the interpreter to define a new class. After the class name, options such as METACLASS, SUBCLASS, MIXINCLASS, ABSTRACT and INHERIT can be set in order to use OOP features. The ::METHOD directive can be used to define a new class method that is associated with the last ::CLASS directive. The ::ATTRIBUTE directive is used to define an accessor method that can retrieve or assign an object variable. Using the EXPOSE instruction, an object variable can be exposed to a method.

d = .dog~new("Bella")                             /* create and assign a dog  */
d~bark                                            /* send bark message        */
say d~name                                        /* output: Bella            */

::class dog                                       /* class directive          */
  ::Attribute name                                /* attribute directive      */
::method init                                     /* object initiation method */
  Expose name                                     /* exposes name of dog      */
  Parse arg name                                  /* assigns "Bella" to name  */
::method bark                                     /* method directive         */
  Expose name
  say Name "goes woof!"                           /* output: Bella goes woof! */

Packages

To facilitate the reusability of code, the ::REQUIRES directive allows to include another Rexx program, an external package or an external library. This directive is placed after the main code section and makes available every routine, class, method and object that specifies the PUBLIC option. External packages usually use the file extension .cls, for example ::requires "csvstream.cls" or ::requires "json.cls", and can be easily created. Some external packages and libraries are delivered with the ooRexx interpreter.

Multi-threading

Conceptually, ooRexx provides object-based concurrency, according to which objects have independent resources to execute methods and can communicate with each other using the messaging paradigm. Several objects can be active at the same time and exchange messages for synchronization. Concurrency can be achieved either with the REPLY keyword instruction, which causes an early return from a method while its remainder continues to execute in a new thread, with the GUARD keyword instruction, which can set a method as unguarded so that it can execute together with other methods of the same class, or by using the START method of the Object class, which causes the receiver to process the message in a separate thread.

Tracing

As in “Classic Rexx”, the TRACE keyword instruction and the built-in TRACE() function facilitate debugging, allow for control of the level of detail and enable interactive debugging at runtime. When interactive debugging, the interpreter pauses after most instructions that are traced. While multi-threaded programs can be traced, ooRexx 5.1.0 introduces as an addition the TraceObject class, which provides additional information such as the interpreter instance, the number of the thread on which the message is dispatched, and the state of the guard locks, allowing to judge which method is currently blocked.

Built-in functions and classes

While ooRexx is an extension of "Classic Rexx" with objects, classes and methods, the traditional built-in functions are still available and thus ensure compatibility. The ooRexx release 5.0.0 provides 82 built-in functions, including character manipulation, conversion and information functions, many of which call methods of the String class. In addition, the built-in dynamic link library RexxUtil offers 29 cross-platform, 25 Windows-specific and four Unix-specific functions for manipulating system files, directories, classes and objects.

ooRexx 5.0.0 contains a total of 57 built-in classes, which are divided into the class groups Fundamental, Stream, Collection and Utility.

Fundamental classes

Fundamental classes are the essential building blocks for all other classes. The Object class is the root of the class hierarchy, so that its methods and attributes are available for all instantiated objects of each class. The Class class acts as a factory that creates factories, which in turn create objects. Therefore, an instance of this class is created for each ::CLASS directive. The purpose of the Method class and Routine class is to create method or routine objects. The String class provides methods for handling strings, such as logical operations, concatenation, copying, joining, splitting, reversing, arithmetic, conversion and others. A Package class instance contains all created routines, classes and methods as well as manages external dependencies that are referenced by ::REQUIRES directives. The Message class enables the asynchronous sending of a messages, which enables the concurrent execution of methods.

Stream classes

Stream classes facilitate communication with external objects such as files, queues, serial interfaces, devices and others. The Stream class itself is a mixin class that can be inherited and is a subclass of the InputOutputStream, InputStream and OutputStream classes.

The Stream class provides methods for opening, reading, writing and closing streams as well as flushing buffers, setting the file location, retrieving information and other stream-related operations. While the OPEN method opens the stream, the ARRAYIN method can be used to read its content into an array object. The CLOSE method explicitly closes a stream before the stream object is reclaimed by the garbage collector.

StreamObj = .stream~new("someFile.txt")               /* create stream object */
StreamObj~open                                        /* open the stream      */
FileContent = StreamObj~ArrayIn                       /* read content         */
StreamObj~close                                       /* close the stream     */

say FileContent                                       /* outputs content      */

Collection classes

A collection is an object that contains multiple items with associated indexes that enable item to be retrieved using the AT or [] methods. There are MapCollection, SetCollection and OrderedCollection classes, all of which allow manipulation of a specific collection type.

The MapCollection class is a mixin class that defines the basic set of methods implemented by all collections that map from an index to a value. The Directory, StringTable, IdentityTable, Properties, Table, Relation and Stem classes inherit these methods. A Directory object is a collection of string indexes, while a StringTable object is a collection of unique string indexes. In an IdentityTable object, each item is associated with a single index, and there can only be one item for each index. The Properties object provides specific methods for saving and loading properties into files. Unlike a Table object, which cannot contain duplicate indexes, a Relation object is a collection in which elements can have the same index, which can be of any object type.

A Stem object is created automatically when a compound variable is used. As in “Classic Rexx”, such a variable consists of a stem and a tail, separated by a dot (.). While the stem must begin with a letter, the tail can be any character. Using a single numeric tail creates the same effect as an array, while multiple numeric tails can be used to create a multidimensional array.

fruits.1 = "Apple"                              /* assigning to stem variable */
fruits.4 = "Orange"                             /* assigning to stem variable */
say fruits.4                                    /* output: Orange             */
say fruits.[1]                                  /* output: Apple              */

SetCollections are special types of MapCollections where the index and the element are the same object. While the indexes in a Set object are unique, each index in a Bag object can appear more than once.

The OrderedCollection class is a mixin class that defines the basic methods for all collections that have an inherent index order, such as the List, Queue, CircularQueue and Array classes. A List object allows new items, for which a new index is created, to be added at any position in a collection. The associated index remains valid for that item regardless of other additions or removals. A Queue object allows items to be removed from the head and added to the tail or head of the queue. A CircularQueue object is a queue with a predefined size. Once the end of the circular queue is reached, new elements are inserted from the beginning to replace the previous items.

An Array is sequenced collection ordered by whole-number indexes. Like some other collection classes, the Array class provides the MAKESTRING method to encode its elements as a string object.

ArrayObj = .array~of("One", "Two", "Three")        /* array with 3 items      */
say ArrayObj~at(2)                                 /* output: Two             */
say ArrayObj~makeString(,"; ")                     /* output: One; Two; Three */

Utility classes

Utility classes are a collection of 31 classes that provide implementations for common tasks. The MutableBuffer class enables greater efficiency in string operations such as concatenation, as no new object needs to be assigned. The File class offers methods for all supported file systems, such as listing files in a directory or retrieving information about files and directories.

FileObj = .File~new("~/someUnixFolder/")     /* create file object for folder */
FileArr = FileObj~ListFiles                  /* retrieve array of files       */

do FilePath over FileArr                     /* go through array items        */
    say FilePath                             /* output: FilePath item         */
end

The DateTime or TimeSpan classes support the retrieval and formatting of a date, time or timestamp in various formats and enable arithmetic operations between them. Several Comparator classes facilitate sorting for built-in classes such as File, DateTime and others. The class Supplier and its subclass StreamSupplier enable the enumeration of an items collection together with an indexes collection. The Validate class provides methods that can be used to check whether given arguments are of the correct class and type, or within a numerical range. A VariableReference instance maintains a reference, while a WeakReference instance creates a reference to another object that is not pinned.

A regular expression is a pattern that can be used to match strings. To increase the readability of patterns in the code, the RegularExpression class allows the use of symbolic names encapsulated with colons (:) for common sets. For instance, matching a string containing only letters typically described as [A-Za-z] can be abbreviated using [:alpha:].

Other classes help to obtain information about the context of the currently executed code (RexxContext), the Rexx language or the executing platform (RexxInfo) and execution specifics (StackFrame) via environment symbols. The Buffer and Pointer classes are specifically designed to support writing methods and function in native code using the C/C++ APIs. Alarm and Ticker classes provide notification functions and EventSempahore and MutexSempahore classes implement synchronization mechanisms for multi-threading activities. The Monitor class enables messages to be forwarded to various target objects and the RexxQueue class provides object-like access to external Rexx data queues.

External packages and libraries

Using the ::REQUIRES directive and specifying the LIBRARY option, external libraries can be integrated per program. Such libraries are usually organized around domain-specific functions.

The Rexx extension library provides a class for reading and writing comma-separated values (CSV) files, for creating and processing JavaScript Object Notation (JSON) data and a sub-command environment that partially emulates a TSO/CMS environment. The RxSock library enables to incorporate TCP/IP protocols, while the RxFtp library specifically provides access to the file transfer protocol. The RxMath library offers advanced mathematical functions such as square root calculation, exponential function, logarithm, sine, cosine, tangent, arc sine and power calculation.

Say rxcalcsin(1)                                      /* output: 0.0174524064 */

::requires 'rxmath' LIBRARY

For Windows, ooRexx includes the ooDialog framework allowing to produce Windows dialogs and therefore graphical user interfaces. The ooRexx interpreter is delivered with several example programs and function packages that demonstrate the use of this framework. For POSIX-compatible operating systems, the orxnCurses class library enables the writing of text-based user interfaces using the ncurses programming library. The RxUnixSys library provides functions on most Unix systems for interacting with processes and threads, users and user groups, files and file systems and other.

Many of these external packages and libraries are also compatible with other Rexx implementations.

Bridges

While ooRexx compared to Object REXX no longer contains classes for SOM and WPS support, it offers application programming interfaces (APIs) for interacting with code written in C or C++. There is also an external library that implements a bidirectional Java bridge, which enables interaction between ooRexx and Java. Furthermore, classes are provided that enable the automation of Windows applications. The ooSQLite class provides an interface to SQLite, an in-process library that implements a self-contained, serverless, zero-configuration, transactional SQL database engine.

C/C++ APIs

As "Classic Rexx", ooRexx includes APIs for extending Rexx with applications written in C and vice versa. This enables the creation of handlers for subcommands used in Rexx programs that run as application macros, external functions that allow a direct extension of the ooRexx function set and system functions that allow the behavior of the interpreter to be customized.

With ooRexx 4.0.0 APIs have been introduced that allow C++ applications to extend ooRexx and vice versa. This includes handlers for methods and functions written in C++ that extend ooRexx, both packaged as external libraries. These are dynamic link libraries on Windows or as shared libraries on Unix-based systems. An external library can be loaded with the ::REQUIRES directive or by using the EXTERNAL keyword instruction as part of a ::ROUTINE, ::METHOD, or ::ATTRIBUTE directive.

Java

Using the C++ APIs, BSF4ooRexx is a bidirectional Java bridge based on the Bean Scripting Framework that allows ooRexx to communicate with Java objects and enable Java to interact with Rexx applications. The bridge is realized by requiring the ooRexx package BSF.CLS, which defines public routines, classes and the environment symbol .BSF4REXX. Examples are provided for the use of Java classes in connection with AWT, Swing, JavaFX, JDBC, Java 2D and some others.

.bsf~new('java.awt.Frame', 'Frame from ooRexx.')~show   /* create Java object */
call SysSleep 10

::requires BSF.CLS                                      /* get Java support   */

Based on BSF4ooRexx, interaction with Universal Network Objects (UNO), as used in OpenOffice and LibreOffice, is supported via the UNO.CLS package. In addition, the CLR.CLS package together with Jini4Net enables the use of the .NET framework. Communication with processes via the D-Bus middleware under Linux is possible using the DBUS.CLS package.

Windows automation

The Windows extension includes the Windows Script Host (WSH) Scripting Engine that can be used to perform general automation tasks. It also includes Object Linking and Embedding/ActiveX (OLE) support allowing to interact with Windows programs via the OLEObject. OLE Automation is an inter-process communication mechanism developed by Microsoft that is based on a subset of the Component Object Model (COM) and enables, among other things, the invocation of program functions, the querying and setting of attributes and the interception of component events. The ooRexx interpreter includes examples that demonstrate some features of WSH, interaction with Access, Word, Excel and other programs via OLE, and a utility to browse available OLE objects.

excelApp = .OLEObject~new("Excel.Application")     /* create object for Excel */
excelApp~visible = .true                           /* make Excel visible      */
Worksheet = excelApp~Workbooks~Add~Worksheets[1]   /* add worksheet           */
Worksheet~cells(1,1)~Value = “First Cell”          /* insert string into cell */

In addition to OLE support, the Windows extension enables interaction with the Windows program manager, the system event log, the clipboard and the registry as well as to query, edit and interact with windows, menus or sub-menus.

See also

• Comparison of programming languages
• Timeline of programming languages
• REXX
• NetRexx

Further reading

• Ashley, W. David; Flatscher, Rony G.; Hessling, Mark; McGuire, Rick; Peedin, Lee; Sims, Oliver; Wolfers, Jon (2022). ooRexx Documentation 5.0.0 Open Object Rexx Reference (PDF). RexxLA.
• Ashley, W. David; Flatscher, Rony G.; Hessling, Mark; McGuire, Rick; Peedin, Lee; Sims, Oliver; Wolfers, Jon (2022). ooRexx Documentation 5.0.0 Programmer Guide (PDF). RexxLA.
• Ashley, W. David; Flatscher, Rony G.; Hessling, Mark; McGuire, Rick; Peedin, Lee; Sims, Oliver; Sims, Oliver; Wolfers, Jon (2022). ooRexx Documentation 5.0.0 Windows Extensions Reference (PDF). RexxLA.
• Ashley, W. David; Flatscher, Rony G.; Hessling, Mark; McGuire, Rick; Peedin, Lee; Sims, Oliver; Wolfers, Jon (2022). ooRexx Documentation 5.0.0 Application Programming Interfaces (PDF). RexxLA.

External links

• Rexx Language Association
• Open Object Rexx 5.0.0 documentation
• Open Object Rexx on Sourceforge
• Open Object Rexx Website
• Open Object Rexx on Rosetta Code
• BSF4ooRexx on Sourceforge