Rexx Is Still Strong After 25 years
therexxman writes "March marks the 25th anniversary of the Rexx programming language, and to celebrate the Rexx Language Association is hosting the 15th Annual Rexx Symposium at the IBM Research Labs in Boeblingen, Germany, from May 2 to 6, 2004.
Full details of the Symposium can be found in the 2004 Rexx Symposium Announcement.
Many of the world's 'Rexxperts' will be in attendance including Rexx's founder, Decimal Arithmetic guru, and IBM Fellow, Mike Cowlishaw."
Therefore I believe the Rexx is overrated and I would recommend against it. Just my two cents.
I'd never heard of REXX before. Looking at the FAQ, I found my explanation:
This FAQ is for REXX/MVS, that is, REXX for IBM mainframes (MVS, OS/390 and VM).
Okay... but is this language at the forefront of modern computing, or even close to it? That's not a cynical inquiry; I'd literally never heard of this language before and I'm curious to know whether it's making some kind of progressive, hidden impact that was just totally unknown to me.
Anyone? Anyone? Bueller?
The coolest voice ever.
This reminds me of wasting hours and hours on my Amiga500. Yeah, it only had 3MB of RAM and no hard drive, but give me a blitter chip and four channel audio any day! Anyway, there was a great version of Rexx for the Amiga that became the defacto scripting dialect of the day. Great stuff, that aRexx.
The CB App. What's your 20?
----------
Create a WAP server
It was funny then and it's funny now.
GET YOUR WEAPONS READY! --DR.LIGHT
I still use Kedit, a win32 programmer's editor, that uses Rexx as the macro language and it rocks (both the editor and the macro environment). Even though Mansfield software has quit supporting Kedit about a decade ago it is still the best editor on the windows platform. I tried switching several times - first to Brief then to Codewright and then Slick edit but came back to Kedit because of if clean interface and performance.
I send mansfield an e-mail every so often requesting a Linux version or ask to open source the code but they just ignore me. Kedit would be a good replacement for vi on linux.
Any other Kedit fans out there? BTW not to be confused with the KDE based editor by the same name.
I doubt whether academics see much to love in the language, but I always found it easy to learn and very effective in getting things done. On the few occasions I have used it in recent years, I have still considered it highly useable (and I speak as someone who has used Perl, Python, Lua and even occasionally Ruby).
I work at a back where we have a Siemens Mainframe (BS2000) and use Win 2000 machines with Logics (a terminal emulator for the 9720's BS2000 machines use).
...So it's nice to see REXX is still going :)
Back at Y2K when we didn't have too much to do (being at work only watching the blinkenlights) I wrote my own interface to BS2000 in REXX to bypass Logics.
Ok, the thing isn't perfect; the terminal emulation sucks (it's not 3270 and info is very hard to find). I never perfected it. The little REXX routines do their jobs well enough and I'm too lazy to beg Siemens for manuals which describe terminal emulation.
I now use cygwin and call REXX scripts from within a bash shell. A great way to automate lookups on the mainframe: the output of my REXX scripts gets redirected in cygwin and I can grep/awk/sed/perl for what I need.
On the other hand, as I pointed out in my speech that day, there was another new language coming up that was 20000% better. It was called Perl. Perhaps you've heard of it. :-)
I don't really agree here. REXX is a free form shell scripting language and stomps on everything else I have used for that purpose and that includes perl. You can write a simple sequence of commands with virtually no syntactic clutter and incrementally add expressions and control structures. With REXX, one can effortless take a program across the entire practical range of tranditional Unix shell languanges and far beyond.
Perl, of course, is more powerful but it is not really a shell language. It's syntax is more complex and gets in the way when you are trying to mix control code with command calls.
I still write bourne shell scripts. I also write awkward "shell" scripts in perl. But I would rather use REXX.
My first job. I wrote an Email System in Rexx for CMC ( had four IBM VM systems over the country linked together ). It was the first email system for a Company. Was better and faster then VM/Profs which IBM offered. Everyone used it for 5 to 6 years.
Go Rexx!! a great language for writing code.
WHen I started my first job , to work on Airline Applications - TPF based, on VM/CMS - I started using REXX. Then, at times, whenever I required a particular action on CMS file(s), I started writing REXX EXECs to do it for me. Although my demands were not that tough, as most of the times it was only to help me save my time while working, I found it extremely easy to write EXEcs. And I had no formal training in REXX. For me, its easy to understand the REXX commands/syntax. As I have no experience on Perl or whatever other stuff that you guys may be discussing, I am not in a position to compare REXX with anything else. But I like REXX and I am happy to see that it's still doing the job for me.
On the other hand, it also featured arbitrary precision mathematics, which is a pretty nifty and not altogether common feature for a language.
It's perfect, although somewhat slow, for working with very large integers. No special programming is required. Just add NUMERIC DIGITS 20 (for example) and you have 20 digit decimal numbers. It was very easy to translate an old program for Knuth's algorithm S (the spectral test) that once used UCSD Pascal's "long integers" (31 decimal digits + sign) into REXX.
Back then, when I was first working with REXX, my wife was finishing up her second Master's degree in Math. Her thesis involved some pretty hairy prime decomposition and polynomial factoring, and required some pretty high precision math. She had just discovered that PL/1 wouldn't be able to keep up, and I kept jokingly suggesting REXX. Instead of REXX, she went with Maple, an arbitrary precision math package from Waterloo, if I recall (the name seems like a good hint that it was Canadian).
Given that one of her more significant runs ended up tallying one CPU- Month on the Math Department's 780, I suppose it's just as well that she didn't use an interpreted language like REXX.
On the other hand, I remember discovering that REXX must have had some fairly smart tricks built in to its mathematical functionality. Back when I was doing OS/2 programming, awed by the awesome processing power of the 16Mhz 386, I exercised the OS/2 REXX interpreter by writing a teeny-tiny program to output the value of X raised to the X power, for a variety of different values of X. For X = 99, it took forever; on the other hand, for X = 100, it finished almost immediately. Like I said, someone put some smarts in there.
I've heard a lot of people saying good things about REXX. Sadly, it only took one bad experience to sour me to the language.
At CountryWide Home Loans there's a group that's responsible for transfering loan data between the branches and the AS400's. They use a commercial tool that has the option of firing off a program or script at a givien time, kinda like a weak cron.
So, long before I got there, someone said, "Hey, since we're running this on OS/2 we can use REXX for the new service management is asking for." Sadly, none of them were programmers. They added on parts based on when the script was run instead of what is did. Over the years, the whole systems grew into a self referential uneditable monster.
For those who don't know REXX, it defaults all variables to be the text of their names (eg. MYVAR would default to a value of "MYVAR"), REXX behaves like Perl without use strict (all typo's are new variables, initialized to their misspoelled names), and (just about)anything that doesn't parse to something meaningfull in the language is passed along into the shell. This lead to some of the most bizaar emergent behaviour I've ever seen.
Instead of failing completely and dieing a well deserved death, REXX allowed it to twitch on, destroying operators, programmers and management in its path. Add to that someone's brilliant idea to have it page the programmer whenever it idn't complete its task at 2:30AM (I inherited the pager the previous bastard hardcoded into the script).
Since then, I hear my old coworker recoded the entire thing, and it's now a beautiful machine that doesn't fail in any horrible way (if anyone could have done that with REXX, it was him). I don't know. I don't care. Once around the REXX monster is more than enough for me.
"One man can change the world with a bullet in the right place."
- Mick Travis, "If..."
From: ------- [KEDIT]
l e.pl?sid=04/0 3/24/0034224&mode=thread&t6 &tid=187
[mailto:------------]
Sent: Wednesday, March 24, 2004 1:00 PM
To: '------------'
Subject: RE: Kedit Port
Hi Steven,
Thanks for the link. It's nice to see that KEDIT still has admirers.
To correct a couple of points in the threads I looked at:
1) "I send mansfield an e-mail every so often requesting a Linux
version or ask to open source the code but they just ignore me."
We never ignore Linux/Unix version inquiries but there really haven't
been many over the years. We've been consistent in stating that we
have no plans for a Unix/Linux KEDIT. We've also been consistent in
stating that there are no open source plans.
1) "Mansfield software has quit supporting Kedit about a decade ago."
We still do support KEDIT for DOS, OS/2 and Windows. We essentially
don't sell KEDIT for DOS and OS/2 anymore since we ran out of manuals
some time ago and with sales of these versions so low, it wasn't cost
effective to print more. We sell license-only copies occasionally to
users who already know the product and need some more copies to be
legal. We're still selling KEDIT for Windows 1.5. We have no new
versions of KEDIT in the works though and perhaps this was what was
meant by the above comment.
Thanks again for the link. I only wish I had some better news for you.
------ -------
Mansfield Software Group, Inc
PO Box 532
Storrs CT 06268-0532 USA
Phone: 860-429-8402 x117 (M-F 8-5 EST)
Fax: 860-487-1185
Email: ----------------
Web: http://www.kedit.com
>
>>>>>>> Original Message: >>>>>>>
>
> FYI Scroll down to the post titled "Kedit and Rexx"
>
>
http://developers.slashdot.org/artic
id=126&tid=136&tid=15
>
> If you ever port kedit to Linux our department is good for 12
> copies....