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: PARSE wishlist/brainstorming
- Message-ID: <1992Aug21.153953.796@wrkgrp.COM>
- Organization: The Workstation Group
- References: <ANDERS.92Aug21003253@lise4.lise.unit.no>
- Date: Fri, 21 Aug 92 15:39:53 GMT
- Lines: 35
-
- anders@lise4.lise.unit.no (Anders Christensen) writes:
- : In article <1992Aug20.154822.8057@hou.amoco.com> zjlc12@hou.amoco.com (Jerry Campbell) writes:
- :
- : > Why not add the STEM keyword to the Parse instruction?
- : > Parse Var data STEM "hello" 1 stem. +3
- :...
- : Btw also files and stems could be used in the same way, instead of the
- : stack:
- : ADDRESS 'uni-shell' 'ls -l' TO STEM lines.
- : do i=1 to lines.0
- : parse var lines.i perm.i . user.i size.i . . . filename.i .
- : end
- :...
- : If what you want to do, is to put the output of 'ls' into a stem named
- : "record.", why not the following syntax?
- : ADDRESS 'uni-shell' 'ls' TO STEM records.
-
- At the last ANSI discussion the "users" all liked these kinds of
- suggestions, i.e., making formal within the language definition the
- kind of numerically based stem collections that are commonly used
- in many programming applications. The "implementers" in the group
- were not so sure that we could jump right into that without due
- consideration of the side effects.
-
- I would not be a good person to discuss the possible side effects
- (I was on the side of the "users" in this...)
-
- Do we have a volunteer to present the counter-arguements?
-
- ========================================================================
-
- Ed Spire email: ets@wrkgrp.com (on uunet)
- The Workstation Group voice: 800-228-0255
- 6300 River Road, Suite 700 or 708-696-4800
- Rosemont, Illinois 60018 fax: 708-696-2277
-