home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.lang.rexx
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!att!princeton!pucc.Princeton.EDU!PNNTEST
- From: TDTRUE@pucc.Princeton.EDU
- Subject: Re: Blanks, REXX, and portability...
- Message-ID: <168518812.PNNTEST@pucc.Princeton.EDU>
- Originator: news@nimaster
- Sender: news@Princeton.EDU (USENET News System)
- Nntp-Posting-Host: pucc.princeton.edu
- Organization: Princeton University
- References: <9208280337.AA23023@SERVER.uwindsor.ca>
- Date: Fri, 28 Aug 1992 13:40:19 GMT
- Lines: 26
-
- I'm lost at this point, partly because we're talking about two
- distinct questions. The one is, "What character or characters can
- delimit a word?", the other is, "Should a literal blank represent
- more than a single kind of space?"
-
-
- In the first, it seems to me that you want to pick out what you
- regard as a word; what separates words should make no difference.
- The CMS version of REXX could even benefit from an OPTIONS parameter
- to modify this. I've been bit once or twice trying to parse CP
- output that contained a new line (x'15'). The translate function
- is useful in this case, but on other systems letting a word be a word
- makes more sense.
-
- The other question is illustrated by Eric's question. It seems to
- be that in PARSE and elsewhere a literal string should only match
- a single character string; literal blank should match just one
- character. If you need to match on more than a single character,
- then 'PARSE' needs to be extended, but not just to handle multiple
- meanings for a blank.
-
- Tom True
- Princeton University
- CIT - Advanced Applications
- TDTRUE@PUCC.PRINCETON.EDU
- (609) 258-6064
-