Jump to content
We owe you an explanation.
July 6: An important update for readers in Japan.

You deserve an explanation, so please don't skip this 1-minute read. It's Monday, July 6. Our fundraiser won't last long, but fewer people are seeing our message this month and we might not hit our goal. If you've lost count of how many times you've visited Wikipedia this year, we hope that means it's given you at least ¥300 of knowledge. If everyone who finds Wikipedia useful gave ¥300, we'd hit our goal in a few hours.

It's been 25 years and Wikipedia is still free. It's still created by people, not machines, and we don't run ads or put up paywalls because we're not here to make a profit off your attention. In other words, it's still the internet we were promised.

Less than 2% of our readers donate, so if you've never given and Wikipedia has provided you with at least ¥300 worth of knowledge, donate today. If you are undecided, remember any contribution helps.

Proud host of Wikipedia and other free knowledge projects
How often would you like to donate?
Support Wikipedia year-round
Thanks for your generous support
Please select an amount (JPY)
The average donation in Japan is around ¥800.
  • Preferred Amount
Please select a payment method
Please select an amount (minimum ¥154)
We cannot accept donations greater than 3850000 JPY through our website. Please contact our major gifts staff at benefactors@wikimedia.org.
Please select a payment method
Can we follow up and let you know if we need your help again? The support and advice we get from donors in Japan is priceless, but many donors don't let us stay in touch. Will you commit today, this Monday, to staying in touch with the Wikimedia Foundation?
Sorry to hear that. We don't email often; would you consider changing your mind?
Thanks for changing your mind! We’ll respect your inbox.
Your information is handled in accordance with our donor privacy policy, and each email you receive will include easy unsubscribe options.
Please select an email option
Almost done: Please, make it  monthly.
Monthly support is the best way to ensure that Wikipedia keeps thriving.
How would you like to be reminded?
Whether you give now or later, any contribution helps. We can send you an email or text message reminder to join the 2% of readers who donate.
🎉 Thank you for donating recently! 🎉
Your support means the world to us. We'll hide banners in this browser for the rest of our campaign.
Where your donation goes
Accountability and transparency are core values at the Wikimedia Foundation. We manage funds and resources to ensure that every contribution supports our mission. We have earned the Platinum Seal of Transparency from Candid (formerly GuideStar), and Charity Navigator awarded us its highest rating. You can read our most recent annual report for more information about our financial health.
45% $85.4M Technology 32% $60.7M Support 12% $22.8M Fundraising 11% $20.9M General $189.7M Total Funding
45% Investment in Technology

Nearly half of our budget goes toward supporting the technology that powers Wikipedia and other Wikimedia projects. We are constantly working to enhance the user experience for both contributors and readers, improve site security, and ensure reliable access to our websites globally. This infrastructure and product support sustain one of the top ten most visited websites in the world, all at a fraction of the cost of popular for-profit websites.

32% Support for Volunteers

The global reach of Wikimedia projects is made possible by the hard work of volunteers from across the globe. We provide grants, legal support, and other resources to help build vibrant volunteer communities. Additionally, we promote community engagement through outreach initiatives and advocate for the growth and protection of free knowledge.

12% Allocation to Fundraising Efforts

Donor support is crucial to sustaining Wikipedia and our other free knowledge endeavors. Our team is committed to efficient and effective fundraising throughout the year, ensuring that every contribution helps advance our mission.

11% General and Administrative Expenses

Operational costs are essential for the smooth management and governance of the Wikimedia Foundation. These expenses help us recruit top talent and support staff around the world, empowering them to carry out the mission of the Wikimedia Foundation.

ARexx

From Wikipedia, the free encyclopedia
ARexx
Original authorWilliam S. Hawes
Release1987; 39 years ago (1987)
Written inMotorola 68000 assembly
Operating systemAmigaOS
PlatformAmiga
Included withAmigaOS 2.0
TypeRexx interpreter
LicenseProprietary

ARexx is a Rexx interpreter for Amiga, written in 1987 by William S. Hawes, with a number of Amiga-specific features beyond standard Rexx. An ARexx script can communicate with software that implements an ARexx port. An Amiga application can define a set of commands and functions for ARexx to address, thus making the capabilities of the software available to an ARexx script.[1] Several applications support running an ARexx script as a macro.

An ARexx script can execute commands and functions in multiple applications which allows a script to integrate the functionality of the applications. For example, an ARexx script could extract data from a database, insert the data into a spreadsheet to perform calculations on the data, then insert tables and charts based on the results into a word processor document.

ARexx allows a script to communicate with applications that are "ARexx compatible" able to receive commands from ARexx and execute them. Notable examples include: the MicroFiche Filer database application provides extensive ARexx commands, the Textra editor supplied with JForth provides an integrated programming environment, and the AmigaVision multimedia presentation application can control other programs via ARexx.

As in standard Rexx, ARexx uses typeless data representation. Other programming languages distinguish types such as integer, floating point, string, but Rexx treats all data as text (string). This makes writing code easier, but leads to runtime inefficiency and errors. As is often the case in dynamically scoped languages, variables are not declared before using them. They are created on first use.

ARexx provides built-in commands and access to its host Amiga library (rexxsyslib.library) as well as other libraries and functions. An Amiga program with an ARexx port can serve its functionality to an ARexx script. An ARexx script can invoke other ARexx scripts.

History

[edit]

ARexx was created in 1987, developed for 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.

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[3] editor, and was set in TeX using AmigaTeX.
This is a 100% Amiga product.[4]

As ARexx is written in 68000 assembly language, it cannot function at full speed with PPC CPUs of MorphOS, a more modern descendant of Amiga. ARexx has not been rewritten for them and is still missing from MorphOS. William Hawes is no longer involved in development of Amiga software and no firm is financing new versions of ARexx. Notwithstanding, the existing version of ARexx continues to be used, although not distributed with MorphOS.

Examples

[edit]

Implement new capabilities

[edit]

If a user is using a program which builds animations by joining various bitmap image files but which lacks image processing capabilities, they 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

Automate repetitive tasks

[edit]

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

Extend AmigaOS

[edit]

A significant value of ARexx is extending AmigaOS by adding capabilities it lacks. For example, a ARexx program could display a warning message or play an audio alert sound if a certain Amiga program stops, faults or has finished its scheduled job.

The following script is a ARexx script that displays warnings depending on events:

/* 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"

See also

[edit]

References

[edit]
  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. "Amazing_Computing_1986-03_067.JPG".
  4. ARexx Users Reference Manual
  5. Peruggi, Fulvio. "EqFiles".
  6. 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.
[edit]