SCOUG Logo


Next Meeting: Sat, TBD
Meeting Directions


Be a Member
Join SCOUG

Navigation:


Help with Searching

20 Most Recent Documents
Search Archives
Index by date, title, author, category.


Features:

Mr. Know-It-All
Ink
Download!










SCOUG:

Home

Email Lists

SIGs (Internet, General Interest, Programming, Network, more..)

Online Chats

Business

Past Presentations

Credits

Submissions

Contact SCOUG

Copyright SCOUG



warp expowest
Pictures from Sept. 1999

The views expressed in articles on this site are those of their authors.

warptech
SCOUG was there!


Copyright 1998-2024, Southern California OS/2 User Group. ALL RIGHTS RESERVED.

SCOUG, Warp Expo West, and Warpfest are trademarks of the Southern California OS/2 User Group. OS/2, Workplace Shell, and IBM are registered trademarks of International Business Machines Corporation. All other trademarks remain the property of their respective owners.

The Southern California OS/2 User Group
USA

SCOUG-Programming Mailing List Archives

Return to [ 20 | December | 2003 ]

>> Next Message >>


Date: Sat, 20 Dec 2003 14:08:35 PST8
From: Peter Skye <pskye@peterskye.com >
Reply-To: scoug-programming@scoug.com
To: scoug-programming@scoug.com
Subject: SCOUG-Programming: Blair Parses Rexx (was: 2004 Schedule)

Content Type: text/plain

Lynn H. Maxson wrote:
>
> Scheduled for January we have Bob Blair discussing
> REXX programming, specifically the parse operator.

Good, Bob has a lot of experience with Rexx, and Parse is one of Rexx's
assets.

I don't like Parse when Arg may be used instead. However, there are
some tricks which you can use with Parse (for example, use a character
other than a space for the delimiter) which are handy.

When you want the entire command line parameter string rather than the
individual parameters you should remember that the entire command line
ends up in arg(1) so you don't have to reassemble it from the Parsed
components (assuming you want the entire command line). Alternately
the Word() procedure might work better depending on your logic; I use
Word() because my command line parameters might occur in any order and I
need to process them one-at-a-time. And for called procedures the
individual parameters are already in arg(1) arg(2) etc so there's no
need to Parse.

Luckily Bob is way ahead of me and I'm sure he'll have some great tricks
for everyone. Parse can separate a drive letter from the directory path
in one statement and it can also split a time in HH:MM:SS format into
its respective components, again in one statement. It can similarly
speed up the parsing of email header lines, web log data and just about
everything else where you have a bunch of data in a single string with a
known format. I've had a heck of a time writing CONFIG.SYS processing
utilities and Parse with "=" as delimiter might be a good way to
separate a line's keyword from its designated value.

When has anyone needed PARSE VERSION?

- Peter

=====================================================

To unsubscribe from this list, send an email message
to "steward@scoug.com". In the body of the message,
put the command "unsubscribe scoug-programming".

For problems, contact the list owner at
"rollin@scoug.com".

=====================================================


>> Next Message >>

Return to [ 20 | December | 2003 ]



The Southern California OS/2 User Group
P.O. Box 26904
Santa Ana, CA 92799-6904, USA

Copyright 2001 the Southern California OS/2 User Group. ALL RIGHTS RESERVED.

SCOUG, Warp Expo West, and Warpfest are trademarks of the Southern California OS/2 User Group. OS/2, Workplace Shell, and IBM are registered trademarks of International Business Machines Corporation. All other trademarks remain the property of their respective owners.