Jump to content

Talk:Sorting algorithms/Cycle sort: Difference between revisions

→‎4 REXXen: added more comments (4 REXXen).
(→‎4 REXXen: Thanks Gerard for the reply...)
(→‎4 REXXen: added more comments (4 REXXen).)
Line 21:
::Thanks Gerard for the reply. I guess it is a matter of style, and knowing that you have considered things then that's fine.
::P.s. maybe you could ask for the REXX version that works with version 1 if you interested in confirming that it works on something? Or maybe not. Only if you are interested I guess. --[[User:Paddy3118|Paddy3118]] ([[User talk:Paddy3118|talk]]) 00:32, 14 June 2014 (UTC)
 
-----
 
::: No thanks, I've beat that dead horse before.   I assume the aforementioned REXX program works for ooRexx   (since it uses a construct that is only valid in ooRexx);   although it was my version that was translated to ooRexx, not version 1.
 
[Note that ooRexx and NetRexx are considered different languages than REXX, but it is thought that it might be possible to (re-)write most REXX programs so that they will execute under ooRexx and NetRexx if certain restrictions are followed --- this is an on-going   ··· discussion   about this very matter --- does a programmer restrict their programming of (Classic) REXX so as to also execute under a different language such as object-oriented REXX?]
 
I'm a firm (and maybe overly religiously concerned) believer that any computer program solution posted under the (Classic) REXX language actually be tested/executed under a (Classic) REXX interpreter   --- well, this would extend to all Rosetta Code languages.   One would think this would be axiomatic on Rosetta Code.
 
Elsewhere, I wrote about a contest during my college days (cough, cough, Eisenhower was still alive) to write a (singular) program to compile and execute correctly under COBOL, FORTRAN, ASSEMBLER (IBM), ''and'' PL/I.   --- Yeah, yeah, yeah, back then, the languages were all capitalized and most of us used candles, quills, and parchment.   I view that endeavor that same as (Classic) REXX and ooRexx (and NetRexx).
 
I know of several REXX examples that have been entered on Rosetta Code that don't work for a Classic REXX, but rather than hit that beehive with a stick, I just enter my own REXX program version.   Meanwhile, back at the ranch ... whenever I find one of my REXX computer programs that don't work for all the REXXes that I have installed, I re-write the REXX program so that it does execute correctly under all REXXes (that I have), unless otherwise noted as being specific to a particular REXX interpreter.
 
The various (Classic) REXX interpreters are very fortunate in that there are few differences between them, the main differences are those that have features or BIFs added. -- [[User:Gerard Schildberger|Gerard Schildberger]] ([[User talk:Gerard Schildberger|talk]]) 01:34, 14 June 2014 (UTC)
 
-----
Cookies help us deliver our services. By using our services, you agree to our use of cookies.