Path: utzoo!censor!geac!torsqnt!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!unix.cis.pitt.edu!dsinc!ub!uhura.cc.rochester.edu!rochester!kodak!sisd!jeh From: jeh@sisd.kodak.com (Ed Hanway) Newsgroups: comp.sys.amiga.tech Subject: Re: REXX command standards Message-ID: <1990Nov16.131723.9688@sisd.kodak.com> Date: 16 Nov 90 13:17:23 GMT References: <1990Nov12.224249.18759@sisd.kodak.com> <533@epicb.com> Sender: news@sisd.kodak.com Organization: Printer Products Division Eastman Kodak Lines: 19 cimshop!davidm@uunet.UU.NET (David S. Masterson) writes: >Could somebody enlighten a novice? What would standardizing the AREXX >commands buy you? The basic AREXX commands (those that aren't sent out of >AREXX) are already standard and the commands sent to application ports would >have requirements based on the application. Currently, commands sent to application ports are unique to each program, but many programs do much of the same thing. Let's say I wanted an AREXX program to run from an fkey in my editor that would get the current word under the cursor and use it look for a manual page in my man: directory, displaying it in a new window of my editor. The basic flow of the program is the same no matter what editor I use, and any editor worth using has the ability to do this with AREXX, but I'd need one version if I used CEDpro, another for LSE, another for TxEd, another for QED, ad nauseum. -- Ed Hanway --- uunet!sisd!jeh Use other side for additional listings. Some assembly required. Any resemblance to real persons, living or dead, is purely coincidental.