Greetings John,
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.
I thought way back when Java was invented, one of the pros was "no direct memory access". No? So is in fact BSF4ooRexx able to directly edit the JVM's memory directly and bypass the JVM to do so? I am thankful, -- Michael Lueck Lueck Data Systems http://www.lueckdatasystems.com/ ------------------------------------------------------------------------------ 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
