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
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
Bonjour Jean-Louis,
I uploaded the changes to the patches tracker for BSF4Rexx.
Great, thank you very much!
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
Roni,
I confirm that the current distribution built with ooRexx 3.2 works well
with ooRexx 4, after the changes made by Rick today.
All the scripts in samples run without problem, from rexx or from java.
Only Snippet108.rex is not running, I suppose I don't have SWT.
Even not a little bug to
Bonjour Jean-Louis,
I confirm that the current distribution built with ooRexx 3.2 works
well with ooRexx 4, after the changes made by Rick today.
All the scripts in samples run without problem, from rexx or from java.
That's really great news!
Only Snippet108.rex is not running, I suppose I
On Sun, Jan 4, 2009 at 6:33 PM, Rony G. Flatscher
rony.flatsc...@wu-wien.ac.at wrote:
Bonjour Jean-Louis,
I confirm that the current distribution built with ooRexx 3.2 works well
with ooRexx 4, after the changes made by Rick today.
All the scripts in samples run without problem, from rexx or
