RFR: 8287745 jni/nullCaller/NullCallerTest.java fails with "exitValue = 1"

Tim Prinzing tprinzing at openjdk.java.net
Mon Jun 6 20:55:05 UTC 2022


On Mon, 6 Jun 2022 07:45:16 GMT, David Holmes <dholmes at openjdk.org> wrote:

> Hi Tim,
> 
> Sorry but I have to ask why this test was created as a C++ program instead of keeping it as a C program likes it predecessors? No need for C++ libs or special exception handling flags in that case.

The idea was to reduce duplicate code.  Changing to use objects to encapsulate the up calls got rid of a lot of repeated code and made things simpler and clearer.  Objects are created with the class, method, and signature strings and then calls can be made and the the error reporting has a context.  It was simply easier to do in c++ and there was no reason not to use it.

-------------

PR: https://git.openjdk.java.net/jdk/pull/9010



More information about the build-dev mailing list