Am 10.01.2022 um 16:16 schrieb Seymour J Metz <sme...@gmu.edu>: > > >> >> ooRexx will never be high speed because it's implementation is >> fundamentally ineffecient. No, for what ooRexx does and allows for it is not „fundamentally inefficient“. If forgoing all its helpful new features, because all of a sudden „inheritance“ or „message paradigm“ is not important, then you could implement it totally different. But then you loose what makes it so powerful and easy to use.
Just think about REXX and for what purposes you use it there. If „hi speed“ gets important then you probably use native code/functions/libraries from REXX. I know of companies that use ooRexx with BSF4ooRexx for nifty professional applications, where they use powerful JavaFX for the GUI, but interact with RDBMS on IBM middle range hardware. They develop on the MacOS platform, but can deploy their products on Windows and Linux. Complex, challenging applications that get created and maintained with ooRexx+BSF4ooRexx. The reason? They had REXX knowledge (coming from the mainframe world, also consulting AS/400 customrs etc.), learned about ooRexx and BSF4ooRexx and were able (on their own!) to learn and research all they needed for a solution that others would have thought was impossible with REXX knowledge. Rather they would speculate/expect to have to learn a new language from scratch. This is not the case, one can keep and take advantage of the REXX knowledge and year long experiences. —-rony Rony G. Flatscher (mobil/e) ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
