From: <hp...@we...> - 2022-06-09 02:44:37
|
Hello Rony! Sorry for my delayed response, but a PC not touched several month takes its time to be up to date again. Am 08.06.2022 um 13:31 schrieb Rony G. Flatscher: > > Maybe one more thing: the current version of BSF4ooRexx is > supposed to work with ooRexx 4.1 and higher. If it does not, then > it is to be regarded as an error in the current GA release of > BSF4ooRexx! If you find such errors please file a bug with a small > sample at <https://sourceforge.net/p/bsf4oorexx/bugs/> (if going > there, yes, currently there are no known bugs!). This may be > possible as my testing with pre-5.0 interpreters (due to time > restrictions) has become limited (e.g. it may be the case that > here and there 5.0 features got introduced by mistake). I'd like to get VilMA converted to use NetRexx Pipelines first as agreed with René. When this works I'll take it to the pre-5.0 ooRexx PC. I prefer to take one step after the other and to avoid as much interferences as possible. > Ad release and supported minimum versions of ooRexx and Java: one > can infer that from the naming, the current GA version of > BSF4ooRexx is named: "BSF4ooRexx-641.20220131". So here the > deciphering in a rexxtry session: > [...] Is there an indicator if the installed java is too old? > --- > > Also, one, two things you might want to know: > > * it is possible to run ooRexx 5.0 without installation, if no > older Rexx is installed. I have on my "test-NetRexx-Pipelines-with-BSF4ooRexx-Support"-PC now installed ooRexx 5.0, which installed also ooDialog 4.2.4 (preview), unasked. No problem since it's a test machine only. > * ooRexx 5.0 introduced the ability to run 32- and 64-bit ooRexx > interpreters in parallel without > inhibiting each other! It is also possible to run different > revisions of ooRexx 5.0 in parallel. I assume, the how-to is described somewhere. How to use BSF4ooRexx to make stage varload set vars in ooRexx -- later please, not now, I'm too tired. Best M. |