home *** CD-ROM | disk | FTP | other *** search
- Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
- Path: sparky!uunet!paladin.american.edu!auvm!SERVER.UWINDSOR.CA!OPHOF
- X-Mailer: ELM [version 2.3 PL11]
- Message-ID: <9208260321.AA05688@SERVER.uwindsor.ca>
- Newsgroups: comp.lang.rexx
- Date: Tue, 25 Aug 1992 23:21:29 EDT
- Sender: REXX Programming discussion list <REXXLIST@UGA.BITNET>
- From: Scott Ophof <ophof@SERVER.UWINDSOR.CA>
- Subject: Blanks, REXX, and portability...
- Comments: To: REXX Discussion list <REXXLIST@uga.cc.uga.edu>,
- REXX on Unix discussion list <UREXX-L@Liverpool.ac.uk>
- Lines: 35
-
- Question: When are blanks not only the space character?
- Answer: In any case in Unix.
-
- In "The REXX Language" (Mike Cowlishaw) and most other REXX
- publications meant for CMS and equivs, the character known as
- "space" and the concept of "blanks" are used interchangeably.
-
- For CMS-REXX (and analogous implementations), this poses no
- problems. The space character is the *only* character defined
- as a "blank".
- (Note that I'm *not* talking about non-printable characters,
- and the space char *is* a printable character!)
-
- Under Unix however, the tab character (and some others) are
- considered "blanks", though it's called "whitespace" there.
- At least some REXX implementations for Unix recognize more than
- the space char as whitespace. And REXX on the PC recognizes at
- least the space char and the tab char as whitespace/blank...
-
- My point?
- I would hate to have to port to CMS any REXX program written for
- Unix (or PC); to have a program fail due to something like this
- would not be very easy to debug...
-
- My suggestion?
- In the interest of increasing the chance of successful porting, to
- request the ANSI-REXX committee to define that the *only* blank/
- whitespace recognized in standard REXX is the SPACE character (ASCII
- hex-20, EBCDIC hex-40).
-
- Your comments? :-)
-
-
- Regards.
- $$/
-