Anonymous user
Rosetta Code:Village Pump/Dialects: Difference between revisions
m
clarified classic REXX vs o-o Rexx, added questions, added which versions of Regina allowed single-line comments. -- ~~~~
Walterpachl (talk | contribs) (cross posting as one way of bringing ooRexx and REXX together) |
m (clarified classic REXX vs o-o Rexx, added questions, added which versions of Regina allowed single-line comments. -- ~~~~) |
||
Line 58:
- the Upper instruction
- /= and /== as alternatives to \= or \== (see characters below)
</pre>
::: I hate to interject here, but where you referring to '''ooRexx''' when stating that some 'features' were removed? If that's the case, could you add ... were removed from ooRexx (or maybe say ... not implenteded in ooRexx and/or removed from the ooRexx' standard(s). As it stands now, it sounds like the classic (original?) REXXes no longer support those 'features' listed above. [As far as I know, most classic REXXes still support a majority of those features.] Also (regarding below), what (or where) did you mean "other features were introducted..."? Were you speaking of the classic REXX standard or ooRexx? Please feel free to delete these comments as they are obtrusive and I only placed them here to clarify your point and have this in close proximity to the statements in question. -- [[User:Gerard Schildberger|Gerard Schildberger]] 22:16, 8 July 2012 (UTC)
<pre>
Other features were introduced with the ANSII standard created
Line 71 ⟶ 75:
- -- as line comment (instead of /* ... */)
Regina 3.4 introduced the single-line comment feature,
Regina 3.5 wasn't configurable concerning single-line comments,
and it wasn't until
Regina 3.6 that allowed the noSingle_line_comments
environmental variable. --- Gerard Schildberger
Avoiding all of the language elements mentioned above makes a program
Line 115 ⟶ 125:
I shall proceed in that direction.
--[[User:Walterpachl|Walterpachl]] 21:13, 8 July 2012 (UTC)
-----
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: Personnal/REXX, Regina (sometimes more than one version when there is a perculiar release-based feature), and R4. [Sometimes I say PC/REXX when I meant to say Personnal REXX --- they have the same pedigree.]
I don't know what you mean by ''plain'' REXX; the point under discussion is classic REXX vs. the o-o (object-orientated) REXXes.
And yes, some ooRexx examples have that wording: " ... the entry under REXX works with oo-REXX ..." (or NetRexx). There's nothing wrong with that, and it shows for that particular classic REXX program, it solves the task using that language. As for asking what I want, I have no interest in the o-o REXXes. I don't care if you want to enter a comment under ooRexx that it works with the program entry under REXX or not (but I think that would be a good idea). I you want to change a copy of a classic REXX program and then move that changed classic REXX program to the ooRexx language section, I think that would also be a great idea and an endeaver worth the time and effort. -- [[User:Gerard Schildberger|Gerard Schildberger]] 22:16, 8 July 2012 (UTC)
----
This is one of the cross postings that you deny to exist. (24 game)
: Walter, I don't deny any exist. I emphatically stated that they DO exist ("... has now occurred ..."), and in any case, and I didn't specifically mention any particular REXX entry. I do wish you wouldn't accuse me of denying things to exist when I stated the opposite. Also, I have just noted that the program example that I referred to has just been moved to ooRexx. -- [[User:Gerard Schildberger|Gerard Schildberger]] 22:16, 8 July 2012 (UTC)
It was my start with the topic and you changed your program (thanks)
"While the solution shown within this page at Rexx version 2 was created for Classic Rexx
| |||