I believe that the current ooRexx is faster but that it is 64-bit only, and still slower than Regina when running classic Rexx code.
There is no requirement that I know of to write a DSL for foo in foo. With regard to Lua, it's the implementation language for wiki extensions. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 ________________________________________ From: IBM Mainframe Discussion List [[email protected]] on behalf of David Crayford [[email protected]] Sent: Wednesday, June 29, 2022 9:54 AM To: [email protected] Subject: Re: Some questions on SYSCALL Hi Rony, I know ooRexx. I ported it to z/OS 10 years ago but it was buggy and slow. There is zero chance of IBM or a vendor wasting resources on REXX today as there is no market for it. Now we have Python on z/OS REXX is very much a legacy language. That's even more pertinent with the shift from TSO/ISPF to IDEs. I could be wrong and I'm willing to be turned. I'm a big fan of Lua which I consider to be the most elegant language I know. It can easily be used to write DSLs for configuration or model development. How do I write a DSL in REXX? https://secure-web.cisco.com/1zwwka9ikrz2Xisd3pYWYkYh_Q_tbNFsPDN57uWZIaSXWPlM6h9BLe1xSGcZ-T0vIdVvC05cVcgIMjecqoCzQSgGAlsLvvuolInHOKoS8XB96f9mY-avq4OztVSHNRJe9TtVHK54Pyo9BoPbw5u-CKRa4_-MebNKDA_sAnWBSkAT8bjLwIokBwrneh-u1sVGFB8QLYd_-r1X20zlWDSXaPM2USYGoIcnkZkp87hZJHcS58JqRxXl0lEZngrsMgqpgUpnguUHHalz2D2FjmZBOQcfcEZOGXlyWrMAgTo-iH1L2pBp8fe_jQYgrON9EGs24XIJehzw3Lh2FCCiWj4KoiCi4UlXaScRlCX83RpvvelePIAoq-4XuAlFN1sz7bUe-f9da7zAq31veX-K-BCdWodXoeD0oiil5KLWde95Yc3NInTPBpihQB1l7RuiM_TNI/https%3A%2F%2Fleafo.net%2Fguides%2Fdsl-in-lua.html On 29/06/2022 9:41 pm, Rony G. Flatscher wrote: > Hi David, > > On 29.06.2022 14:06, David Crayford wrote: >> On 29/06/2022 6:37 pm, Seymour J Metz wrote: >>> Sme, but manageable. The article Safe REXX at >>> <http://secure-web.cisco.com/1U-cEbyGSEGcoIb7CbHdBCM7EqV1QrPFBg1ql-ejAJo0ivTEKEn8o85zSW8sQ5JGruF6UW6TMsPtdyuC-fN_FhyffbQp90Raob5-4Xkb_pB91vBGSfx9RzmimizQpRy5lnzRqmB_-IyqUpcR0uL6c9W4_-e_mq3Y3PQBRCER9UIV4QQKEdzx1KGdfikLHChy_5Jak_CBZLVbuPZRnpp-jdfkKv1QNOGEMOyt9YO7umNBJiRtkU8IgxubA3TYqciAKx0Qqyoh6fuKqsbA9YVTbHNmma1KEoeQ81WTlnE3YEJE_nz6yzBpasGLWP7AQWfd1Ad9097622M5yAkxgb8hqP309HWuM-P23nP0VUNgzpgMnoU34t9fedfPG8bL6sq2fD9Ja_d-6nAyvcsiE6nKFBiU8j8GtleJ0YTIctJcqoowOy4HHVmphaRHZm5U2lOQ7/http%3A%2F%2Fwww.rexxla.org%2FNewsletter%2F9812safe.html> >>> and >>> <http://secure-web.cisco.com/1mPsmK9Rc_gBcwojK1nVonHiQmIogmEbnUr3iId3AUjbZ0URJZsO9yTzIin3vVyRcdzJxrm4p3Rhz82BKOOBBlXa1BAkg-5GSDH-pcvZjKORkWByiXMwaB9j-LAvDXdYhz88XeUPsdr4yHUU_Ky3VxaOLn2U9xhu5Ly8y_2AW25BGERnuq55yeDAl_KirFm4j1W1Nak4G3X-zN4Fa4ALZuTphhC91ilXQsUYLFxK1VkJNlw59OCB9Bv4f4vnh_YcFmKCVinFvKSAppFMYHCBmyKdLkiLV21X3TDrbQTprWhI2iHzZtsfiz7oFjGVr1aga-LZeI1QpiYlwAa5ZCTBSDYC0mEwCu7lReHAEIZpKI05xtypTUsYOrctsjDvEplnQfmfkdsSfTfLcaheUsXAc1wMi8HnbW5T8p3SelNLQUScPmNDPSeVbwQaBIL8kfJ5F/http%3A%2F%2Fwww.rexxla.org%2FNewsletter%2F9901safe.html";> >>> has some tips on >>> avoiding REXX pitfalls. >> >> What's the point in managing something when you can just use a better >> language? It's a good time to be working on z/OS as we have an >> abundance of choice. That's not entirely obvious on this forum where >> every problem seems to be met with a ham-fisted REXX solution. >> >> Yes, Crayford's bashing REXX again. I have some experience of using >> z/OS UNIX REXX services but I didn't find it productive. Maybe >> somebody with more knowledge than me could post a snippet that >> demonstrates how to recursively traverse a directory tree printing >> the entries. >> > The problem is that this is not constructive. Not sure why it is so > important for you to bash REXX even if it makes you look bad at times. > > REXX in the mainframe world (I learned REXX for the first time on a > VM/CMS 370 system a few decades ago) is of course a great - and > unmatched - productivity tool and as a result over the decades there > has been an incredible amount of useful REXX inventory created. Best, > REXX is easy to learn and easy to use like no other language of that > power. > > If you were to know ooRexx you would realize that porting it to the > mainframe would even help yourself and everyone else to settle on a > few important languages and not being forced to go astray with this > language for solving this particular problem, that language for > solving that particular problem, and then suggesting to use yet > another language for ... > > Porting ooRexx to the mainframe would allow for keeping the existing > REXX programs running with ooRexx (the design of ooRexx - by demand of > IBM's customers - is such that it is compatible with classic REXX). > Therefore one can use ooRexx to run existing REXX programs and one > could use ooRexx to create new classic REXX programs. > > Only then would one become able to take advantage of the many new > ooRexx features like becoming able to fetch e.g. stems by reference, > or using ANSI REXX' "address...with" (e.g. redirecting input from > stems or standard and error output to stems), being able to create > public Rexx routines (can be directly called from another REXX > program) and much more. > > Doing so would be sensible as it allows for exploiting the already > known programming language, its environment and existing REXX > infrastructure; one would gain new abilities and options from then on. > > Also the important property - being able to learn and understand the > language quickly - remains intact with ooRexx, it just increases the > problem solution capacity dramatically by embracing the > object-oriented paradigm the way it does. > > If Business administration students are able to learn ooRexx from > scratch in just four months such that in the end they have become able > to create programs for Windows and Microsoft Office (after only two > months) and portable (running unchanged on Windows, Linux and MacOS) > applications including OpenOffice/LibreOffice and even JavaFX (!) GUIs > (after another two months, exploiting all of Java which gets > camouflaged as the dynamically typed, caseless ooRexx, without having > to learn a single line of Java; one only needs to be able to read and > understand the JavaDocs). > > So it is feasible and not expensive at all to teach newcomers to > program in ooRexx. Putting ooRexx into the hands of REXXperts like the > ones that can be found here, would be a real and important boon ... > > As IBM has been successfully porting quite a few programming languages > to the mainframe, it should be feasible to port ooRexx as well as > ooRexx is purely implemented in C++ (it has in addition a very nice > and powerful native API to the interpreter) making a modern and > powerful incarnation of REXX available on the mainframe where REXX was > born ... > > ---rony > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
