Anonymous user
Rosetta Code:Village Pump/Dialects: Difference between revisions
Rosetta Code:Village Pump/Dialects (view source)
Revision as of 22:08, 15 August 2012
, 11 years ago→REXX and o-o REXXes: corrected a misspelling. -- ~~~~
Walterpachl (talk | contribs) mNo edit summary |
m (→REXX and o-o REXXes: corrected a misspelling. -- ~~~~) |
||
(4 intermediate revisions by 2 users not shown) | |||
Line 54:
Some 'features' of the original Rexx were removed '''in this grandchild (ooRexx)'''
:- Use of @#$¢ as or in symbols
:- a= as a short form
:- Multi-line strings (extending a string over line boundaries)
:- stream I/O (present in CMS but only optional on TSO (not on 'mine')▼
:: (on TSO I have to use EXECIO)▼
:- Bifs: externals, find, index, justify, linesize
:- the Upper instruction
:- /= and /== as alternatives to \= or \== (see characters below)
Other features were introduced '''with the ANSII standard''' created
by a committee comprising Rexx implementers from IBM (notably the
original author, Mike Cowlishaw) and from elsewhere:
:- Date and Time conversion
:- Parse Caseless
:- Address With (not available in ooRexx)
:- Bifs: changestr, countstr, qualify
A feature introduced with ooRexx (and Regina unless you opt out, see below)
Line 76 ⟶ 77:
Avoiding all of the language elements mentioned above makes a program
portable across all Rexxes (including the two
Using additional features introduced with other implementations
(notably directives in ooRexx) will also prohibit program porting.
Characters:
:Originally ¬ was
:This was later changed to the backslash on PCs and ^ on the host.
:On my German TSO I cannot use | and \ due to code page diff:erences.
Line 126 ⟶ 127:
-----
Classic REXX is not object-orientated REXX. To put them under an o-o umbrella would be a disservice to both languages. A classic REXX entered under the ooRexx language would (to me) imply that it would work using ooRexx, and I have no way of testing/verifying that. My main interest is in classic REXX and have no need for object-oriented features. Again: hammer, fly. I test all of my classic REXX program examples (unless noted otherwise) under three classic REXXes:
I don't know what you mean by ''plain'' REXX; the point under discussion is classic REXX vs. the o-o (object-orientated) REXXes.
Line 241 ⟶ 242:
-----
Er, no. The example version 2 for REXX was a straight copy of version 1's functionality (but with the
This also implies that the NetRexx version has the same problem, as the REXX version (as stated) was taken/copied/transcribed from NetRexx), but I can't verify if the NetRexx version as I don't have access to the NetRexx language. Most likely, other examples have the same inability.
|