home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.lang.rexx
- Path: sparky!uunet!wrkgrp!ets
- From: ets@wrkgrp.COM (Edward T Spire)
- Subject: Re: Capturing System Command Output (was: SH Backquote)
- Message-ID: <1992Sep1.145948.22780@wrkgrp.COM>
- Organization: The Workstation Group
- References: <1992Aug20.142314.19261@wrkgrp.COM>
- Date: Tue, 1 Sep 92 14:59:48 GMT
- Lines: 17
-
- ets@wrkgrp.COM (Edward T Spire) writes:
- :
- : AREXX does contain some features that do not conform to Cowlishaw's
- : rules. In some cases this is somewhat understandable, such as the
- : issue we're discussing here, where Cowlishaw gave no guidance, and each
- : implementer was forced to roll his own. In other areas (such as I/O)
- : Bill Hawes simply did something he thought was better than what
- : Cowlishaw had suggested. He may have been "right" about that, but it
- : is causing some problems in the ANSI REXX efforts.
-
- Someone just reminded me that AREXX I/O differs from the standard not
- because Bill just plain wanted to do something he thought was better,
- but because the only REXX model he had was CMS, so he had to roll his
- own I/O. If Bill had had a copy of "The REXX Language" in hand when
- he was writing AREXX, it may well have turned out quite differently.
-
- -Ed
-