currently, BSF4ooRexx itself seems to be stable and bug-free, which
is nice. :)
Would you have comments on the following thoughts, ideas?
- However installing on newer 64-Bit Windows machines is
problematic, as the 32-bit script-based elevation seems to not
work anymore. So one improvement is to use a different elevation
mechanism that hopefully works on Vista, W7 and W8, using the
which has a MIT license. Would anyone object using such a tool
from you, and if so, why?
- As each Rexx interpreter instance has its own .local
environment it would be possible to store the thread id for
which the Java bridge was set up and store it e.g. as
"bsf.primodalTID" in .local. This would allow the ooRexx
programmer who runs multiple Rexx threads to use
BSFAttachtoTID() by merely using the environment symbol
- BSFAttachToTID()' argument could be made optional, and if
missing, .bsf.primodalTID is used.
- It may be even possible to do an automatic BSFAttachToTid()
using .bsf.primodalTID from native code as well, foregoing the
need to do an explicit BSFAttachToTID().
- OpenOffice ScriptProviderForooRexx()-support is not functional
on MacOSX since AOO 4.x, the reason seems to be with the
dispatching changes in AOO 4.x. The error from
ScriptProviderForooRexx()-support is too general as to hint to
the cause of a problem (e.g. running UNO.CLS causes the Java awt
error to popup on MacOSX only, due to the "interesting"
event-loop design on MacOSX).
- So the idea is to try to add more granular error messages to
ScriptProviderForooRexx() which should help the programmer to
better identify a problem in that area.
- Note, interfacing with OpenOffice via BSF4ooRexx is not
affected, only executing ooRexx macros from within AOO 4.x.
- AIX: there is a 64-bit compilation of BSF4ooRexx.cc that is
reported to be functional, making BSF4ooRexx available on 64-bit
AIX. The idea would be to get somewher access to an AIX machine
to adapt the BSF4ooRexx installation scripts to AIX, thereby
allowing to add the AIX binary to the distribution.
The idea would be to work on these items in the next weeks and to
finalize a new version of BSF4ooRexx (maybe a version 4.5) for
this year's International Rexx symposium at the beginning of May.
What do you think? Any feedback highly appreciated.