Category talk:REXX Implementations: Difference between revisions

From Rosetta Code
Content added Content deleted
(The important part is still the "on Rosetta Code" part)
(added a long-winded comment about my confusion. Yak, yak, yak. -- ~~~~)
Line 6: Line 6:
:Make sure you read the rest of the sentence: "on Rosetta Code". It ''is'' all of the ones that are on this site. --[[User:Mwn3d|Mwn3d]] 00:10, 9 June 2012 (UTC)
:Make sure you read the rest of the sentence: "on Rosetta Code". It ''is'' all of the ones that are on this site. --[[User:Mwn3d|Mwn3d]] 00:10, 9 June 2012 (UTC)


:: No, there are other REXXes, and most of them (I haven't tried them all, of course) work with most of my REXX examples), but I didn't include the other various REXXes as one of them is propietary (that is, it costs money to use), and others I don't know enough about to discuss here, and one or more of them only work on *NIX systems, which I don't have). I don't mention which REXXes the example(s) work on, that would entail too much testing. Except for the Hello World program, which would proably work everywhere. I try to make sure that my REXX examples work on the three REXXes that I have on my (Windows) PC. -- [[User:Gerard Schildberger|Gerard Schildberger]] 00:23, 9 June 2012 (UTC)
:: No, there are other REXXes, and most of them (I haven't tried them all, of course) work with most of my REXX examples), but I didn't include the other various REXXes as one of them is propietary (that is, it costs money to use), and others that I don't know enough about to discuss here, and one or more of them only work on *NIX systems, which I don't have). I don't mention which other REXX interpreters the REXX example(s) work on, that would entail too much testing.
Except for the Hello World program, which would proably work everywhere. I try to make sure that my REXX examples work on the three REXXes that I have on my (Windows) PC. -- [[User:Gerard Schildberger|Gerard Schildberger]] 00:23, 9 June 2012 (UTC)

:::Which other REXXes are there '''on Rosetta Code''' that should go in this category? They should be marked as such on their respective pages. If there aren't any others that are already on the site then the text is correct the way it is. --[[User:Mwn3d|Mwn3d]] 01:30, 9 June 2012 (UTC)
:::Which other REXXes are there '''on Rosetta Code''' that should go in this category? They should be marked as such on their respective pages. If there aren't any others that are already on the site then the text is correct the way it is. --[[User:Mwn3d|Mwn3d]] 01:30, 9 June 2012 (UTC)

:::: I'm now confused. I don't quite fully understand about REXXes on Rosetta Code. I assume you mean the ''examples'' of REXX programs. As such, there isn't a REXX interpretor on RC, and I haven't been noting which REXX interpreters (if any) for the most part, which REXX it was written ''for'' [or runs under -- I write the REXX code to conform to the REXX standard, and most REXX try very hard to adhere to ''the'' REXX standard. This isn't as simple as I make it sound. There is a lot of interpretation in the Regina REXX's standard (with is really a documentation manual) for instance. It needs a lot of work to approach IBM's standard of documentation. I only have access to (as I mentioned previously) three REXX interpretors, and I try to use all three to test the REXX programs before posting them. None of the (eariler) REXXes noted which ones they used when I first started reading Rosetta Code, and I continued that tradition. Oops-ay, I lied. I actually have a fourth REXX interpreter which I won't mention --- it's so buggy that I refuse to even mention the name of it. It's documentation is almost none-existant. But I really don't want to go back and mark each example for which it was written for or tested under. I note that hardly any examples (not just REXX) do this, although some do, of course. There are other REXX interpreters out there, I know but of a few. The older REXX on CMS and TSO are essentially, the same REXX. I wish dearly that I could have access to these. I consider those REXXes the ''gold standard''. If a REXX program works there, and not elsewhere, usually the REXX that "doesn't" work gets changed. REXX programs written on IBM mainframes will run (compile) forever, IBM is very good and keeping the older programs running. Upward compatible in IBM-land is pratically a mantra, a religious creed. Kudos to the old guard. There is also one REXX '''compiler''' (I think, only on the IBM mainframes) --- I believe it is of different code. I have even less REXXes than that which I can use/test. I just looked at the "sum of squares" Rosetta Code task, and of 94 examples, only 7 mention which "compiler" they use, and some of them, like Algol, Fortran, BASIC, and a few others have versions are are somewhat incompatable, proabably because of added (and/or depreciated) features (this is my assumption and probably reflects too much of me viewing the bigger picture). To top it all off, there are some people who think that ooRexx and oRexx are also REXXes, and almost none of my (classic) REXX will ''run as is'' under those object-orientated REXXes. Classic REXX is the REXX that started it all (1982 or so), the that name is used to differentiate it from the object REXXes and NetRexx. It is this Classic REXX (standard) that I program the REXX examples for. I forgot to mention KEXX, the REXX that KEDIT uses (both of which I have). I haven't even brought up the differences of the REXXes that behave differently when they execute under a different operating system. Re-reading this entry, I maybe shouldn't have thrown so many stones. I may wake up tomorrow and delete the whole she-bang when I come to my senses. -- [[User:Gerard Schildberger|Gerard Schildberger]] 02:19, 9 June 2012 (UTC)

Revision as of 02:19, 9 June 2012

I want to change this page from
these are all of the REXX implementations to
these are some of the REXX implementations,

but there doesn't seem to be a way to do that. -- Gerard Schildberger 22:18, 8 June 2012 (UTC)

Make sure you read the rest of the sentence: "on Rosetta Code". It is all of the ones that are on this site. --Mwn3d 00:10, 9 June 2012 (UTC)
No, there are other REXXes, and most of them (I haven't tried them all, of course) work with most of my REXX examples), but I didn't include the other various REXXes as one of them is propietary (that is, it costs money to use), and others that I don't know enough about to discuss here, and one or more of them only work on *NIX systems, which I don't have). I don't mention which other REXX interpreters the REXX example(s) work on, that would entail too much testing.

Except for the Hello World program, which would proably work everywhere. I try to make sure that my REXX examples work on the three REXXes that I have on my (Windows) PC. -- Gerard Schildberger 00:23, 9 June 2012 (UTC)

Which other REXXes are there on Rosetta Code that should go in this category? They should be marked as such on their respective pages. If there aren't any others that are already on the site then the text is correct the way it is. --Mwn3d 01:30, 9 June 2012 (UTC)
I'm now confused. I don't quite fully understand about REXXes on Rosetta Code. I assume you mean the examples of REXX programs. As such, there isn't a REXX interpretor on RC, and I haven't been noting which REXX interpreters (if any) for the most part, which REXX it was written for [or runs under -- I write the REXX code to conform to the REXX standard, and most REXX try very hard to adhere to the REXX standard. This isn't as simple as I make it sound. There is a lot of interpretation in the Regina REXX's standard (with is really a documentation manual) for instance. It needs a lot of work to approach IBM's standard of documentation. I only have access to (as I mentioned previously) three REXX interpretors, and I try to use all three to test the REXX programs before posting them. None of the (eariler) REXXes noted which ones they used when I first started reading Rosetta Code, and I continued that tradition. Oops-ay, I lied. I actually have a fourth REXX interpreter which I won't mention --- it's so buggy that I refuse to even mention the name of it. It's documentation is almost none-existant. But I really don't want to go back and mark each example for which it was written for or tested under. I note that hardly any examples (not just REXX) do this, although some do, of course. There are other REXX interpreters out there, I know but of a few. The older REXX on CMS and TSO are essentially, the same REXX. I wish dearly that I could have access to these. I consider those REXXes the gold standard. If a REXX program works there, and not elsewhere, usually the REXX that "doesn't" work gets changed. REXX programs written on IBM mainframes will run (compile) forever, IBM is very good and keeping the older programs running. Upward compatible in IBM-land is pratically a mantra, a religious creed. Kudos to the old guard. There is also one REXX compiler (I think, only on the IBM mainframes) --- I believe it is of different code. I have even less REXXes than that which I can use/test. I just looked at the "sum of squares" Rosetta Code task, and of 94 examples, only 7 mention which "compiler" they use, and some of them, like Algol, Fortran, BASIC, and a few others have versions are are somewhat incompatable, proabably because of added (and/or depreciated) features (this is my assumption and probably reflects too much of me viewing the bigger picture). To top it all off, there are some people who think that ooRexx and oRexx are also REXXes, and almost none of my (classic) REXX will run as is under those object-orientated REXXes. Classic REXX is the REXX that started it all (1982 or so), the that name is used to differentiate it from the object REXXes and NetRexx. It is this Classic REXX (standard) that I program the REXX examples for. I forgot to mention KEXX, the REXX that KEDIT uses (both of which I have). I haven't even brought up the differences of the REXXes that behave differently when they execute under a different operating system. Re-reading this entry, I maybe shouldn't have thrown so many stones. I may wake up tomorrow and delete the whole she-bang when I come to my senses. -- Gerard Schildberger 02:19, 9 June 2012 (UTC)