On 14.07.2017 21:00, John Timmons wrote:
> This sounds like somebody isn't locking/guarding the stack when it is being
> updated...probably on
> the Java side. It might be assuming that no one else is going to update ITS
> "proprietary" stack.
> Wrong.
There could be many reasons for the perceived behaviour. It is very well
possible that my BSF4ooRexx
is to blame, maybe ooRexx (there are crashes that can be caused without
BSF4ooRexx, but these
crashes may have other reasons), but I doubt that Java would be to blame. Java
offers an incredible
wealth of fine tuned concurrent classes, e.g.
<https://docs.oracle.com/javase/8/docs/api/index.html?java/util/concurrent/package-summary.html>,
here with relation to JavaFX:
<https://docs.oracle.com/javase/8/javafx/interoperability-tutorial/concurrency.htm>
and tons of test
units for them.
---rony
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
