ARexx

ARexx is an implementation of the Rexx language for the Amiga, written in 1987 by William S. Hawes, with a number of Amiga-specific features beyond standard REXX facilities. Like most REXX implementations, ARexx is an interpreted language. Programs written for ARexx are called "scripts", or "macros"; several programs offer the ability to run ARexx scripts in their main interface as macros.

ARexx can easily communicate with third-party software that implements an "ARexx port". Any Amiga application or script[1] can define a set of commands and functions for ARexx to address, thus making the capabilities of the software available to the scripts written in ARexx.

ARexx can direct commands and functions to several applications from the same script, thus offering the opportunity to mix and match functions from the different programs. For example, an ARexx script could extract data from a database, insert the data into a spreadsheet to perform calculations on it, then insert tables and charts based on the results into a word processor document.

History

ARexx was first created in 1987, developed for the Amiga by William S. Hawes. It is based on the REXX language described by Mike Cowlishaw in the book The REXX Language: A Practical Approach to Programming.[2] ARexx was included by Commodore with AmigaOS 2.0 in 1990, and has been included with all subsequent AmigaOS releases. This later version of ARexx follows the official REXX language closely; Hawes was later involved in drafting the ANSI standard for REXX.

ARexx is written in 68000 Assembly, and cannot therefore function at full speed with new PPC CPUs, a version of ARexx has not been rewritten for them and is still missing from MorphOS 3.0. William Hawes is no longer involved in development of Amiga programs and no other Amiga-related firm is financing new versions of ARexx. Notwithstanding this fact, the existing version of ARexx continues to be used, although it is not distributed with MorphOS.

From the ARexx manual:

ARexx was developed on an Amiga 1000 computer with 512k bytes of
memory and two floppy disk drives. The language prototype was
developed in C using Lattice C, and the production version was written
in assembly-language using the Metacomco assembler. The documentation
was created using the TxEd editor, and was set in TeX using AmigaTeX.
This is a 100% Amiga product.[3]

Characteristics

ARexx is a programming language that can communicate with other applications. Using ARexx, for example, one could request data from a database application and send it to a spreadsheet application. To support this facility, an application must be "ARexx compatible" by being able to receive commands from ARexx and execute them. A database program might have commands to search for, retrieve, and save data — the MicroFiche Filer database has an extensive ARexx command set. A text editor might have ARexx commands corresponding to its editing command set — the Textra editor supplied with JForth can be used to provide an integrated programming environment. The AmigaVision multimedia presentation program also has ARexx port built in and can control other programs using ARexx.

ARexx can increase the power of a computer by combining the capabilities of various programs. Because of the popularity of a stand-alone ARexx package, Commodore included it with Release 2 of AmigaDOS.

Like all REXX implementations, ARexx uses typeless data representation. Other programming languages made distinctions between integers, floating point numbers, strings, characters, vectors, etc. In contrast, REXX systems treat all data as strings of characters, making it simpler to write expressions and algorithms. As is often the case in dynamically scoped languages, variables are not declared before using them, they come into being on their first use.

ARexx scripts benefit from an error handling system which monitors execution and responds accordingly. The programmer can choose to suspend and resume the execution of the program as needed.

The ARexx command set is simple, but in addition to the commands there are the functions of its Amiga reference library (rexxsyslib.library). It is also easy to add other libraries or individual functions. ARexx scripts can also be invoked as functions from other ARexx scripts. Any Amiga program which has an ARexx port built in can share its functions with ARexx scripts.

Examples of ARexx solutions to common problems

Implementing new features and capabilities via scripts

If end user is using a program which builds animations by joining various bitmap image files but which lacks image processing capabilities, he could write an ARexx script which performs these actions:

  1. ARexx locates the image files in their directories
  2. ARexx loads first image
  3. ARexx loads paint program
  4. The image is loaded into paint program which performs modifications to file
  5. The modified image is stored into another directory
  6. ARexx repeats procedure on any image in the directory
  7. The paint program is closed and the animation program is loaded
  8. The animation is built
  9. The animation is saved in its directory
  10. The animation program is closed

Avoiding repetitive procedures

EqFiles.rexx[4] is a well-known example of a simple ARexx script written to automate repetitive and boring procedures. This script uses the ALeXcompare program [5] to compare files, and then finds all duplicates in a set of files and returns output by highlighting any results in a different color.

Expand AmigaOS capabilities

One of the main features of ARexx is the fact it could expand the capabilities of the AmigaOS by adding some procedures the OS lacked. For example, a simple ARexx program could be written to print a warning message on the screen of the monitor, or play an audio alert signal if a certain Amiga program stops, faults or has finished its scheduled job.

The following script is a minimal ARexx script that displays warnings depending on events that take place.

   /* Alarm.rexx */
   
   ARG event
   
   IF event = 0 THEN EXIT
   IF event = 1 THEN SAY "Program has ended unexpectedly"
   IF event = 2 THEN SAY "Program has finished its job"
   IF event = 3 THEN SAY "Cannot find data in selected directory"
gollark: In Minoteaur 7.1, you manage files from a thing underneath the `textarea` used for text editing.
gollark: However, where does the file upload thing go?!
gollark: The intention is that it is possible to conveniently edit elements of the list without having to switch to an editor view as you would for a text block.
gollark: So the content model rework thing means that pages can, instead of just being a text block, be a list of text things instead, displayed as a list.
gollark: Mi-note-eaur.

See also

References
  1. Giguere, Eric. "ARexx Command Hosts".
  2. Cowlishaw, Michael (1985). The REXX Language: A Practical Approach to Programming (1st ed.). Prentice Hall. ISBN 0-13-780651-5.
  3. ARexx Users Reference Manual
  4. Peruggi, Fulvio. "EqFiles".
  5. Kazik, Alex. "ALeXcompare".
Notes
  • Callaway, Merrill. (1992). The ARexx cookbook. Albuquerque, NM: Whitestone. ISBN 0-9632773-0-8.
  • Zamara, Chris; Sullivan, Nick (1991). Using Arexx on the Amiga. Abacus Software Inc. ISBN 1-55755-114-6.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.