Rony,
I uploaded the changes to the "patches tracker" for BSF4Rexx.
There is a new target oorexx4 in the makefile (for Window only).
It defines the variable USE_OOREXX4 which is used for conditional
compilation (I leave you decide if that's the good way)
I use Visual C++ 2008 Express Edition, and I had to remove INITINSTANCE
from BSF4Rexx.def (syntax error).
No longer needed to modify the call RxFuncLoad, thanks to Rick.
It's really impressive to see BSF4Rexx working like a breeze with ooRexx
4, without no change at all !
Tested with jre1.6.0_11
Jean-Louis
"Rony G. Flatscher" <rony.flatsc...@wu-wien.ac.at>
04/01/2009 20:02
Please respond to
Open Object Rexx Developer Mailing List
<oorexx-devel@lists.sourceforge.net>
To
Open Object Rexx Developer Mailing List
<oorexx-devel@lists.sourceforge.net>
cc
Subject
Re: [Oorexx-devel] BSF4Rexx and ooRexx 4.0 : (tiny) adjustments needed -
and a bug in rxapi.exe ?
Rick McGuire wrote:
Neither of those APIs should be necessary in 4.0. RexxStart will now
behave the way it should always have behaved and wait for all threads
started by the executed program to terminate. I hadn't realized those
APIs had actually been documented. I think I'll need to add back in
some stubbed replacements that just return immediately and document
them as deprecated.
Thank you, just saw that you already took care of it in today's rev 3861
which is great.
---rony
On Sun, Jan 4, 2009 at 6:13 AM, Rony G. Flatscher
<rony.flatsc...@wu-wien.ac.at> wrote:
Bonjour Jean-Louis,
great that you are tackling BSF4Rexx on ooRexx 4.0 already!
Under Windows, the current version of BSF4Rexx (2008-09-12) does not work
with ooRexx 4.0.
BSF4Rexx.dll is not loaded because it depends on these functions which are
no longer exported by rexx.dll :
RexxWaitForTermination
RexxDidRexxTerminate
I recompiled BSF4Rexx without these dependencies (is it safe to do that ?)
Under pre 4.0 ooRexx it is mandatory to have these available. The reason:
if
ooRexx programs run multithreaded then the threads need to be able to
continue, even if the main thread has finished already.
Not sure how 4.0 behaves. So I would at least do a conditional include,
i.e.
do not include them if compiled for ooRexx 4.0, until Rick can clarify the
behaviour on 4.0.
An other problem occurred :
call rxFuncAdd "BsfLoadFuncs", "BSF4Rexx", "BsfLoadFuncs"
fails, because ooRexx 4.0 searches for "BsfLoadFuncs" and does not find it
(it's "BSFLOADFUNCS" which is exported).
Easy to fix, use
call rxFuncAdd "BsfLoadFuncs", "BSF4Rexx", "BSFLOADFUNCS"
(4.0 is more strict than 3.2, other external packages may need this kind
of
adjustment)
Interesting.
Now, infoBSF.rex and infoBSF-oo.rex works.
Super!
During my trials and errors, I had several times the script infoBSF.rex
frozen during initialization.
Maybe the problem comes from rxapi.exe.
RegistrationData::findSessionReference in RegistrationManager.cpp, I think
this line is missing :
cookie = cookie->next
Here are the changes I made to BSF.cc (all are fixes for compilation
errors
due to changes in rexx.h) :
If you can supply a unified diff, I would apply it to the original source
(license is <http://www.apache.org/licenses/LICENSE-2.0>).
Regards,
---rony
------------------------------------------------------------------------------
_______________________________________________
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
------------------------------------------------------------------------------
_______________________________________________
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
------------------------------------------------------------------------------
_______________________________________________
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
------------------------------------------------------------------------------
_______________________________________________
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
