🚀 go-pugleaf

yorkw@stable.ecn.purdue.edu (Willis F York) writes:
>Well Just my .02$, CED2.0 has a very nice rexx port.
>basicially every menu item can be asecced from REXX.
>by saying the name of the menu item, or the menu command,
>ie 
>menu(1,2,3)
>will select the 3 subitem of the 2 item on the first menu.

Ugh. That's a quick&dirty way to include REXX support, and it may have
advantages if all you want to do is automate sequences of things done from
the menus, but obviously any standard should use real command names like
cut, paste, move, etc.

(This is not a criticism of CED; given ASDG's reputation for setting and
following standards, I'm sure that when a standard does emerge, CED will
follow it.)

As Mike Meyer pointed out, simply taking every command that a program has
and creating an AREXX equivalent for it isn't a good way to develop a
standard.  Simple things like port name and command syntax conventions
should be relatively easy to agree on.  The hard part will be agreeing
on what commands should (and should not) be included in a standard.

--
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.